| 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 12:50:37 |
| Message-ID: | CAKKd064HC4p84vXq3ns8FSr0eRJ3DqWGG8bvrpNVNtaq0EM6Mg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thanks a lot Laurenz Albe.
On Wed, Jun 19, 2013 at 6:16 PM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | francis picabia | 2013-06-19 13:09:23 | Re: Concrete steps for use of PITR warm backup? |
| Previous Message | Albe Laurenz | 2013-06-19 12:46:36 | Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory |