diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-05-17 17:01:18 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-05-17 17:01:18 -0400 |
| commit | e13ac5586c49c77f301329b79bd7e8f489d0e66f (patch) | |
| tree | 8bf0f11cba4dac8362a1f63c118d0b975d5dd233 /src | |
| parent | 7c979c95a3700d0bd34c2831f49a9260d505b0f9 (diff) | |
| download | postgresql-e13ac5586c49c77f301329b79bd7e8f489d0e66f.tar.gz postgresql-e13ac5586c49c77f301329b79bd7e8f489d0e66f.zip | |
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.
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions