| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup from cascading standby after timeline switch |
| Date: | 2012-12-18 18:21:14 |
| Message-ID: | 11428.1355854874@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> On Tue, Dec 18, 2012 at 8:09 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> What I'm saying is that the new history file is created from the old
>> one, so the latest file includes all the history as a direct copy. The
>> only thing new is one line of information.
> The timeline history file includes only ancestor timelines history. So
> the latest one might not include all the history.
Indeed. And even if there are a thousand of them, so what? It'd still
be less space than a single WAL segment file.
Better to keep the data than wish we had it later.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-12-18 18:24:12 | Re: [ADMIN] Problems with enums after pg_upgrade |
| Previous Message | Fujii Masao | 2012-12-18 18:06:53 | Re: Error restoring from a base backup taken from standby |