Re: strange perf regression with data checksums - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: strange perf regression with data checksums
Date
Msg-id CAH2-WznUWysOeHEZ7YnQrZDbWzaF=+gnn+-vi5bvK3Dnxj-g6Q@mail.gmail.com
Whole thread Raw
In response to Re: strange perf regression with data checksums  (Tomas Vondra <tomas@vondra.me>)
Responses Re: strange perf regression with data checksums
List pgsql-hackers
On Wed, Jun 4, 2025 at 7:33 AM Tomas Vondra <tomas@vondra.me> wrote:
> So better to get this in now, otherwise we may have to wait until PG19,
> because of ABI (the patch adds a field into BTScanPosData, but maybe
> it'd be possible to add it into padding, not sure).

I agree. I can get this into shape for commit today.

Does anybody object to my proceeding with committing the patch on the
master branch/putting it in Postgres 18?  (FWIW I could probably fit
the new field into some BTScanPosData alignment padding, but I don't
favor back patching.)

I consider my patch to be low risk. There's a kind of symmetry to how
things work with the patch in place, which IMV makes things simpler.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Oleg Tselebrovskiy
Date:
Subject: Cluster.pm psql() undefined $$stderr
Next
From: Fujii Masao
Date:
Subject: Add tab-completion for ALTER TABLE ADD NOT NULL