| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Recovery target 'immediate' |
| Date: | 2013-04-26 12:41:10 |
| Message-ID: | CA+U5nMK6K8tMXEad_tzy2HdtEcFppiTYOyO0Z4YFnuk0ySMG-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 26 April 2013 12:54, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> That said, maybe the easier choice for a *system* (such as v-thingy)
> would be to simply to the full backup using pg_basebackup -x (or
> similar), therefor not needing the log archive at all when restoring.
> Yes, it makes the base backup slightly larger, but also much
> simpler... As a bonus, your base backup would still work if you hosed
> your log archive.
Good point. My comments also apply there.
I think we should put a clear health warning on that to explain what
you get and don't get.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-04-26 12:51:23 | Re: pg_controldata gobbledygook |
| Previous Message | Magnus Hagander | 2013-04-26 11:54:43 | Re: Recovery target 'immediate' |