On Sat, Mar 12, 2016 at 12:38 PM, Peter Geoghegan <p...@heroku.com> wrote: > Only insofar as it helps diagnose the underlying issue, when it is a > more subtle issue. Actually fixing the index is almost certainly a > REINDEX. Once you're into the messy business of diagnosing a > problematic opclass, you have to be an expert, and tweaking amcheck > for your requirements (i.e. rebuilding from source) becomes > reasonable. Part of the reason that the code is so heavily commented > is to make it hackable, because I do not feel optimistic that I can > get an expert-orientated interface right, but I still want to make the > tool as useful as possible to experts.
Heroku began a selective roll-out of amcheck yesterday. amcheck already found a bug in the PostGiS Geography B-Tree opclass: https://github.com/postgis/postgis/blob/svn-trunk/postgis/geography_btree.c#L260 The issue is not that PG_RETURN_BOOL() is used here (that's just a problem of style). Rather, the issue is that the Geography opclass support function 1 considers an "empty geometry" equal to all other possible values (values not limited to other empty geometries). This breaks the transitive law, which nbtree requires and relies on. I'll go report this to the PostGiS people. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
