Re: Index plan returns different results to sequential scan

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: John Burns <john(at)impactdatametrics(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Index plan returns different results to sequential scan
Date: 2024-03-22 01:40:05
Message-ID: CAH2-Wzmyevb7yfM0MkmvWQKA8Pah=SSotRJf=LTw1upihhgtZQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Mar 21, 2024 at 9:22 PM Tomas Vondra
<tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
> I don't know what the problem is, or whether it's a big in PG or in the
> postcode extension (I agree the extension is fairly straightforward).

Could you try running amcheck's bt_index_check function against the index?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message John Burns 2024-03-22 05:42:42 Re: Index plan returns different results to sequential scan
Previous Message Tomas Vondra 2024-03-22 01:21:49 Re: Index plan returns different results to sequential scan