diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-02-18 03:06:46 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-02-18 03:06:46 +0000 |
| commit | 7981c34279fbddc254cfccb9a2eec4b35e692a12 (patch) | |
| tree | 454e03c935aae1e552853c1a2e377287484ff2fe /src/backend/executor/nodeModifyTable.c | |
| parent | c0d5be5d6a736d2ee8141e920bc3de8e001bf6d9 (diff) | |
| download | postgresql-7981c34279fbddc254cfccb9a2eec4b35e692a12.tar.gz postgresql-7981c34279fbddc254cfccb9a2eec4b35e692a12.zip | |
Force READY portals into FAILED state when a transaction or subtransaction
is aborted, if they were created within the failed xact. This prevents
ExecutorEnd from being run on them, which is a good idea because they may
contain references to tables or other objects that no longer exist.
In particular this is hazardous when auto_explain is active, but it's
really rather surprising that nobody has seen an issue with this before.
I'm back-patching this to 8.4, since that's the first version that contains
auto_explain or an ExecutorEnd hook, but I wonder whether we shouldn't
back-patch further.
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions