From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: John Burns <john@impactdatametrics.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: Index plan returns different results to sequential scan
Date: Thu, 21 Mar 2024 20:27:00 +0100
Message-ID: <72600f8a-4231-45b7-a116-8ceec5ccf66e@enterprisedb.com> (raw)
In-Reply-To: <3B86F188-F4BF-4331-AD79-E5FF2D0711A3@impactdatametrics.com>
References: <3B86F188-F4BF-4331-AD79-E5FF2D0711A3@impactdatametrics.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tomas.vondra@enterprisedb.com, john@impactdatametrics.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Index plan returns different results to sequential scan
In-Reply-To: <72600f8a-4231-45b7-a116-8ceec5ccf66e@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox