From: | Tim Uckun <timuckun(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | A question about pg_standby. |
Date: | 2009-07-24 03:42:10 |
Message-ID: | 855e4dcf0907232042v63cdbfa7pd2a20135eaaab142@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am using pg_standby to set up a warm standby.
Everything seems to be working OK so far but I do have one question.
I wanted to check to make sure that the replication was happening so I
created the trigger file which put the database to "live"mode. I ran
a query on the standby to make sure the new data was there. I
re-created the recovery.conf file and restarted the postgres server.
The server went back into the standby mode but now it's confused and
wants to keep all archive files. The log file says
Keep archive history : 000000000000000000000000 and later
So it looks like it's applying the log files but not deleting the old ones.
What's the best way to "pause" the log shipping and restart it later?
Thanks.
From | Date | Subject | |
---|---|---|---|
Next Message | tomrevam | 2009-07-24 03:53:41 | Re: synchronous_commit=off doesn't always return immediately |
Previous Message | Alexandr Varlamov | 2009-07-24 03:13:29 | service stopping and pg_standby on windows |