From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
---|---|
To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Alexander Lakhin <exclusion(at)gmail(dot)com> |
Cc: | Andrey Borodin <amborodin86(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Jose Arthur Benetasso Villanova <jose(dot)arthur(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Amcheck verification of GiST and GIN |
Date: | 2024-07-12 18:16:42 |
Message-ID: | 1f01738f-0708-4b89-ab09-4a623e569efc@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
OK, one more issue report. I originally thought it's a bug in my patch
adding parallel builds for GIN indexes, but it turns out it happens even
with serial builds on master ...
If I build any GIN index, and then do gin_index_parent_check() on it, I
get this error:
create index jsonb_hash on messages using gin (msg_headers jsonb_path_ops);
select gin_index_parent_check('jsonb_hash');
ERROR: index "jsonb_hash" has wrong tuple order, block 43932, offset 328
I did try investigating usinng pageinspect - the page seems to be the
right-most in the tree, judging by rightlink = InvalidBlockNumber:
test=# select gin_page_opaque_info(get_raw_page('jsonb_hash', 43932));
gin_page_opaque_info
----------------------
(4294967295,0,{})
(1 row)
But gin_leafpage_items() apparently only works with compressed leaf
pages, so I'm not sure what's in the page. In any case, the index seems
to be working fine, so it seems like a bug in this patch.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2024-07-12 19:18:37 | Re: Restart pg_usleep when interrupted |
Previous Message | Andres Freund | 2024-07-12 17:45:32 | Re: gcc 13 warnings |