Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory

From: girish R G peetle <giri(dot)anamika0(at)gmail(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory
Date: 2013-06-19 11:36:12
Message-ID: CAKKd065jM=sySoac+TaqLqqhv-3Nz9juhpGyHhwz59LKjp_vNg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, Jun 19, 2013 at 4:32 PM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Albe Laurenz 2013-06-19 12:46:36 Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory
Previous Message Albe Laurenz 2013-06-19 11:02:14 Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory