| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Kuzmenkov <akuzmenkov(at)timescale(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Incorrect result of bitmap heap scan. |
| Date: | 2025-03-02 00:32:05 |
| Message-ID: | CAH2-Wz=Prv5buOehZnVrkk24nVn5xDQFXJ9=L8y0PhKzPCnSJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 28, 2025 at 12:53 PM Matthias van de Meent
<boekewurm+postgres(at)gmail(dot)com> wrote:
> Rebased again, now on top of head due to f7a8fc10.
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.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-02 00:35:15 | Re: Incorrect result of bitmap heap scan. |
| Previous Message | Tom Lane | 2025-03-01 23:54:21 | Re: bug when apply fast default mechanism for adding new column over domain with default value |