From 910690415b661186ae44e3b5e538e23eaa48de1b Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Fri, 14 Nov 2025 14:37:10 +0900 Subject: Revert "Drop unnamed portal immediately after execution to completion" This reverts commit 1fd981f05369, based on concerns that the logging improvements do not justify the protocol breakage of dropping an unnamed portal once its execution has completed. It seems unlikely that one would try to send an execute or describe message after the portal has been used, but if they do such post-completion messages would not be able to process as the previous versions. Let's revert this change for now so as we keep compatibility and consider a different solution. The tests added by 76bba033128a track the pre-1fd981f05369 behavior, and are still valid. Discussion: https://postgr.es/m/CA+TgmoYFJyJNQw3RT7veO3M2BWRE9Aw4hprC5rOcawHZti-f8g@mail.gmail.com --- doc/src/sgml/protocol.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index d1b9af11b07..9d755232873 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -1006,8 +1006,8 @@ SELCT 1/0; 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 statement - specifying the unnamed portal as destination is processed to completion. (Note + destroyed at the end of the transaction, or as soon as the next Bind + statement specifying the unnamed portal as destination is issued. (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. -- cgit v1.2.3