Re: pg_standby and build farm

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: simon(at)2ndquadrant(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_standby and build farm
Date: 2006-12-13 22:35:17
Message-ID: 20061214.073517.44988426.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'd love to see your program. Could you please submit to -pacthes?
--
Tatsuo Ishii
SRA OSS, Inc. Japan

> 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
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-12-13 22:42:37 Re: Operator class group proposal
Previous Message Tom Lane 2006-12-13 22:21:54 Re: Operator class group proposal