Skip site navigation (1) Skip section navigation (2)

Re: We should Axe /contrib/start-scripts

From: Chander Ganesan <chander(at)otg-nc(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: We should Axe /contrib/start-scripts
Date: 2009-08-25 19:53:15
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Alvaro Herrera wrote:
> Kevin Grittner wrote:
>> The reason is that we don't want certain other processes attempting to
>> start until and unless the database they use has started successfully.
> This is something we're not quite ready on, yet.  We need some mechanism
> that allows scripts to verify not only that postmaster started, but also
> that it has finished recovery.  You can sort-of do it by attempting a
> connection and checking the error message, but it's ugly.  There was
> talk about a pg_ping utility years ago, but nobody got around to writing
> it ...
Can't you use pg_controldata to see whether it is in recovery or not?  
Seems like you've got a way to see if it's running, seeing if it is in 
recovery should therefore be pretty straightforward, no?

Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC  27560

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2009-08-25 19:54:06
Subject: Re: We should Axe /contrib/start-scripts
Previous:From: Alvaro HerreraDate: 2009-08-25 19:48:07
Subject: Re: We should Axe /contrib/start-scripts

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group