Re: Segmentation fault with postgres -C external_pid_file

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Segmentation fault with postgres -C external_pid_file
Date: 2016-06-16 15:50:07
Message-ID: 31465.1466092207@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ranier VF 2016-06-16 16:26:48 Re: Use after free? in fe-connect.c:closePGconn
Previous Message Rader, David 2016-06-16 15:34:41 Re: BUG #14194: Why do these bases are open to public access?