aboutsummaryrefslogtreecommitdiff
path: root/contrib/intarray/_intbig_gist.c
diff options
context:
space:
mode:
authorNathan Bossart <nathan@postgresql.org>2023-05-03 11:32:43 -0700
committerNathan Bossart <nathan@postgresql.org>2023-05-04 16:26:00 -0700
commit800531846ef7da5f4a234fbb6fd65a91c7ecb33f (patch)
tree64b30be3a68308313ba15b1362722046ef0c9dea /contrib/intarray/_intbig_gist.c
parent9a72f499a4b61c34e3ae7759c209e92e0cfef6e1 (diff)
downloadpostgresql-800531846ef7da5f4a234fbb6fd65a91c7ecb33f.tar.gz
postgresql-800531846ef7da5f4a234fbb6fd65a91c7ecb33f.zip
Move return statements out of PG_TRY blocks.
If we exit a PG_TRY block early via "continue", "break", "goto", or "return", we'll skip unwinding its exception stack. This change moves a couple of such "return" statements in PL/Python out of PG_TRY blocks. This was introduced in d0aa965c0a and affects all supported versions. We might also be able to add compile-time checks to prevent recurrence, but that is left as a future exercise. Reported-by: Mikhail Gribkov, Xing Guo Author: Xing Guo Reviewed-by: Michael Paquier, Andres Freund, Tom Lane Discussion: https://postgr.es/m/CAMEv5_v5Y%2B-D%3DCO1%2Bqoe16sAmgC4sbbQjz%2BUtcHmB6zcgS%2B5Ew%40mail.gmail.com Discussion: https://postgr.es/m/CACpMh%2BCMsGMRKFzFMm3bYTzQmMU5nfEEoEDU2apJcc4hid36AQ%40mail.gmail.com Backpatch-through: 11 (all supported versions)
Diffstat (limited to 'contrib/intarray/_intbig_gist.c')
0 files changed, 0 insertions, 0 deletions