Re: Bug with pg_ctl -w/wait and config-only directories
Aaron W. Swenson <titanofold@gentoo.org>
From: "Mr. Aaron W. Swenson" <titanofold@gentoo.org>
To: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-10-05T21:41:29Z
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 →
-
Fix nested PlaceHolderVar expressions that appear only in targetlists.
- ceaf5052c6a7 8.4.9 cited
On Wed, Oct 05, 2011 at 10:44:38AM -0400, Bruce Momjian wrote:
> 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
> ...
Maybe I'm misunderstanding what you've written, but for 'pg_ctl -w' it is
possible. The following command does work (I've replaced the variables
with their default values to make it easier to read):
su -l postgres \
-c "env PGPORT=\"5432\" /usr/lib/postgresql-9.1/bin/pg_ctl start -w \
-t 60 -s -D /var/lib/postgresql/9.1/data/ \
-o '-D /etc/postgresql-9.1/ \
--data-directory=/var/lib/postgresql/9.1/data/ \
--silent-mode=true'"
--
Mr. Aaron W. Swenson
Gentoo Linux Developer
Email : titanofold@gentoo.org
GnuPG FP : 2C00 7719 4F85 FB07 A49C 0E31 5713 AA03 D1BB FDA0
GnuPG ID : D1BBFDA0