]> granicus.if.org Git - postgresql/commit
Remove hash_destroy calls in hash_create's failure paths. As noted by
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 14 Aug 2006 12:39:55 +0000 (12:39 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 14 Aug 2006 12:39:55 +0000 (12:39 +0000)
commitc859294ca2eabf65c680fe311596388b36a5fcb8
treedb3396c3b4d74a2259ab509bdf306a3783dc97f4
parentf058451871879392ed9295daed3f5310e85f3986
Remove hash_destroy calls in hash_create's failure paths.  As noted by
a Coverity warning, these are risky since the hashtable isn't necessarily
fully set up yet.  They're unnecessary anyway: a deletable hashtable
should be in a memory context that will be cleared following elog(ERROR).
Per report from Martijn van Oosterhout.
src/backend/utils/hash/dynahash.c