Magnus Hagander <mag...@hagander.net> writes: > On Sun, Oct 11, 2015 at 5:22 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> I'm a bit suspicious that we may have leaked a handle to the shared >> memory block someplace, for example. That would explain why this >> symptom is visible now when it was not in 2009. Or maybe it's dependent >> on some feature that we didn't test back then --- for instance, if >> the logging collector is in use, could it have inherited a handle and >> not closed it?
> Even if we leaked it, it should go away when the other processes died. I'm fairly certain that we do not kill/restart the logging collector during a database restart (because it's impossible to reproduce the original stderr destination if we do). Not sure if any other postmaster children are allowed to survive. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers