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 CAKKd065jM=sySoac+TaqLqqhv-3Nz9juhpGyHhwz59LKjp_vNg@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>)
Responses Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-admin

On Wed, Jun 19, 2013 at 4:32 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
girish R G peetle wrote:
> @Albe
> Even I was thinking to backup the transaction log files under pg_xlog directory. But my concern is,
> will it lead some kind of error or inconsistency ?

No.
During recovery, archived WAL files will overwrite the ones in
pg_xlog.  The WAL files in pg_xlog will only be used if
no archived version is available.

As long as pg_xlog is backed up after the end of
pg_stop_backup(), you should be safe.

Yours,
Laurenz Albe



Hi Laurenz Albe,
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.


Thanks
Girish

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: Albe Laurenz
Date:
Subject: Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory