Alvaro Herrera <alvhe...@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.1259630...@sss.pgh.pa.us I mention it only because there might be one place to fix both.... -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
