Re: PITR problem

> 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 command is:
-----------------------------------------------------------------------------------------
restore_command = 'pg_standby -l -d -s 5 -w 0 -t /tmp/
pgsql.promote_trigger.5432 ~postgres/incoming_wal %f %p %r 2>&1 |
logger -p local1.info -t pitr-standby'
-----------------------------------------------------------------------------------------

As you can see I didn't set -k to keep fixed number of WALs, but %r
parameter and the PostgreSQL controls number of keeped files
automatically (or at least it should)