Re: [PATCHES] pg_standby - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [PATCHES] pg_standby
Date
Msg-id 1173378868.3641.164.camel@silverbirch.site
Whole thread Raw
In response to Re: [PATCHES] pg_standby  (Doug Knight <dknight@wsi.com>)
Responses Re: [PATCHES] pg_standby  (Doug Knight <dknight@wsi.com>)
Re: [PATCHES] pg_standby  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Thu, 2007-03-08 at 13:29 -0500, Doug Knight wrote:

> I would preserve the existing trigger function as little t "-t", and
> maybe implement a catchup trigger function as big t "-T"? Set it up so
> that if the first attempt to find the WAL file postgres is currently
> requesting succeeds, skip over the trigger check. If the first attempt
> fails, then do your trigger check. That way, in the OCF script, the
> postmaster can be started, the trigger file set, and connection to the
> database looped on until it succeeds as an indication for when the
> database is up and available. I think that's cleaner than comparing a
> filename from a 'ps' command. Once I've completed the OCF script and
> done some testing, I'll forward it to you for you to review and see if
> you want to include it.

I'm happy to do this, unless other objections.

I'll be doing another version before feature freeze.

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Gaetano Mendola
Date:
Subject: Re: Calculated view fields (8.1 != 8.2)
Next
From: Alvaro Herrera
Date:
Subject: Re: RFC: changing autovacuum_naptime semantics