diff options
| author | Nathan Bossart <nathan@postgresql.org> | 2023-05-03 11:32:43 -0700 |
|---|---|---|
| committer | Nathan Bossart <nathan@postgresql.org> | 2023-05-04 16:26:05 -0700 |
| commit | 24964394a972d0e7b030bf02a600bceea0be72d3 (patch) | |
| tree | 3e8edafa3a21672e8eae09143f6577c1c9a458df /src/backend/executor/nodeAgg.c | |
| parent | 580df507896351a0ebb5a09c2c84c0eac7b6740f (diff) | |
| download | postgresql-24964394a972d0e7b030bf02a600bceea0be72d3.tar.gz postgresql-24964394a972d0e7b030bf02a600bceea0be72d3.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/executor/nodeAgg.c')
0 files changed, 0 insertions, 0 deletions