Re: Display is_prev_bucket_same_wrt of xl_hash_squeeze_page - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Display is_prev_bucket_same_wrt of xl_hash_squeeze_page
Date
Msg-id aMIdqPKKEm6ctZTR@paquier.xyz
Whole thread Raw
In response to Display is_prev_bucket_same_wrt of xl_hash_squeeze_page  (Kirill Reshke <reshkekirill@gmail.com>)
Responses Re: Display is_prev_bucket_same_wrt of xl_hash_squeeze_page
List pgsql-hackers
On Wed, Sep 10, 2025 at 06:28:10PM +0500, Kirill Reshke wrote:
> While doing some xlog-related task at my job I noticed that pg_waldump
> utility does not display `is_prev_bucket_same_wrt` of
> xl_hash_squeeze_page record. I had to patch pg_waldump to fix the
> issue, because I use pg_waldump output of vanilla pg to cross-check my
> patches (in our closed-source pg-related project).

Good idea.

We are still missing the offsets in xl_hash_vacuum_one_page, which
would lead to a longer output, with perhaps less value in in.

How about old_bucket_flag and new_bucket_flag in
xl_hash_split_allocate_page, as well as procid in
xl_hash_init_meta_page?  While we are looking at this area, we may as
well close the gap in the output produced.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: Proposal: GUC to control starting/stopping logical subscription workers
Next
From: Michael Paquier
Date:
Subject: Re: Stale comment in guc.h; publish listing of setting sources?