Re: [GENERAL] postmaster deadlock while logging after syslogger exited - Mailing list pgsql-general

From Michael Paquier
Subject Re: [GENERAL] postmaster deadlock while logging after syslogger exited
Date
Msg-id CAB7nPqTs18x4zPTsYwFUjKckACvdwftRMOvB3RB5zh-8+MkLLQ@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] postmaster deadlock while logging after sysloggerexited  (Andres Freund <andres@anarazel.de>)
List pgsql-general
On Fri, Nov 17, 2017 at 11:14 AM, Andres Freund <andres@anarazel.de> wrote:
> On 2017-11-17 11:09:56 +0900, Michael Paquier wrote:
>> when redirection_done is switched to true because the first process
>> generating a message to the syslogger pipe needs to open it first if
>> not done yet?
>
> I can't follow. The syslogger pipe is created when the first syslogger
> is started (before it's forked!). Which happens before other processes
> are created, because they all need to inherit that file descriptor.

Ah, OK. I didn't recall this dependency. Sorry for the confusion.
-- 
Michael


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Andres Freund
Date:
Subject: Re: [GENERAL] postmaster deadlock while logging after sysloggerexited
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] postmaster deadlock while logging after syslogger exited