Re: Postmaster holding unlinked files for pg_largeobject table
Alvaro Herrera <alvherre@commandprompt.com>
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Kevin Grittner <kevin.grittner@wicourts.gov>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, alexk <alexk@commandprompt.com>, Alexander Shulgin <ash@commandprompt.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-06T16:04: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
Excerpts from Kevin Grittner's message of lun jun 06 11:58:51 -0400 2011: > 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.... Hmm interesting. I don't think the placement suggested by Tom would be useful, because the Zabbix backends are particularly busy all the time, so they wouldn't run ProcessCatchupEvent at all. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support