Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 3374464FCFE
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat, 15 Nov 2008 16:29:11 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 98044-03 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat, 15 Nov 2008 16:29:09 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from defout.telus.net (defout.telus.net [204.209.205.13])
	by mail.postgresql.org (Postfix) with ESMTP id 0C07C64FC83
	for <pgsql-admin@postgresql.org>; Sat, 15 Nov 2008 16:29:07 -0400 (AST)
Received: from localhost ([204.209.205.55]) by priv-edmwes26.telusplanet.net
	(InterMail vM.7.08.03.00 201-2186-126-20070710) with ESMTP
	id <20081115202906.DKHZ2706.priv-edmwes26.telusplanet.net@localhost>
	for <pgsql-admin@postgresql.org>; Sat, 15 Nov 2008 13:29:06 -0700
Received: from 75.157.221.130 ( [75.157.221.130])
	as user a3a18850@204.209.205.54 by legacywebmail.telus.net with HTTP;
	Sat, 15 Nov 2008 12:29:05 -0800
Message-ID: <1226780945.491f3111e22de@legacywebmail.telus.net>
Date: Sat, 15 Nov 2008 12:29:05 -0800
From: Mischa Sandberg <mischa_sandberg@telus.net>
To: pgsql-admin@postgresql.org
Subject: Re: Reliably determining whether the server came up
References: <1226527535.491b532f4c45e@legacywebmail.telus.net>
	<491F1861.4060403@reedyriver.com>
In-Reply-To: <491F1861.4060403@reedyriver.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.1-cvs
X-Originating-IP: 75.157.221.130
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200811/79
X-Sequence-Number: 30733

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.