Re: pgsql: Remove secondary checkpoint

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Remove secondary checkpoint
Date: 2017-11-08 00:19:55
Message-ID: CAB7nPqRV-aROBqA+GfEaa33M7PiVoO5w8zw8eWmgkUntG=w+-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Nov 8, 2017 at 4:43 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> I think you misunderstand my point - I'm saying that pg_resetxlog should
>> be able to force the use of older checkpoints, basically as a fallback
>> to cases where the previous approach might actually have worked, not
>> that it needs to work across format changes.
>
> That seems like a completely separate feature --- and one of dubious
> value, frankly. The further back you go, the less likely it'd be
> to work.

Because the less guarantees you would have to reach a consistent point
with a non-corrupted instance. I think that Andres' idea here are
worth debating though. Why not just spawning a new thread on the
matter and summarize what you have in mind?
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-11-08 02:15:08 pgsql: Expand empty end tag
Previous Message pgsql 2017-11-07 23:03:44 pgsql: Tag refs/tags/REL9_4_15 was created