I just saw this issue... so though of reporting it before I have to get rid of the environment.
I `touch`d the trigger file and I saw the following message: Trigger file : /tmp/pg_standby.trigger.5444 Waiting for WAL file : 000000010000000B000000F2 WAL file path : ../wal_archive//000000010000000B000000F2 Restoring to... : pg_xlog/RECOVERYXLOG Sleep interval : 5 seconds Max wait interval : 0 forever Command for restore : cp "../wal_archive//000000010000000B000000F2" "pg_xlog/RECOVERYXLOG" WAL file not present yet. Checking for trigger file...Keep archive history : 0000000100000000000000F1 and later running restore : OK Trigger file : /tmp/pg_standby.trigger.5444 Waiting for WAL file : 000000010000000B000000F3 WAL file path : ../wal_archive//000000010000000B000000F3 Restoring to... : pg_xlog/RECOVERYXLOG Sleep interval : 5 seconds Max wait interval : 0 forever Command for restore : cp "../wal_archive//000000010000000B000000F3" "pg_xlog/RECOVERYXLOG" WAL file not present yet. Checking for trigger file... WAL file not present yet. Checking for trigger file... < ~40000 repetitions > WAL file not present yet. Checking for trigger file... WAL file not present yet. Checking for trigger file... WAL file not present yet. Checking for trigger file...trigger file found Trigger file : /tmp/pg_standby.trigger.5444 Waiting for WAL file : 000000010000000B000000F3 WAL file path : ../wal_archive//000000010000000B000000F3 Restoring to... : pg_xlog/RECOVERYXLOG Sleep interval : 5 seconds Max wait interval : 0 forever Command for restore : cp "../wal_archive//000000010000000B000000F3" "pg_xlog/RECOVERYXLOG" WAL file not present yet. Checking for trigger file... WAL file not present yet. Checking for trigger file... Here's the background info: This is a EnterpriseDB 8.2 installation (not very different from Postgres, architecturally (as if you didn't know 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: 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' Where pg_last_restart_point.pl is the same script I posted here a while back. The standby server is running on the same box as the master DB. This was just a test setup, I had done for testing, a few days ago. There hasn't been much activity (no activity on master DB): wc -l pg_standby.log 489122 pg_standby.log uniq pg_standby.log | wc -l 80 As you can see, before and after the 'trigger file found' message, pg_standby is waiting for the same file! The standby server is still running, waiting for pg_standby to return. If somebody wants to take a shot at debugging the issue, I'll leave the environment as it is for a few hours more before I try to touch the trigger file again... Best regards, -- [EMAIL PROTECTED] [EMAIL PROTECTED] gmail | hotmail | indiatimes | yahoo }.com EnterpriseDB http://www.enterprisedb.com Mail sent from my BlackLaptop device