Re: Bug with pg_ctl -w/wait and config-only directories - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Bug with pg_ctl -w/wait and config-only directories
Date
Msg-id CA+TgmoYUnN7SYnDw8ozRx3ntri__qpE_awtCx-yH+TQTbT5KCQ@mail.gmail.com
Whole thread Raw
In response to Re: Bug with pg_ctl -w/wait and config-only directories  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug with pg_ctl -w/wait and config-only directories
List pgsql-hackers
On Tue, Oct 4, 2011 at 8:32 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I still think this is a matter for HEAD only.  We haven't supported
> these cases in back branches and so there is little argument for
> back-patching.

According to Bruce's original post, there is at least one 9.1
regression here relative to 9.0:

>> What is even worse is that pre-9.1, pg_ctl start would read ports from
>> the pg_ctl -o command line, but in 9.1 we changed this to force reading
>> the postmaster.pid file to find the port number and socket directory
>> location --- meaning, new in PG 9.1, 'pg_ctl -w start' doesn't work for
>> config-only directories either.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Action requested - Application Softblock implemented | Issue report ID341057
Next
From: Robert Haas
Date:
Subject: Re: Action requested - Application Softblock implemented | Issue report ID341057