relcache: Avoid memory leak on tables with no CHECK constraints As complained about by Valgrind, in commit a379061a22a8 I failed to realize that I was causing rd_att->constr->check to become allocated when no CHECK constraints exist; previously it'd remain NULL. (This was my bug, not the mentioned commit author's). Fix by making the allocation conditional, and set ->check to NULL if unallocated.
Reported-by: Yasir <yasir.hussain.s...@gmail.com> Reviewed-by: Tom Lane <t...@sss.pgh.pa.us> Discussion: https://postgr.es/m/202505082025.57ijx3qrbx7u@alvherre.pgsql Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/dc9a2d54fd2571c21c074103cc8ddd93e840b985 Modified Files -------------- src/backend/utils/cache/relcache.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
