| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "alexk" <alexk(at)commandprompt(dot)com>, "Alexander Shulgin" <ash(at)commandprompt(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Postmaster holding unlinked files for pg_largeobject table |
| Date: | 2011-06-06 15:58:51 |
| Message-ID: | 4DECB2EB020000250003E1DD@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> What we found out after more careful investigation is that the
> file is kept open by a backend connected to a different database.
> I have a suspicion that what happened here is that this backend
> was forced to flush out a page from shared buffers to read some
> other page; and it was forced to do a fsync of this file. And
> then it forgets to close the file descriptor.
This sounds vaguely similar to what I found with WAL files being
held open for days after they were deleted by read-only backends:
http://archives.postgresql.org/message-id/15412.1259630304@sss.pgh.pa.us
I mention it only because there might be one place to fix both....
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-06-06 16:04:51 | Re: Postmaster holding unlinked files for pg_largeobject table |
| Previous Message | Alvaro Herrera | 2011-06-06 15:45:08 | Re: Postmaster holding unlinked files for pg_largeobject table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-06-06 16:04:51 | Re: Postmaster holding unlinked files for pg_largeobject table |
| Previous Message | Heikki Linnakangas | 2011-06-06 15:57:46 | Re: WIP: AuthenticationMD5 protocol documentation clarification |