From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Segmentation fault with postgres -C external_pid_file |
Date: | 2016-06-17 14:28:50 |
Message-ID: | 20160617162850.419d577b@firost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Le Thu, 16 Jun 2016 11:50:07 -0400,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> > On Thu, Jun 16, 2016 at 3:40 AM, Jehan-Guillaume de Rorthais
> > <jgdr(at)dalibo(dot)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)
>
> > Confirmed. puts() would print (null) on OSX even if that's not
> > mentioned in the standard, and Linux would just segfault on it.
>
> Right, this is going to be platform-specific behavior.
>
> > 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:
>
> 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,
From | Date | Subject | |
---|---|---|---|
Next Message | Martín Marqués | 2016-06-17 17:21:01 | Re: pg_dump doesn't dump new objects created in schemas from extensions |
Previous Message | Martín Marqués | 2016-06-17 13:56:16 | Re: pg_dump doesn't dump new objects created in schemas from extensions |