Re: Index plan returns different results to sequential scan

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: John Burns <john(at)impactdatametrics(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Index plan returns different results to sequential scan
Date: 2024-03-21 23:58:09
Message-ID: 27496161-e7ec-47bd-b559-3571fde4dcb4@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 3/21/24 21:08, John Burns wrote:
>
>
>> On 21 Mar 2024, at 20:27, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
>>
>>
>> Sorry about that … the patched version of the package, plus a sample data set is in the attached zip file,
>>
>> -John
>>

Thanks, I can reproduce the issue. I don't know why is it happening, but
the behavior I see is that the (postcode % 'NW10') query somehow misses
rows with postcodes 'NW10 0AA' - 'NW10 3NL' when executed using index.

I don't see anything obviously wrong in the extension / index pages.

You suggested it used to work OK and then broke. Do you perhaps know at
which version it broke? Or did you use 9.x until now, upgrades to 16 and
realized it's broken?

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2024-03-22 00:07:14 Re: Regression tests fail with musl libc because libpq.so can't be loaded
Previous Message Tom Lane 2024-03-21 23:30:52 Re: Regression tests fail with musl libc because libpq.so can't be loaded