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 bb9cf18a-c83c-4857-b3f0-4566918b0249@enterprisedb.com
Whole thread Raw
In response to Re: Index plan returns different results to sequential scan  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Index plan returns different results to sequential scan  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
List pgsql-bugs
On 3/22/24 02:40, Peter Geoghegan wrote:
> On Thu, Mar 21, 2024 at 9:22 PM Tomas Vondra
> <tomas.vondra@enterprisedb.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?
> 

I tried (on master). It doesn't report anything:

test=# select bt_index_check('xxx_postcode_idx', 't');
 bt_index_check
----------------

(1 row)

I also tried looking at the index using bt_page_items from pageinspect,
and I did not notice anything obviously wrong. But I don't have much
experience with btree at such low level ...


regards

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



pgsql-bugs by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded
Next
From: Wolfgang Walther
Date:
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded