Re: Index plan returns different results to sequential scan - Mailing list pgsql-bugs

From Tomas Vondra
Subject Re: Index plan returns different results to sequential scan
Date
Msg-id 72600f8a-4231-45b7-a116-8ceec5ccf66e@enterprisedb.com
Whole thread Raw
In response to Index plan returns different results to sequential scan  (John Burns <john@impactdatametrics.com>)
List pgsql-bugs
On 3/21/24 18:25, John Burns wrote:
> Hi…
> 
> ...
> 
> Although the postcode package is probably not especially significant
> in the scheme of things , the behaviour of indexed versus non-indexed
> queries is worrisome.
> 

Seems like a thinko in the indexing, but that's just a guess.

> I’ve had to make a couple of minor changes to the postcode package
> as the Postgres versions have changed, i.e. define TRUE and FALSE in
> the c header files and change the location of the include files when
> Postgres 16 arrived, but nothing else.
Can you share a patch with the tweaks?

> 
> I’ve attached a sample data file to populate a table that exhibits 
> the behaviour, and the tweaked version of the Postcode package.
> 

I don't see any attachments :-(


regards

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



pgsql-bugs by date:

Previous
From: John Burns
Date:
Subject: Index plan returns different results to sequential scan
Next
From: Wolfgang Walther
Date:
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded