pg_standby and build farm - Mailing list pgsql-hackers

From Simon Riggs
Subject pg_standby and build farm
Date
Msg-id 1166038610.3733.36.camel@silverbirch.site
Whole thread Raw
Responses Re: pg_standby and build farm  (Tatsuo Ishii <ishii@postgresql.org>)
Re: pg_standby and build farm  (Euler Taveira de Oliveira <euler@timbira.com>)
Re: pg_standby and build farm  ("Andrew Dunstan" <andrew@dunslane.net>)
List pgsql-hackers
I've written up a Warm Standby script as a .c program rather than
scripts, to allow it to be portable and potentially shipped as part of
PostgreSQL core.

pg_standby is designed to be a wait-for restore_command, required to
turn a normal archive recovery into a Warm Standby. Within the
restore_command of the recovery.conf you could configure pg_standby in
the following way:
   restore_command = 'pg_standby archiveDir %f %p'

It has a number of other useful options and works with Win32 also.

So far I've written this as a contrib module. Would people like to see
this submitted to -patches, or should I make it available via PgFoundry
HAPITR?

Should this be reworked as an src/bin program? Or is the contrib module
the best form for this in 8.3?

I've also written a test program that uses this. I'm using this on a
server at EDB to run a continuous Warm Standby test.

Would anybody consider this test script worth including somewhere in
core? and/or: Might it become part of the build farm?

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




pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Load distributed checkpoint
Next
From: "Jim C. Nasby"
Date:
Subject: Re: EXPLAIN ANALYZE