| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup from cascading standby after timeline switch |
| Date: | 2012-12-17 22:44:08 |
| Message-ID: | CA+U5nMJN9G9Uy9LON2CXw0O2YRaV1Sw2-5xGjjoV1cW5=F12EA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17 December 2012 14:16, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
> I'm not happy with the fact that we just ignore the problem in a backup
> taken from a standby, silently giving the user a backup that won't start up.
That's spooky. I just found a different issue with prmotion during
backup on your other thread.
> Why not include the timeline history file in the backup? That seems like a
> good idea regardless of this issue.
Yeh
> I also wonder if pg_basebackup should
> include *all* timeline history files in the backup, not just the latest one
> strictly required to restore.
Why? the timeline history file includes the previous timelines already.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-12-17 22:55:11 | Re: XLByte* usage |
| Previous Message | Simon Riggs | 2012-12-17 22:35:43 | Re: Error restoring from a base backup taken from standby |