summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-11-18 13:28:06 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2014-11-18 13:28:06 -0500
commit8b13e5c6c0e8a6b797370fb91d207031df5e784a (patch)
tree4bd1d68bd6f25a7e2d552107fdf0e420f0d07786 /src/backend/access/gist/gist.c
parent606c0123d627b37d5ac3f7c2c97cd715dde7842f (diff)
downloadpostgresql-8b13e5c6c0e8a6b797370fb91d207031df5e784a.tar.gz
Fix some bogus direct uses of realloc().
pg_dump/parallel.c was using realloc() directly with no error check. While the odds of an actual failure here seem pretty low, Coverity complains about it, so fix by using pg_realloc() instead. While looking for other instances, I noticed a couple of places in psql that hadn't gotten the memo about the availability of pg_realloc. These aren't bugs, since they did have error checks, but verbosely inconsistent code is not a good thing. Back-patch as far as 9.3. 9.2 did not have pg_dump/parallel.c, nor did it have pg_realloc available in all frontend code.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions