From: Mischa Sandberg <mischa_sandberg@telus.net>
To: pgsql-admin@postgresql.org
Subject: Re: Reliably determining whether the server came up
Date: Sat, 15 Nov 2008 12:29:05 -0800
Message-ID: <1226780945.491f3111e22de@legacywebmail.telus.net> (raw)
In-Reply-To: <491F1861.4060403@reedyriver.com>
References: <1226527535.491b532f4c45e@legacywebmail.telus.net>
<491F1861.4060403@reedyriver.com>
Quoting "H. Hall" <hhall1001@reedyriver.com>:
>
> 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 FAILED.
> > This is for several hundred unattended appliance-type servers,
> > currently on PG 8.0 but soon to be on 8.3
> >
>
> Why don't you try to create a connection to a db on each server?
Thanks, but that only tells me if the server is up at the time of trying
to connect. What I'm trying to test is, did the server just start up and
abort? This is in a large cluster, and in (say) a box-by-box software
upgrade, any time-outs are additive.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mischa_sandberg@telus.net
Subject: Re: Reliably determining whether the server came up
In-Reply-To: <1226780945.491f3111e22de@legacywebmail.telus.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox