Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory - Mailing list pgsql-admin

From girish R G peetle
Subject Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory
Date
Msg-id CAKKd064HC4p84vXq3ns8FSr0eRJ3DqWGG8bvrpNVNtaq0EM6Mg@mail.gmail.com
Whole thread Raw
In response to Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-admin
Thanks a lot Laurenz Albe. 


On Wed, Jun 19, 2013 at 6:16 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
girish R G peetle wrote:
> I was wondering if I can use the modified version of your solution.
>
>  1. Convert output of pg_stop_backup to transaction log file name. (This refers to the latest active
> transaction log file)
>  2. If we are able to see this file under archive(WAL) directory, backup this file from this
> directory.
>  3. If the file is not found under archive(WAL) directory, backup this file form pg_xlog directory.

That should work just fine.

Yours,
Laurenz Albe

pgsql-admin by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory
Next
From: francis picabia
Date:
Subject: Re: Concrete steps for use of PITR warm backup?