Re: pg_ctl of postgres 8.4 doesn't behave the same than 9.x when using a custom unix socket path

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Cécile Tonglet <cecile(dot)tonglet(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_ctl of postgres 8.4 doesn't behave the same than 9.x when using a custom unix socket path
Date: 2014-05-07 13:49:27
Message-ID: 26211.1399470567@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?UTF-8?Q?C=C3=A9cile_Tonglet?= <cecile(dot)tonglet(at)gmail(dot)com> writes:
> I think there is an issue with *pg_ctl of PostgreSQL 8.4*, it doesn't
> behave the same than 9.1 and 9.3 (didn't tested 9.2 yet). It does not give
> me back the control if I use *a unix socket different than /run/postgresql
> and disable listening*.

Sorry, you're out of luck on that. Pre-9.1 postmasters don't report
their socket location in postmaster.pid, so pg_ctl doesn't have a way
to find it out if it's not default.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Adrian Klaver 2014-05-07 14:03:25 Re: Server process crash - Segmentation fault
Previous Message Graham Johnson 2014-05-07 08:42:33 lost administrator privileges after postgres installation!