From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: PITR Archive Recovery plus WIP PITR |
Date: | 2004-07-14 04:45:10 |
Message-ID: | 22534.1089780310@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> I think that judgment is exactly backward. *Not* having timelines is
>> what will cause serious and possibly fatal mistakes during restore:
>> people will hand the wrong xlog files to restore and the software will
>> be unable to recognize the inconsistency.
> I assume they could just restore from backup and try again.
Sure, if they don't mind losing whatever transactions they processed
before realizing how broken their database was. That's not going to be
an acceptable answer for the sort of installations that need PITR in the
first place.
I think it's really important to get this right the first time, both for
reliability's sake and because we are expecting people to write their
own archiving scripts. If we change the xlog segment naming convention
later on, then we will break all those scripts.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-07-14 06:14:39 | Fixes for 3 bugs in pg_dump |
Previous Message | Bruce Momjian | 2004-07-14 04:36:04 | Re: PITR Archive Recovery plus WIP PITR |