Re: Fix inconsistencies with code and beautify xlog structures description and fin hash_xlog.h

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Kirill Reshke <reshkekirill(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix inconsistencies with code and beautify xlog structures description and fin hash_xlog.h
Date: 2025-09-11 07:55:14
Message-ID: aMKAYgTeoPPg_xsc@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 10, 2025 at 05:36:48PM +0500, Andrey Borodin wrote:
> Proposed change is correct and in line with a description of
> e.g. XLOG_HASH_MOVE_PAGE_CONTENTS.
> I'd note that block is for lock only and record does not include
> image, but other such cases are not reported in comments.

Right, the case of block 0 being registered in a MOVE_PAGE_CONTENTS
record to ensure that a cleanup lock is taken is documented in
_hash_squeezebucket()@hashovfl.c, for SQUEEZE_PAGE, or for DELETE.
Squeeze can also do that for buffer 1.

On top of your suggestions, I have double-checked the rest of the hash
records, and they seem to be in line with hash_xlog.h. Will fix,
thanks.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shubham Khanna 2025-09-11 08:11:11 Re: Add support for specifying tables in pg_createsubscriber.
Previous Message Zsolt Parragi 2025-09-11 07:42:25 Re: OAuth client code doesn't work with Google OAuth