From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
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 07:43:45 |
Message-ID: | bb9cf18a-c83c-4857-b3f0-4566918b0249@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 3/22/24 02:40, Peter Geoghegan wrote:
> 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?
>
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
From | Date | Subject | |
---|---|---|---|
Next Message | Wolfgang Walther | 2024-03-22 07:55:52 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
Previous Message | Andrew Dunstan | 2024-03-22 07:02:19 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |