On 29 Kwi, 17:16, [EMAIL PROTECTED] (Erik Jones) wrote:
> On Apr 29, 2008, at 3:20 AM, wstrzalka wrote:
>
>
>
> >> What is the full pg_standby command string (restore_command=) in
> >> your recovery.conf. It sound's like you have pg_standby set to
> >> delete
> >> archived WALs and possibly ha
On Apr 29, 2008, at 3:20 AM, wstrzalka wrote:
What is the full pg_standby command string (restore_command=) in
your recovery.conf. It sound's like you have pg_standby set to
delete
archived WALs and possibly have that a little too aggressive. Do you
have the -k flag set in your pg_stan
> What is the full pg_standby command string (restore_command=) in
> your recovery.conf. It sound's like you have pg_standby set to delete
> archived WALs and possibly have that a little too aggressive. Do you
> have the -k flag set in your pg_standby call in your restore_command?
My restore
On Apr 26, 2008, at 5:11 PM, wstrzalka wrote:
I have some problem with setting up PITR recovery on the database.
I have archive_command set properly and logs are shipping OK. Archive
timeout is also set (5 min).
When performing pg_start_backup the WAL is lets say on position
000100010
I have some problem with setting up PITR recovery on the database.
I have archive_command set properly and logs are shipping OK. Archive
timeout is also set (5 min).
When performing pg_start_backup the WAL is lets say on position
0001000100D9, then I start copy database to the second
