I've been trying to work out a reliable script to determine,
after pg_ctl start, that the server is done attempting
to come up, and that it has either succeeded OR FAILED.
This is for several hundred unattended appliance-type servers,
currently on PG 8.0 but soon to be on 8.3
Haven't found anythi
Quoting "H. Hall" <[EMAIL PROTECTED]>:
>
> Mischa Sandberg wrote:
> > I've been trying to work out a reliable script to determine,
> > after pg_ctl start, that the server is done attempting
> > to come up, and that it has either succeeded OR FAILE
Comment below:
Joshua D. Drake wrote:
> On Sat, 2008-11-15 at 12:29 -0800, Mischa Sandberg wrote:
>> Quoting "H. Hall" <[EMAIL PROTECTED]>:
>>> Mischa Sandberg wrote:
>>>
>>>> I've been trying to work out a reliable script to
Perhaps it's my "test for DB ready" that's the problem?
This is the typical glitch I get ...
+ mkdir -p /persist/pgdata
+ chmod 700 /persist/pgdata
+ initdb -Atrust -Upmx -L/persist/pgsql/8.0.9/share >/dev/null
+ cp -p /persist/etc/p*g*.conf /persist/pgdata
+ chmod u+w /persist/home/mischa/pgdata/
Quoting Tom Lane <[EMAIL PROTECTED]>:
> Mischa Sandberg <[EMAIL PROTECTED]> writes:
> > Perhaps it's my "test for DB ready" that's the problem?
>
> > + while pg_ctl status && ! psql -l; do sleep 1; done >/dev/null
> 2>&1
&g
Quoting Tom Lane <[EMAIL PROTECTED]>:
> Mischa Sandberg <[EMAIL PROTECTED]> writes:
> > Quoting Tom Lane <[EMAIL PROTECTED]>:
> >> I'd bet that the pg_ctl status part is failing. I get exit status
> 1
> >> from it if there's no server
