Re: Requesting external_pid_file with postgres -C when not initialized lead to coredump - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Requesting external_pid_file with postgres -C when not initialized lead to coredump
Date
Msg-id CAB7nPqQjAKTV9iO1QO8BEXtXtJYhYMV9FbSnm6QLoZbTO-irZA@mail.gmail.com
Whole thread Raw
In response to Re: Requesting external_pid_file with postgres -C when not initialized lead to coredump  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Requesting external_pid_file with postgres -C when not initialized lead to coredump  (alain radix <alain.radix@gmail.com>)
List pgsql-hackers
On Wed, Jun 22, 2016 at 2:02 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> alain radix wrote:
>> So, here is my first patch for PostgreSQL.
>
> Looking forward to further ones,

A comment on this patch: this is an incorrect approach anyway.
PostmasterMain relies on this value being NULL to decide if this PID
file should be written or not, so this patch applied as-is would
result in a message outputted to stderr if the logic is not changed
there.
-- 
Michael



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Rethinking behavior of force_parallel_mode = regress
Next
From: Alvaro Herrera
Date:
Subject: Re: MultiXactId error after upgrade to 9.3.4