postgresql/contrib/bloom
Tom Lane e13ac5586c Avoid possible crash in contrib/bloom's blendscan().
It's possible to begin and end an indexscan without ever calling
amrescan.  contrib/bloom, unlike every other index AM, allocated
its "scan->opaque" storage at amrescan time, and thus would crash
in amendscan if amrescan hadn't been called.  We could fix this
by putting in a null-pointer check in blendscan, but I see no very
good reason why contrib/bloom should march to its own drummer in
this respect.  Let's move that initialization to blbeginscan
instead.  Per report from Jeff Janes.
2016-05-17 17:01:18 -04:00
..
expected Improve contrib/bloom regression test using code coverage info. 2016-04-10 13:12:24 -04:00
sql Improve contrib/bloom regression test using code coverage info. 2016-04-10 13:12:24 -04:00
t Bloom index contrib module 2016-04-01 16:42:24 +03:00
.gitignore Bloom index contrib module 2016-04-01 16:42:24 +03:00
blcost.c Bloom index contrib module 2016-04-01 16:42:24 +03:00
blinsert.c Revert no-op changes to BufferGetPage() 2016-04-20 08:31:19 -05:00
bloom--1.0.sql Bloom index contrib module 2016-04-01 16:42:24 +03:00
bloom.control Bloom index contrib module 2016-04-01 16:42:24 +03:00
bloom.h Add page id to bloom index 2016-04-12 18:03:01 +03:00
blscan.c Avoid possible crash in contrib/bloom's blendscan(). 2016-05-17 17:01:18 -04:00
blutils.c Prevent to use magic constants 2016-04-28 16:39:25 +03:00
blvacuum.c Revert no-op changes to BufferGetPage() 2016-04-20 08:31:19 -05:00
blvalidate.c Bloom index contrib module 2016-04-01 16:42:24 +03:00
Makefile Bloom index contrib module 2016-04-01 16:42:24 +03:00