From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Woody Woodring" <george(dot)woodring(at)iglass(dot)net> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Pg_standby and shutting down the warm standby |
Date: | 2007-06-18 20:36:19 |
Message-ID: | 1182198979.6855.264.camel@silverbirch.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2007-06-18 at 13:26 -0400, Woody Woodring wrote:
> I am wondering if there is a proper procedure for shutting down the
> warm_standby server (8.2.4)? I am using pg_standby as my restore script in
> my testing:
>
> [postgres(at)jbeam]$ cat recovery.conf
> restore_command = 'pg_standby -m -d -s 5 -w 0 -t /tmp/pgsql.trigger.5432
> /usr/local2/pg_archive %f %p 2>> standby.log'
>
> My issue is it looks like the when the warm_standby comes back up, it is
> looking for a file that has already been loaded (and deleted). It was
> looking for log '*30' when it was shut down, but upon startup again it is
> looking for '*2F'.
The -m command is not supported in the most recent version of pg_standby
because it results in the error your point out. The latest version has a
-k option that works around this error and a server patch is in the
queue for 8.3 that will allow a more flexible approach to this.
I'll add a --version option to pg_standby to allow us to discuss which
version is in use, to avoid such issues in future. Thanks,
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-06-18 20:44:41 | Re: Apparent Wraparound? |
Previous Message | g.hintermayer | 2007-06-18 20:28:17 | Re: Apparent Wraparound? |