On Thu, 2007-10-11 at 16:37 +0200, Thomas Karcher wrote:
> 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
> >
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
Thomas Karcher <[EMAIL PROTECTED]> writes:
>> 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 i
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
Thomas Karcher <[EMAIL PROTECTED]> writes:
> 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
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
