Closed
Bug 1201737
Opened 9 years ago
Closed 9 years ago
Close Zenko Postgres connection after each query
Categories
(Content Services Graveyard :: Tiles: Administration Front-End, defect)
Content Services Graveyard
Tiles: Administration Front-End
Tracking
(Not tracked)
RESOLVED
FIXED
Iteration:
43.2 - Sep 7
People
(Reporter: mruttley, Assigned: mruttley)
Details
najiang has requested that the connection to the database in zenko be closed after each request as it is causing problems on the backend. This was mentioned in a github issue here: https://github.com/matthewruttley/zenko/issues/1 He says "In Zenko, all database queries are executed via two global connections/cursors. That might unnecessarily hold the connection resources and prevent other applications from accessing the database. Better localize the connection usage, like create a new connection while executing a new query, and close it immediately once you're done using this connection. " I think this can be fixed by abstracting all queries to a specific querying function.
Assignee | ||
Updated•9 years ago
|
Iteration: --- → 43.2 - Sep 7
Points: --- → 2
Assignee | ||
Comment 1•9 years ago
|
||
Fixed https://github.com/matthewruttley/zenko/commit/e47023800380f53ede1e6db2cce35cdfaec4155e
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•