From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Remove secondary checkpoint |
Date: | 2017-11-07 19:14:15 |
Message-ID: | 20171107191415.ubl7klakaxy6eu6z@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 2017-11-07 14:12:19 -0500, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2017-11-07 17:57:31 +0000, Simon Riggs wrote:
> >> Remove secondary checkpoint
>
> > FWIW, I don't think this should be applied without a pg_resetxlog
> > feature allowing to manually use older checkpoints.
>
> Uh, what? We have never before insisted on pg_resetxlog being able
> to use WAL across a WAL format change, and there have been many of
> those.
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.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-11-07 19:43:00 | Re: pgsql: Remove secondary checkpoint |
Previous Message | Tom Lane | 2017-11-07 19:12:19 | Re: pgsql: Remove secondary checkpoint |