diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2018-02-01 17:07:38 -0500 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2018-02-16 16:21:24 -0500 |
| commit | ad9a274778d2d88c46b90309212b92ee7fdf9afe (patch) | |
| tree | e48bd1ffc725696fde3279ffabd4fb316743ab45 /src/backend/executor/nodeWindowAgg.c | |
| parent | 49bff412edd9eb226e146f6e4db7b5a8e843bd1f (diff) | |
| download | postgresql-ad9a274778d2d88c46b90309212b92ee7fdf9afe.tar.gz postgresql-ad9a274778d2d88c46b90309212b92ee7fdf9afe.zip | |
Fix crash when canceling parallel query
elog(FATAL) would end up calling PortalCleanup(), which would call
executor shutdown code, which could fail and crash, especially under
parallel query. This was introduced by
8561e4840c81f7e345be2df170839846814fa004, which did not want to mark an
active portal as failed by a normal transaction abort anymore. But we
do need to do that for an elog(FATAL) exit. Introduce a variable
shmem_exit_inprogress similar to the existing proc_exit_inprogress, so
we can tell whether we are in the FATAL exit scenario.
Reported-by: Andres Freund <andres@anarazel.de>
Diffstat (limited to 'src/backend/executor/nodeWindowAgg.c')
0 files changed, 0 insertions, 0 deletions