On Monday 17 February 2014 21:14:35 Tom Lane wrote:
Kevin Grittner kgri...@ymail.com writes:
Perhaps we should arrange for a DROP DATABASE command to somehow
signal all backends to close files from that backend?
See commit ff3f9c8de, which was back-patched into 9.1.x as of 9.1.7.
Hi List,
I have droped a database a few hours ago to reclaim some badly-needed space,
but that disk space has not been freed yet. Investigating further, there are
lots of deleted but open files that seem to correspond to the droped db, all
open by some postgres process.
A lot of process were
On Monday 17 February 2014 18:46:49 Vincent de Phily wrote:
Hi List,
I have droped a database a few hours ago to reclaim some badly-needed space,
but that disk space has not been freed yet. Investigating further, there
are lots of deleted but open files that seem to correspond to the droped
Vincent de Phily vincent.deph...@mobile-devices.fr writes:
I have droped a database a few hours ago to reclaim some badly-needed space,
but that disk space has not been freed yet. Investigating further, there are
lots of deleted but open files that seem to correspond to the droped db, all
Vincent de Phily vincent.deph...@mobile-devices.fr wrote:
I have droped a database a few hours ago to reclaim some badly-needed space,
but that disk space has not been freed yet. Investigating further, there are
lots of deleted but open files that seem to correspond to the droped db, all
open
Kevin Grittner kgri...@ymail.com writes:
Perhaps we should arrange for a DROP DATABASE command to somehow
signal all backends to close files from that backend?
See commit ff3f9c8de, which was back-patched into 9.1.x as of 9.1.7.
Unfortunately, the complainant is running 9.1.2.
