Re: postmaster deadlock while logging after syslogger exited

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Pacheco <dap(at)joyent(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: postmaster deadlock while logging after syslogger exited
Date: 2017-11-17 02:16:14
Message-ID: CAB7nPqTs18x4zPTsYwFUjKckACvdwftRMOvB3RB5zh-8+MkLLQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Nov 17, 2017 at 11:14 AM, Andres Freund <andres(at)anarazel(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-11-17 02:39:49 Re: postmaster deadlock while logging after syslogger exited
Previous Message Andres Freund 2017-11-17 02:14:17 Re: postmaster deadlock while logging after syslogger exited