Re: Postmaster holding unlinked files for pg_largeobject table

Kevin Grittner <kevin.grittner@wicourts.gov>

From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>

To: "Alvaro Herrera" <alvherre@commandprompt.com>, "Tom Lane" <tgl@sss.pgh.pa.us>

Cc: "alexk" <alexk@commandprompt.com>, "Alexander Shulgin" <ash@commandprompt.com>, "pgsql-hackers" <pgsql-hackers@postgresql.org>

Date: 2011-06-06T15:58:51Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Reset reindex-in-progress state before reverifying an exclusion constraint.
- dccfb72892ac 9.1.0 cited

Alvaro Herrera <alvherre@commandprompt.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