From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(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 14:50:55 |
Message-ID: | 200407141450.i6EEotI08466@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
> 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.
We don't have anything hardcoded based on those file names, at last in
PostgreSQL.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-07-14 15:00:39 | Re: PITR Archive Recovery plus WIP PITR |
Previous Message | Bruce Momjian | 2004-07-14 14:50:03 | Re: serverlog rotation/functions |