| From: | Vincent de Phily <vincent(dot)dephily(at)mobile-devices(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Deleted files still open long after droping a database |
| Date: | 2014-02-18 08:43:23 |
| Message-ID: | 1866412.G1gpuDE31P@moltowork |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday 17 February 2014 21:14:35 Tom Lane wrote:
> Kevin Grittner <kgrittn(at)ymail(dot)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.
Thanks for the detailed info, great to see it's already fixed. As it happens,
we're in the process of moving to new servers, where we'll strive to get a
better update process going.
--
Vincent de Phily
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 邓尧 | 2014-02-18 09:44:10 | How to discard partially retrieved result set with the C API? |
| Previous Message | Sofer, Yuval | 2014-02-18 07:37:36 | Postgres service (Windows) running as "local system" |