Re: Segmentation fault with postgres -C external_pid_file - Mailing list pgsql-bugs

From Jehan-Guillaume de Rorthais
Subject Re: Segmentation fault with postgres -C external_pid_file
Date
Msg-id 20160617162850.419d577b@firost
Whole thread Raw
In response to Re: Segmentation fault with postgres -C external_pid_file  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Le Thu, 16 Jun 2016 11:50:07 -0400,
Tom Lane <tgl@sss.pgh.pa.us> a =C3=A9crit :

> Michael Paquier <michael.paquier@gmail.com> writes:
> > On Thu, Jun 16, 2016 at 3:40 AM, Jehan-Guillaume de Rorthais
> > <jgdr@dalibo.com> wrote:
> >> I just found that the following command always produce a segmentation =
fault
> >> when external_pid_file is kept commented:
> >> $ postgres -C external_pid_file
> >> Segmentation fault (core dumped)
>=20
> > Confirmed. puts() would print (null) on OSX even if that's not
> > mentioned in the standard, and Linux would just segfault on it.
>=20
> Right, this is going to be platform-specific behavior.
>=20
> > So instead of your patch, I think that we'd rather just change
> > PostmasterMain() so as it outputs something useful to the user in case
> > of a NULL value, like that:
>=20
> Agreed, fixing the -C code seems much less likely to have unexpected
> side-effects than changing default values.  Will push this in a bit.

Thank you for the fix guys.

Regards,

pgsql-bugs by date:

Previous
From: Martín Marqués
Date:
Subject: Re: pg_dump doesn't dump new objects created in schemas from extensions
Next
From: Martín Marqués
Date:
Subject: Re: pg_dump doesn't dump new objects created in schemas from extensions