From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Display is_prev_bucket_same_wrt of xl_hash_squeeze_page |
Date: | 2025-09-11 00:54:00 |
Message-ID: | aMIdqPKKEm6ctZTR@paquier.xyz |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2025-09-11 01:16:58 | Re: Stale comment in guc.h; publish listing of setting sources? |
Previous Message | Euler Taveira | 2025-09-11 00:11:36 | Re: Proposal: GUC to control starting/stopping logical subscription workers |