aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.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:25:05 -0700
commit52c9cf3239b85f272d928db178d44947c9173d76 (patch)
tree4ae9e9bc4f9f6c25b77942e872502caff19c16ba /src/backend/access/gist/gistproc.c
parentd5de344a50d3fa03fad38fe41cc3443db4143bb5 (diff)
downloadpostgresql-52c9cf3239b85f272d928db178d44947c9173d76.tar.gz
postgresql-52c9cf3239b85f272d928db178d44947c9173d76.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 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions