diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-01-02 16:24:50 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-01-02 16:24:59 -0500 |
commit | 701303590053e100aa3a4ea87ac498d7fe00243f (patch) | |
tree | 98853889ed566a7aea5bae3796274eb722a96d6c /src/backend/access/gist/gistvacuum.c | |
parent | 9200e5664405600ab0bf588a8ff48621682b9fa2 (diff) | |
download | postgresql-701303590053e100aa3a4ea87ac498d7fe00243f.tar.gz postgresql-701303590053e100aa3a4ea87ac498d7fe00243f.zip |
Fix overly-strict assertions in spgtextproc.c.
spg_text_inner_consistent is capable of reconstructing an empty string
to pass down to the next index level; this happens if we have an empty
string coming in, no prefix, and a dummy node label. (In practice, what
is needed to trigger that is insertion of a whole bunch of empty-string
values.) Then, we will arrive at the next level with in->level == 0
and a non-NULL (but zero length) in->reconstructedValue, which is valid
but the Assert tests weren't expecting it.
Per report from Andreas Seltenreich. This has no impact in non-Assert
builds, so should not be a problem in production, but back-patch to
all affected branches anyway.
In passing, remove a couple of useless variable initializations and
shorten the code by not duplicating DatumGetPointer() calls.
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions