diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-09-13 12:42:03 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-09-13 12:42:03 -0400 |
| commit | b1de90699e73a081ac450420b7d4f3fd1d49981b (patch) | |
| tree | c9123acdb6674dc75d6b7490048497079494af96 /src/backend/jit/llvm/llvmjit_error.cpp | |
| parent | 99a1c5d068d84f5097ab40842ecd766d69491d6c (diff) | |
| download | postgresql-b1de90699e73a081ac450420b7d4f3fd1d49981b.tar.gz postgresql-b1de90699e73a081ac450420b7d4f3fd1d49981b.zip | |
Fix EXIT out of outermost block in plpgsql.
Ordinarily, using EXIT this way would draw "control reached end of
function without RETURN". However, if the function is one where we
don't require an explicit RETURN (such as a DO block), that should
not happen. It did anyway, because add_dummy_return() neglected to
account for the case.
Per report from Herwig Goemans. Back-patch to all supported branches.
Discussion: https://postgr.es/m/868ae948-e3ca-c7ec-95a6-83cfc08ef750@gmail.com
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_error.cpp')
0 files changed, 0 insertions, 0 deletions