Hi,
> this one is still open when I run pg_stop_backup(), so I want to trigger the
> archive_command to be sure that I don't miss anything.
I guess what you want is pg_switch_xlog() (see
http://www.postgresql.org/docs/8.2/static/functions-admin.html)
which became available with PG 8.2 ...
Tho
Hi Tom,
> >> I believe the intended way to do this is to look at pg_stop_backup's
> >> return value to determine the last segment you need to archive.
> > Thank you - I saw that, but I didn't have a clue about how to determine
> > the WAL filename in which this segment is to be found ...
> Well, t
Hi Tom,
> > My idea is now: When doing a consistent PITR backup, extend the
> > documented steps between 4 (pg_stop_backup()) and 5 (wait for archived
> > WAL file) with a busy wait on pg_xlog/archive_status/*.ready files - as
> > soon as no .ready files are there anymore, the archiver has done it
Dear list,
in the documentation
(http://www.postgresql.org/docs/8.2/interactive/continuous-archiving.html)
is written that after doing the filesystem based backup, I have to
invoke pg_stop_backup() which triggers an xlog switch, and in order to
have a consistent backup, I need to have the switched
