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

From Alvaro Herrera
Subject Re: Bug with pg_ctl -w/wait and config-only directories
Date
Msg-id 1317656397-sup-1708@alvh.no-ip.org
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
Excerpts from Tom Lane's message of lun oct 03 12:34:22 -0300 2011:
> Bruce Momjian <bruce@momjian.us> writes:
> > I am starting to question the value of config-only directories if pg_ctl
> > stop doesn't work, or you have to specify a different directory for
> > start and stop.
> 
> Yup.
> 
> > Did we not think of these things when we designed config-only
> > directories?  I don't even see this problem mentioned in our
> > documentation.
> 
> Yeah, we did.  The people who were lobbying for the feature didn't care,
> or possibly thought that somebody would fix it for them later.

I think the main proponents are the Debian guys, and they don't use
pg_ctl because they have their own pg_ctlcluster.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: [v9.2] DROP statement reworks
Next
From: "Kevin Grittner"
Date:
Subject: Re: How can i get record by data block not by sql?