On Sun, 2 Mar 2025 at 01:35, Tom Lane <t...@sss.pgh.pa.us> wrote:
>
> Peter Geoghegan <p...@bowt.ie> writes:
> > Is everybody in agreement about committing and back patching this fix,
> > which simply disables the optimization altogether?
> > I myself don't see a better way, but thought I'd ask before proceeding
> > with review and commit.
>
> If you don't see a clear path forward, then "disable" is the only
> reasonable choice for the back branches.  Maybe we'll find a fix
> in future, but it seems unlikely that it'd be back-patchable.

Agreed.

Here's patch v5 for the master branch (now up to f4694e0f), with no
interesting changes other than fixing apply conflicts caused by
bfe56cdf.

Kind regards,

Matthias van de Meent
Neon (https://neon.tech)

Attachment: v5-0002-isolationtester-showing-broken-index-only-bitmap-.patch
Description: Binary data

Attachment: v5-0001-Remove-HeapBitmapScan-s-skip_fetch-optimization.patch
Description: Binary data

Reply via email to