Test all contrib-created operator classes with amvalidate.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 29 Nov 2016 20:05:22 +0000 (15:05 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 29 Nov 2016 20:05:22 +0000 (15:05 -0500)
commitade49c605f1d8f517497829363f8b83f69c73a60
tree95ac16d5feb33f0fc017c2973e5afee303cdfd95
parent11da83a0e70d32ed0e06a5c948cd8343f8ad5102
Test all contrib-created operator classes with amvalidate.

I'd supposed that people would do this manually when creating new operator
classes, but the folly of that was exposed today.  The tests seem fast
enough that we can just apply them during the normal regression tests.

contrib/isn fails the checks for lack of complete sets of cross-type
operators.  That's a nice-to-have policy rather than a functional
requirement, so leave it as-is, but insert ORDER BY in the query to
ensure consistent cross-platform output.

Discussion: https://postgr.es/m/7076.1480446837@sss.pgh.pa.us
25 files changed:
contrib/btree_gin/expected/install_btree_gin.out
contrib/btree_gin/sql/install_btree_gin.sql
contrib/btree_gist/expected/init.out
contrib/btree_gist/sql/init.sql
contrib/citext/expected/citext.out
contrib/citext/expected/citext_1.out
contrib/citext/sql/citext.sql
contrib/cube/expected/cube.out
contrib/cube/expected/cube_2.out
contrib/cube/sql/cube.sql
contrib/hstore/expected/hstore.out
contrib/hstore/sql/hstore.sql
contrib/intarray/expected/_int.out
contrib/intarray/sql/_int.sql
contrib/isn/expected/isn.out
contrib/isn/sql/isn.sql
contrib/ltree/expected/ltree.out
contrib/ltree/sql/ltree.sql
contrib/pg_trgm/expected/pg_trgm.out
contrib/pg_trgm/sql/pg_trgm.sql
contrib/seg/expected/seg.out
contrib/seg/expected/seg_1.out
contrib/seg/sql/seg.sql
contrib/tsearch2/expected/tsearch2.out
contrib/tsearch2/sql/tsearch2.sql