Horton

Re: Vectorize pg_visibility.pg_visibility_map_summary

Matthias van de Meent <boekewurm+postgres@gmail.com>

View thread
From: Matthias van de Meent <boekewurm+postgres@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Nathan Bossart <nathandbossart@gmail.com>, Ants Aasma <ants.aasma@cybertec.at>
Date: 2025-12-22T22:16:39Z
Lists: pgsql-hackers 
Hi,

On Mon, 22 Dec 2025 at 23:04, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> On Mon, Dec 22, 2025 at 1:28 PM Matthias van de Meent
> <boekewurm+postgres@gmail.com> wrote:
> > Here's one small patch that makes it use the visibilitymap_count() API
> > for pg_visibility_map_summary(), replacing its own bespoke counting
> > mechanism with the primary implementation that has vectorized
> > optimizations, thus reducing the overhead of
> > pg_visibility_map_summary.
> >
>
> It looks like a reasonable idea as it also simplifies the
> pg_visibility_map_summary() function. I'm going to push it, barring
> any objections.

Obviously no objections from me, and, thanks!


Kind regards,

Matthias van de Meent
Databricks (https://www.databricks.com)