Re: [PATCHES] pg_standby remove unsupported switch u
Pavel Stehule escribió: Hello this patch removes unsupported switch u from description for command. Applied, thanks. I noticed that the usage section is not very uniform and could well use a cleanup, but I'm not doing it at this time. -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [PATCHES] pg_standby Error cleanup
Patch applied. Thanks. --- Darcy Buskermolen wrote: Please find attached a patch which provides for logging in the event that -k is unable to clean up an old WAL file. Also make the failed to remove file error message consistant for the trigger file. -- Darcy Buskermolen Command Prompt, Inc. Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ [ Attachment, skipping... ] ---(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 -- Bruce Momjian [EMAIL PROTECTED] http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [PATCHES] pg_standby Error cleanup
Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches It will be applied as soon as one of the PostgreSQL committers reviews and approves it. --- Darcy Buskermolen wrote: Please find attached a patch which provides for logging in the event that -k is unable to clean up an old WAL file. Also make the failed to remove file error message consistant for the trigger file. -- Darcy Buskermolen Command Prompt, Inc. Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ [ Attachment, skipping... ] ---(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 -- Bruce Momjian [EMAIL PROTECTED] http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [PATCHES] pg_standby
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. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 6: explain analyze is your friend
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: [PATCHES] pg_standby
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. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com pg_standby.v2.tar Description: Unix tar archive ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [PATCHES] pg_standby
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. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com pg_standby.v3.tar Description: Unix tar archive ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
