postgresql/contrib/bloom
Tom Lane 7d1aa6bf1c Re-enable contrib/bloom's TAP tests.
These tests were disabled back in 2018 (commit d3c09b9b1) because of
failures observed in the buildfarm.  I've not been able to reproduce
any failure on longfin's host, though, so I'm curious whether or to
what extent we've fixed the problem.  Let's re-enable it (in HEAD
only) and see what blows up.

Discussion: https://postgr.es/m/2769443.1632773967@sss.pgh.pa.us
2021-09-27 18:48:01 -04:00
..
expected Fix failure with lock mode used for custom relation options 2019-09-25 10:07:23 +09:00
sql Fix failure with lock mode used for custom relation options 2019-09-25 10:07:23 +09:00
t Unify PostgresNode's new() and get_new_node() methods 2021-07-29 05:58:08 -04:00
.gitignore Bloom index contrib module 2016-04-01 16:42:24 +03:00
blcost.c Update copyright for 2021 2021-01-02 13:06:25 -05:00
blinsert.c Replace RelationOpenSmgr() with RelationGetSmgr(). 2021-07-12 17:01:36 -04:00
bloom--1.0.sql Minor fixes in contrib installation scripts. 2016-06-14 10:47:06 -04:00
bloom.control Bloom index contrib module 2016-04-01 16:42:24 +03:00
bloom.h Pass down "logically unchanged index" hint. 2021-01-13 08:11:00 -08:00
blscan.c Update copyright for 2021 2021-01-02 13:06:25 -05:00
blutils.c Remove redundant memset(0) calls for page init of some index AMs 2021-04-07 14:35:26 +09:00
blvacuum.c Update copyright for 2021 2021-01-02 13:06:25 -05:00
blvalidate.c Update copyright for 2021 2021-01-02 13:06:25 -05:00
Makefile Re-enable contrib/bloom's TAP tests. 2021-09-27 18:48:01 -04:00