From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Techie *EXTERN*" <techchavez(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PITR WAL Restore and configuration |
Date: | 2014-08-04 07:35:52 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17D22E7F@ntex2010i.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Techie wrote:
> Thanks man, I think I understand after re-reading the PITR WAL documentation a little better. I think that I need the WAL log or logs mentioned in the .backup file.
> So for example when I run the pg_start_bkup and pg_stop_backup It outputs something like this into the .backup file
>
> START WAL LOCATION: 111/CD000020 (file 0000000200000111000000CD)
> STOP WAL LOCATION: 111/CD0000A8 (file 0000000200000111000000CD)
[...]
> This means that in ordrt to restore this base backup I need the contents of the base backup and this WAL log 0000000200000111000000CD, is that correct?
Yes.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Rural Hunter | 2014-08-04 10:12:35 | Re: Very slow planning performance on partition table |
Previous Message | Rural Hunter | 2014-08-04 07:23:11 | Re: Very slow planning performance on partition table |