pg_standby issue - Mailing list pgsql-hackers

I just saw this issue... so though of reporting it before I have to get rid of the environment.<br /><br />I `touch`d
thetrigger file and I saw the following message:<br /><br />Trigger file            : /tmp/pg_standby.trigger.5444<br
/>Waiting for WAL file    : 000000010000000B000000F2<br />WAL file path           :
../wal_archive//000000010000000B000000F2<br/>Restoring to...         : pg_xlog/RECOVERYXLOG<br />Sleep
interval         : 5 seconds<br />Max wait interval       : 0 forever<br /> Command for restore     : cp
"../wal_archive//000000010000000B000000F2""pg_xlog/RECOVERYXLOG"<br /><br />WAL file not present yet. Checking for
triggerfile...Keep archive history      : 0000000100000000000000F1 and later<br /><br />running restore         : OK<br
/><br/>Trigger file            : /tmp/pg_standby.trigger.5444<br />Waiting for WAL file    :
000000010000000B000000F3<br/>WAL file path           : ../wal_archive//000000010000000B000000F3<br /> Restoring
to...        : pg_xlog/RECOVERYXLOG<br />Sleep interval          : 5 seconds<br />Max wait interval       : 0
forever<br/>Command for restore     : cp "../wal_archive//000000010000000B000000F3" "pg_xlog/RECOVERYXLOG"<br /><br
/>WALfile not present yet. Checking for trigger file...<br />WAL file not present yet. Checking for trigger file...<br
/><~40000 repetitions ><br />WAL file not present yet. Checking for trigger file...<br />WAL file not present
yet.Checking for trigger file...<br /> WAL file not present yet. Checking for trigger file...<span style="color:
rgb(255,0, 0);">trigger file found</span><br /><br />Trigger file            : /tmp/pg_standby.trigger.5444<br
/>Waitingfor WAL file    : 000000010000000B000000F3<br /> WAL file path           :
../wal_archive//000000010000000B000000F3<br/>Restoring to...         : pg_xlog/RECOVERYXLOG<br />Sleep
interval         : 5 seconds<br />Max wait interval       : 0 forever<br />Command for restore     : cp
"../wal_archive//000000010000000B000000F3""pg_xlog/RECOVERYXLOG"<br /><br />WAL file not present yet. Checking for
triggerfile...<br />WAL file not present yet. Checking for trigger file...<br /><br /><br /><br />Here's the background
info:<br/><br />This is a EnterpriseDB 8.2 installation (not very different from Postgres, architecturally (as if you
didn'tknow that :) ) ). So I had got the pg_standby code from PG version 8.3 and got it compiled it under the 8.2
environment.Set up a hot standby using the following restore_command:<br /><br />restore_command = 'pg_standby -c -d -s
5-w 0 -t /tmp/pg_standby.trigger.5444 ../wal_archive/ %f %p `perl pg_last_restart_point.pl` 2>>
pg_standby.log'<br/> <br />Where pg_last_restart_point.pl is the same script I posted here a while back.<br /><br />The
standbyserver is running on the same box as the master DB. This was just a test setup, I had done for testing, a few
daysago. There hasn't been much activity (no activity on master DB):<br /><br />wc -l pg_standby.log<br /> 489122
pg_standby.log<br/><br />uniq pg_standby.log | wc -l<br />80<br /><br />    As you can see, before and after the
'triggerfile found' message, pg_standby is waiting for the same file! The standby server is still running, waiting for
pg_standbyto return.<br /><br />    If somebody wants to take a shot at debugging the issue, I'll leave the environment
asit is for a few hours more before I try to touch the trigger file again...<br /><br />Best regards,<br clear="all"
/><br/>-- <br /> gurjeet[.singh]@EnterpriseDB.com<br />singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com<br
/><br/>EnterpriseDB      <a href="http://www.enterprisedb.com">http://www.enterprisedb.com</a><br /><br />Mail sent
frommy BlackLaptop device