Re: [pgsql-patches] [PATCHES] pg_standby
At the risk of starting trouble, is there some reason this was added to
contrib and not put on pgfoundry ?
On Thursday 08 February 2007 10:09, Bruce Momjian wrote:
Patch applied. Thanks.
---
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
--
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 [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
Re: [pgsql-patches] [PATCHES] pg_standby
Patch applied. Thanks. --- 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 -- 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 [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly -- 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 6: explain analyze is your friend
Re: [pgsql-patches] [PATCHES] pg_standby
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 -- Simon Riggs EnterpriseDB http://www.enterprisedb.com pg_standby.v6.tar Description: Unix tar archive ---(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: [pgsql-patches] [PATCHES] pg_standby
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 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
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
Re: [pgsql-patches] [PATCHES] pg_standby
On 1/17/07, Doug Knight [EMAIL PROTECTED] wrote:
I confirm that I am seeing the exact same characteristic. Could you post
your rotating script?
note: this is still a work in progress, the crude but effective sleep
5 is due to be replaced with a lock/fifo and there catch_wal.sh needs
to be rewritten a bit. truncate is a C one-liner I wrote which does a
ftruncate.
*** primary: ***
archive_command = '/home/postgres/send_wal.sh %p %f'
*** send_wal.sh: ***
!/bin/bash
echo archiving: $2 ~/send_wal.log
cat $1 (echo placeholder) (echo $2) | nc $STANDBY 1234 sleep 5
*** secondary: ***
restore_command = 'pg_standby -m -w0 -t/raid/pitr/kill /raid/pitr %f %p'
*** catch_wal.sh ***
!/bin/bash
WALDIR=/raid/pitr
rm -f $WALDIR/*.old
rm -f $WALDIR/*.older
$WALDIR/tmp.older
$WALDIR/tmp.old
while true;
do
tmpfile=`mktemp`
nc -l 1234 $tmpfile || { echo FATAL: nc listen failed; exit 1; }
chown postgres:postgres $tmpfile
file_name=`tail -1 $tmpfile`
./truncate $tmpfile 16777216
rm -f $WALDIR/*.older
for i in `ls $WALDIR/*.old`; do mv $i $WALDIR/`basename $i .old`.older; done
mv $tmpfile $WALDIR/$file_name.old
cp --preserve=ownership $WALDIR/$file_name.old $WALDIR/$file_name
echo LOG: caught file: $file_name
done
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Re: [pgsql-patches] [PATCHES] pg_standby
On 1/17/07, Merlin Moncure [EMAIL PROTECTED] wrote: On 1/17/07, Doug Knight [EMAIL PROTECTED] wrote: I confirm that I am seeing the exact same characteristic. Could you post your rotating script? note: this is still a work in progress, the crude but effective sleep 5 is due to be replaced with a lock/fifo and there catch_wal.sh needs to be rewritten a bit. truncate is a C one-liner I wrote which does a ftruncate. this turned out not to fix the problem...working on it still! merlin ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgsql-patches] [PATCHES] pg_standby
On 1/17/07, Simon Riggs [EMAIL PROTECTED] wrote: 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 works fantastic. grazi...i guess my rotation would have worked with more files but -k is much cleaner. merlin ---(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
