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

From Tom Lane
Subject Re: pg_ctl of postgres 8.4 doesn't behave the same than 9.x when using a custom unix socket path
Date
Msg-id 26211.1399470567@sss.pgh.pa.us
Whole thread Raw
In response to pg_ctl of postgres 8.4 doesn't behave the same than 9.x when using a custom unix socket path  (Cécile Tonglet <cecile.tonglet@gmail.com>)
List pgsql-bugs
Cécile Tonglet <cecile.tonglet@gmail.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



pgsql-bugs by date:

Previous
From: dlo@isam.kiwi
Date:
Subject: BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password
Next
From: Stephen Frost
Date:
Subject: Re: BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password