On Wed, Jun 4, 2025 at 7:33 AM Tomas Vondra <to...@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
