Re: Requesting external_pid_file with postgres -C when not initialized lead to coredump

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: alain radix <alain(dot)radix(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Requesting external_pid_file with postgres -C when not initialized lead to coredump
Date: 2016-06-21 21:45:35
Message-ID: CAB7nPqQjAKTV9iO1QO8BEXtXtJYhYMV9FbSnm6QLoZbTO-irZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 22, 2016 at 2:02 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2016-06-21 22:15:43 Re: MultiXactId error after upgrade to 9.3.4
Previous Message Tom Lane 2016-06-21 20:41:35 Re: Rethinking behavior of force_parallel_mode = regress