diff options
| author | Michael Paquier <michael@paquier.xyz> | 2025-11-05 14:35:16 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2025-11-05 14:35:16 +0900 |
| commit | 1fd981f05369340a8afa4d013a350b0b2ac6e33e (patch) | |
| tree | 762d242a953595194d39ab31d1987cbb00cf3bf6 /doc | |
| parent | 59dec6c0b09f717e4ce78d54f578d56ef93bcc53 (diff) | |
Drop unnamed portal immediately after execution to completion
Previously, unnamed portals were kept until the next Bind message or the
end of the transaction. This could cause temporary files to persist
longer than expected and make logging not reflect the actual SQL
responsible for the temporary file.
This patch changes exec_execute_message() to drop unnamed portals
immediately after execution to completion at the end of an Execute
message, making their removal more aggressive. This forces temporary
file cleanups to happen at the same time as the completion of the portal
execution, with statement logging correctly reflecting to which
statements these temporary files were attached to (see the diffs in the
TAP test updated by this commit for an idea).
The documentation is updated to describe the lifetime of unnamed
portals, and test cases are updated to verify temporary file removal and
proper statement logging after unnamed portal execution. This changes
how unnamed portals are handled in the protocol, hence no backpatch is
done.
Author: Frédéric Yhuel <frederic.yhuel@dalibo.com>
Co-Authored-by: Sami Imseih <samimseih@gmail.com>
Co-Authored-by: Mircea Cadariu <cadariu.mircea@gmail.com>
Discussion: https://postgr.es/m/CAA5RZ0tTrTUoEr3kDXCuKsvqYGq8OOHiBwoD-dyJocq95uEOTQ%40mail.gmail.com
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/src/sgml/protocol.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index 9d755232873..d1b9af11b07 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -1006,8 +1006,8 @@ SELCT 1/0;<!-- this typo is intentional --> <para> If successfully created, a named portal object lasts till the end of the current transaction, unless explicitly destroyed. An unnamed portal is - destroyed at the end of the transaction, or as soon as the next Bind - statement specifying the unnamed portal as destination is issued. (Note + destroyed at the end of the transaction, or as soon as the statement + specifying the unnamed portal as destination is processed to completion. (Note that a simple Query message also destroys the unnamed portal.) Named portals must be explicitly closed before they can be redefined by another Bind message, but this is not required for the unnamed portal. |