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

From Kirill Reshke
Subject Re: Display is_prev_bucket_same_wrt of xl_hash_squeeze_page
Date
Msg-id CALdSSPjGqCWJ=QizMPkXUvf-uZhTeNT6AC1j2hh2G5=C3jYfQw@mail.gmail.com
Whole thread Raw
In response to Re: Display is_prev_bucket_same_wrt of xl_hash_squeeze_page  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
HI, thanks for looking into this.

On Thu, 11 Sept 2025 at 05:54, Michael Paquier <michael@paquier.xyz> wrote:

> 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.

Yes. I guess we might want to implement this to keep things in sync:
we display dead/redirected tuple offsets in PRUNE VACUUM SCAN output
already, so maybe just display here too, this is also vacuum.

> 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.


Sure

PFA v2.

-- 
Best regards,
Kirill Reshke

Attachment

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Adding basic NUMA awareness
Next
From: "Vitaly Davydov"
Date:
Subject: ALTER DATABASE RESET with unexistent guc doesn't report an error