From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: PITR Archive Recovery plus WIP PITR |
Date: | 2004-07-14 07:15:10 |
Message-ID: | 1089789310.17493.3876.camel@stromboli |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Wed, 2004-07-14 at 05:45, 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.
>
I agree, but I'm going to have a rest day while people test what is
already there in case there are further code changes....which nods
towards both of your concerns.
BTW, one test last night broke because of the lack of timelines...
Best Regards, Simon Riggs
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2004-07-14 07:21:22 | Re: [HACKERS] Point in Time Recovery |
Previous Message | Christopher Kings-Lynne | 2004-07-14 07:08:18 | Re: Fixes for 3 bugs in pg_dump |