Re: Incorrect result of bitmap heap scan.

From: Andres Freund <andres(at)anarazel(dot)de>
To: "Core Studios Inc(dot)" <corestudiosinc(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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>
Subject: Re: Incorrect result of bitmap heap scan.
Date: 2025-09-16 12:25:42
Message-ID: 745E01F7-E62F-491D-963A-B0793AEDA9F5@anarazel.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On September 16, 2025 7:57:54 AM EDT, "Core Studios Inc." <corestudiosinc(at)gmail(dot)com> wrote:
>Hello,
>
>We noticed a sustained increased in IO Wait of read queries after upgrading from 13.13 to 13.21. Eventually, we narrowed it down to a spike in index_blocks_read of a certain table where Bitmap Heap Scans do happen.
>
>Do you think that this change (i.e. removing the optimization) could be what caused this regression?

You're not providing enough details for us to answer that question. We'd need an explain verbose for the query.

Greetings,

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-09-16 12:32:17 Re: Improving the names generated for indexes on expressions
Previous Message shveta malik 2025-09-16 12:12:42 Re: Improve pg_sync_replication_slots() to wait for primary to advance