pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Peter Geoghegan <pg@bowt.ie>
Cc: John Burns <john@impactdatametrics.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Index plan returns different results to sequential scan
Date: Fri, 22 Mar 2024 08:43:45 +0100
Message-ID: <bb9cf18a-c83c-4857-b3f0-4566918b0249@enterprisedb.com> (raw)
In-Reply-To: <CAH2-Wzmyevb7yfM0MkmvWQKA8Pah=SSotRJf=LTw1upihhgtZQ@mail.gmail.com>
References: <3B86F188-F4BF-4331-AD79-E5FF2D0711A3@impactdatametrics.com>
	<72600f8a-4231-45b7-a116-8ceec5ccf66e@enterprisedb.com>
	<881DF028-5222-486C-A13B-451239C1316F@impactdatametrics.com>
	<27496161-e7ec-47bd-b559-3571fde4dcb4@enterprisedb.com>
	<b4ee59ca-a99a-474f-97cc-b26d4ce51e43@enterprisedb.com>
	<CAH2-Wzmyevb7yfM0MkmvWQKA8Pah=SSotRJf=LTw1upihhgtZQ@mail.gmail.com>

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

view thread (10+ messages)  latest in thread

Message-ID: <bb9cf18a-c83c-4857-b3f0-4566918b0249@enterprisedb.com>
Permalink:  ../bb9cf18a-c83c-4857-b3f0-4566918b0249@enterprisedb.com/
Also on:    postgresql.org/message-id/bb9cf18a-c83c-4857-b3f0-4566918b0249@enterprisedb.com

copy link · copy postgr.es

reply

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, pg@bowt.ie, john@impactdatametrics.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: Index plan returns different results to sequential scan
  In-Reply-To: <bb9cf18a-c83c-4857-b3f0-4566918b0249@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