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 ksu5dtbmpvdolwuu2ubq745qbvg4mk2jpwu527autrftpsm6im@lifqp5icoyyi
Whole thread Raw
In response to Re: Incorrect result of bitmap heap scan.  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
Responses Re: Incorrect result of bitmap heap scan.
List pgsql-hackers
Hi,

On 2025-03-17 16:17:03 +0100, Matthias van de Meent wrote:
> As I understand it, Andres agrees that the feature is unsalvageable in
> backbranches ("don't think there's a realistic way to fix it"). Andres
> then continues to elaborate that even if the feature were salvageable,
> it wouldn't contain much of the current code.

Correct.


> My patch removes the feature altogether in master and disables the
> feature in the backbranches in the patches that were built against the
> backbranches, which seems to match Andres' comments.

Agreed.


> @vignesh, could you elaborate on what about Andres' comments I need to
> address in my patch?

I don't think there are any...

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Daniil Davydov
Date:
Subject: Re: Forbid to DROP temp tables of other sessions
Next
From: Robert Haas
Date:
Subject: Re: pgsql: pg_upgrade: Preserve default char signedness value from old clus