Re: Incorrect result of bitmap heap scan. - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Incorrect result of bitmap heap scan.
Date
Msg-id tf5pp2o2a5x5qjcseq354bd26ya4o7p2vjzm5z4w57ca3vy6bc@ep7enrljvdkr
Whole thread Raw
In response to Re: Incorrect result of bitmap heap scan.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2025-03-01 19:35:15 -0500, Tom Lane wrote:
> Peter Geoghegan <pg@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.

I don't think there's a realistic way to fix it in the backbranches. And even
on master, I doubt that much of the current code would survive.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: per backend WAL statistics
Next
From: "Daniel Verite"
Date:
Subject: Re: Add Pipelining support in psql