I confirm that I am seeing the exact same characteristic. Could you post
your rotating script?
On Wed, 2007-01-17 at 10:05 -0500, Merlin Moncure wrote:
> On 12/28/06, Simon Riggs <[EMAIL PROTECTED]> 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.
> I am currently working around this by rotating WAL files a couple of
> versions back in the shell script I am using to receive log files via
> netcat. move mode is very desirable because it keeps the maintenance
> down for the standby system.