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

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "girish R G peetle *EXTERN*" <giri(dot)anamika0(at)gmail(dot)com>
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 12:46:36
Message-ID: A737B7A37273E048B164557ADEF4A58B17BB4633@ntex2010a.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message girish R G peetle 2013-06-19 12:50:37 Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory
Previous Message girish R G peetle 2013-06-19 11:36:12 Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory