Re: Bug with pg_ctl -w/wait and config-only directories

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, Fujii Masao <masao.fujii@gmail.com>, "Mr. Aaron W. Swenson" <titanofold@gentoo.org>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-10-05T14:44:38Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix nested PlaceHolderVar expressions that appear only in targetlists.

Peter Eisentraut wrote:
> On m?n, 2011-10-03 at 15:09 -0400, Bruce Momjian wrote:
> > Why were people not using pg_ctl?
> 
> Actually, a slight correction/addition here: The Debian init script does
> use pg_ctl to start the service.  Seems to work fine.

Yes.  The script authors discovered a working behavior, which matches my
research:

        pg_ctl start            specify config directory
        pg_ctl -w start         impossible
        pg_ctl restart          impossible
        pg_ctl stop             specify real data dir
        pg_ctl -w stop          specify real data dir
        pg_ctl reload           specify real data dir

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +