Ticket #435 (closed defect: wontfix)
Switching between ckan instances causes orphaned postgres processes
| Reported by: | dread | Owned by: | thejimmyg |
|---|---|---|---|
| Priority: | awaiting triage | Milestone: | ckan-v1.4 |
| Component: | ckan | Keywords: | |
| Cc: | Repository: | ||
| Theme: |
Description
Analysis using pg_top reveals orphaed processes:
https://trac.dataco.coi.gov.uk/projects/datagov/ticket/460#comment:6
This followed switching ckan instances on the dgu machine. Do these hang around forever clogging up a db server? Can switching between instances be smoothed to avoid this?
Change History
Note: See
TracTickets for help on using
tickets.
