Re: Remove secondary checkpoint

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove secondary checkpoint
Date: 2017-10-30 14:31:24
Message-ID: CAB7nPqQCRMZirimcCog0JPAkNnnQ6gtFwu5HfgZYmZke_16R9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 30, 2017 at 2:22 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 25 October 2017 at 00:17, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>> - * Delete old log files (those no longer needed even for previous
>> - * checkpoint or the standbys in XLOG streaming).
>> + * Delete old log files and recycle them
>> */
>> Here that's more "Delete or recycle old log files". Recycling of a WAL
>> segment is its renaming into a newer segment.
>
> Sometimes files are deleted if there are too many.

Sure, but one segment is never deleted and then recycled, which is
what your new comment implies as I understand it.

>> - checkPointLoc = ControlFile->prevCheckPoint;
>> + /*
>> + * It appears to be a bug that we used to use
>> prevCheckpoint here
>> + */
>> + checkPointLoc = ControlFile->checkPoint;
>> Er, no. This is correct because we expect the prior checkpoint to
>> still be present in the event of a failure detecting the latest
>> checkpoint.
>
> I'm removing "prevCheckPoint", so not sure what you mean.

I mean that there is no actual bug here. And changing the code as you
do is correct, but the comment is not.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-10-30 14:40:50 Re: How to implement a SP-GiST index as a extension module?
Previous Message Simon Riggs 2017-10-30 14:22:31 Re: Remove secondary checkpoint