Re: [PATCHES] pg_standby
Not at all, in fact I was planning on using the infinite wait, and using something like heartbeat to force creation of the trigger file in the event the primary dies. Thanks Simon! Doug On Fri, 2007-02-02 at 14:38 +, Simon Riggs wrote: > On Thu, 2007-02-01 at 15:14 -0500, Doug Knight wrote: > > > Quick question on the -w option; setting it to zero "disables", do you > > mean it waits until the file appears or a trigger file appears, or it > > just doesn't wait at all? > > It means it waits forever, or until a trigger file appears - but a > trigger file is optional, so its possible to create an awkward > situation. I'm not happy with that default, but feedback from Merlin > suggested production problems with people not understanding that. > > I'm happy to change to whatever consensus is, so if you think that's > dumb, just shout. >
Re: [PATCHES] pg_standby
Hi Simon, Quick question on the -w option; setting it to zero "disables", do you mean it waits until the file appears or a trigger file appears, or it just doesn't wait at all? Doug Knight WSI Inc Andover, MA On Mon, 2007-01-22 at 13:06 +, Simon Riggs wrote: > On Wed, 2007-01-17 at 16:15 +, Simon Riggs wrote: > > 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 +, Simon Riggs wrote: > > > > > On Thu, 2006-12-14 at 12:04 +, 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 >
Re: [pgsql-patches] [PATCHES] pg_standby
I confirm that I am seeing the exact same characteristic. Could you post your rotating script? Thanks, Doug 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 +, Simon Riggs wrote: > > > On Thu, 2006-12-14 at 12:04 +, 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. > > merlin >
