Re: [pgsql-patches] pg_standby

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Dave Page <dpage(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org, Doug Knight <dknight(at)wsi(dot)com>
Subject: Re: [pgsql-patches] pg_standby
Date: 2007-02-08 15:09:51
Message-ID: 200702081509.l18F9pp01121@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


Patch applied. Thanks.

---------------------------------------------------------------------------

Simon Riggs wrote:
> On Wed, 2007-01-17 at 16:15 +0000, Simon Riggs wrote:
> > On Wed, 2007-01-17 at 10:05 -0500, Merlin Moncure wrote:
> > > On 12/28/06, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> > > > On Thu, 2006-12-28 at 19:26 +0000, Simon Riggs wrote:
> > > > > On Thu, 2006-12-14 at 12:04 +0000, Simon Riggs wrote:
> > > > > > pg_standby and test framework, in separate .tar files
> > > > >
> > > > > New version (v2), following further testing.
> > > > >
> > > > > Signal handling not included in this version.
> > > >
> > > > Signal handling now added, tested and working correctly in version 3,
> > > > attached.
> > > >
> > > > pg_standby is an example program for a warm standby script as discussed
> > > > on -hackers:
> > > > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00407.php
> > > >
> > > > Program looks complete and ready for review, to me.
> > >
> > > I double checked and re-ran all my test and confirmed that pg_standby
> > > move (-m) mode is definitely busted in v3 in the sense that a restart
> > > of the standby will not resume recovery and requires a pg_resetxlog to
> > > become operational -- it needs one more WAL file back than the oldest
> > > one available.
> >
> > new v4
> >
> > Changes
> > - removed -m command, design flaw in original spec, use -l instead
> > - added -k N command to cleanup archive and leave max N files
> > - fflush() points added to allow Windows debug
> > - bug fix: when .history file present
> > - bug fix: command line switch cleanup
> > - readme updated
>
> new v6 (v5 was Windows dev release)
>
> Changes
>
> - added -r option to specify maxretries
> - -l option for Windows Vista (only) using mklink
> - Windows examples and docs added to readme
> - code restructured to allow more easy customization
> - bug fix: -k 0 error fixed
>
> - successful port report from Dave Page on Windows XP
>
> --
> Simon Riggs
> EnterpriseDB http://www.enterprisedb.com
>

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-02-08 15:32:11 pgsql: Add lock matrix to documentation.
Previous Message Heikki Linnakangas 2007-02-08 14:47:11 Re: HOT for PostgreSQL 8.3

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-02-08 15:29:03 Re: [pgsql-patches] vc++ regression tests
Previous Message Tom Lane 2007-02-08 14:46:29 Re: Feature: POSIX Shared memory support