Aug 2019

1 commit
Prevent possible double-free when update trigger returns old tuple.
16 Aug 2019Tom Lanemaster13beta1REL_19_STABLE13beta1REL_18_STABLE13beta1REL_17_STABLE13beta1REL_16_STABLE13beta1REL_15_STABLE13beta1REL_14_STABLE13beta1REL_13_STABLE13beta1+6 more
LLM analysis, 100% surelanded as postedfrom patchset #5

The canonical commit's complete diff matches #5 exactly after removing index hashes, changing only src/test/regress/sql/triggers.sql and src/test/regress/expected/triggers.out. The stable-branch backports additionally incorporate Thomas Munro's oldtuple != trigtuple guard from #6; the development branch already avoided the double-free through slotification.

Credits across 1 commit

Author
Tom LaneLLM1
Committer
Tom Lane1

N LLM means N of the credits come from LLM analysis, not from commit trailers.