Re: pgsql: Bloom index contrib module

Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
> Bloom index contrib module

skink provided some pretty suggestive evidence about why this
is unstable:

==32446== VALGRINDERROR-BEGIN
==32446== Conditional jump or move depends on uninitialised value(s)
==32446== at 0x4E2E71: writeDelta (generic_xlog.c:137)
==32446== by 0x4E341E: GenericXLogFinish (generic_xlog.c:313)
==32446== by 0x14E83324: blbulkdelete (blvacuum.c:149)
==32446== by 0x4BCEE7: index_bulk_delete (indexam.c:627)
==32446== by 0x5DE577: lazy_vacuum_index (vacuumlazy.c:1581)
==32446== by 0x5DFB52: lazy_scan_heap (vacuumlazy.c:1273)
==32446== by 0x5E03AA: lazy_vacuum_rel (vacuumlazy.c:249)
==32446== by 0x5DC7B7: vacuum_rel (vacuum.c:1375)
==32446== by 0x5DD5F7: vacuum (vacuum.c:296)
==32446== by 0x693B71: autovacuum_do_vac_analyze (autovacuum.c:2807)
==32446== by 0x695B2A: do_autovacuum (autovacuum.c:2328)
==32446== by 0x696055: AutoVacWorkerMain (autovacuum.c:1647)
==32446== Uninitialised value was created by a stack allocation
==32446== at 0x14E82CAB: blbulkdelete (blvacuum.c:36)
==32446==
==32446== VALGRINDERROR-END

regards, tom lane