aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2019-04-07 22:42:42 -0700
committerAndres Freund <andres@anarazel.de>2019-04-07 22:42:42 -0700
commit4c9e1bd0a37e7b79dfc797dd91627336e871c1b0 (patch)
treea5a46c0132ac2b17610d0c9560bbe7ce01b85157 /doc/src
parent41f5e04aec6cf63ba8392adf70e9289e9c3706d6 (diff)
downloadpostgresql-4c9e1bd0a37e7b79dfc797dd91627336e871c1b0.tar.gz
postgresql-4c9e1bd0a37e7b79dfc797dd91627336e871c1b0.zip
Reset memory context once per tuple in validateForeignKeyConstraint.
When using tableam ExecFetchSlotHeapTuple() might return a separately allocated tuple. We could use the shouldFree argument to explicitly free it, but it seems more robust to to protect Also add a CHECK_FOR_INTERRUPTS() after each tuple. It's likely that each AM has (heap does) a CFI somewhere in the relevant path, but it seems more robust to have one in validateForeignKeyConstraint() itself. Note that this only affects the cases that couldn't be optimized to be verified with a query. Author: Andres Freund Reviewed-By: Tom Lane (in an earlier version) Discussion: https://postgr.es/m/19030.1554574075@sss.pgh.pa.us https://postgr.es/m/CAKJS1f_SHKcPYMsi39An5aUjhAcEMZb6Cx1Sj1QWEWSiKJkBVQ@mail.gmail.com https://postgr.es/m/20180711185628.mrvl46bjgk2uxoki@alap3.anarazel.de
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions