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

From Core Studios Inc.
Subject Re: Incorrect result of bitmap heap scan.
Date
Msg-id bd5ea69b-2b96-42b7-998a-13554983b3c5@gmail.com
Whole thread Raw
In response to Re: Incorrect result of bitmap heap scan.  (Andres Freund <andres@anarazel.de>)
Responses Re: Incorrect result of bitmap heap scan.
List pgsql-hackers
Following up to correct my previous email: the query plan did not really 
change - we see Bitmap Heap Scans even before the upgrade. Therefore, 
the query plan doesn't seem to have changed after the upgrade.

However after the upgrade it seems that those queries are doing more 
disk IO (increased index_blocks_read in that table).

Thanks in advance


On 9/16/25 3:25 PM, Andres Freund wrote:
> Hi,
>
> On September 16, 2025 7:57:54 AM EDT, "Core Studios Inc." <corestudiosinc@gmail.com> wrote:
>> Hello,
>>
>> We noticed a sustained increased in IO Wait of read queries after upgrading from 13.13 to 13.21. Eventually, we
narrowedit 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Improving the names generated for indexes on expressions
Next
From: Greg Burd
Date:
Subject: Re: [PATCH] Add tests for Bitmapset