Re: [COMMITTERS] pgsql: Remove secondary checkpoint - Mailing list pgsql-committers

From Michael Paquier
Subject Re: [COMMITTERS] pgsql: Remove secondary checkpoint
Date
Msg-id CAB7nPqRV-aROBqA+GfEaa33M7PiVoO5w8zw8eWmgkUntG=w+-Q@mail.gmail.com
Whole thread Raw
List pgsql-committers
On Wed, Nov 8, 2017 at 4:43 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andres Freund <andres@anarazel.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


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

pgsql-committers by date:

Previous
From: pgsql@postgresql.org
Date:
Subject: [COMMITTERS] pgsql: Tag refs/tags/REL9_5_10 was created
Next
From: Peter Eisentraut
Date:
Subject: [COMMITTERS] pgsql: Expand empty end tag