Re: [GENERAL] Deleted files still open long after droping a database

2014-02-18 Thread Vincent de Phily
On Monday 17 February 2014 21:14:35 Tom Lane wrote: > Kevin Grittner 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,

Re: [GENERAL] Deleted files still open long after droping a database

2014-02-17 Thread Tom Lane
Kevin Grittner 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. regards

Re: [GENERAL] Deleted files still open long after droping a database

2014-02-17 Thread Kevin Grittner
Vincent de Phily 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 by some postgres process. > >

Re: [GENERAL] Deleted files still open long after droping a database

2014-02-17 Thread Tom Lane
Vincent de Phily 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 > open by some postgres process.

Re: [GENERAL] Deleted files still open long after droping a database

2014-02-17 Thread Vincent de Phily
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 dro