Describe the problem

According to https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY

If successfully created, a named portal object lasts till the end of the current transaction

In other words, after Sync is issued and there is no explicit transaction, the portal that was bound using Bind is destroyed. However, CRDB doesn't implement this behavior.

Indeed, if you try this test against Postgres, it results in portal "p8" does not exist

To Reproduce

The following pgwire test matches the Postgres behavior

send
Parse {"Name": "s8", "Query": "SELECT oid, relname FROM pg_class WHERE oid = $1::regclass;"}
Bind {"DestinationPortal": "p8", "PreparedStatement": "s8", "ResultFormatCodes": [0], "Parameters": [{"text":"t"}]}
Sync
----

until
ReadyForQuery
----
{"Type":"ParseComplete"}
{"Type":"BindComplete"}
{"Type":"ReadyForQuery","TxStatus":"I"}

send
Execute {"Portal": "p8"}
Sync
----

until
ErrorResponse
ReadyForQuery
----
{"Type":"ErrorResponse","Code":"34000"}
{"Type":"ReadyForQuery","TxStatus":"I"}

Running against CRDB with make test PKG=./pkg/sql/pgwire TESTS='TestPGTest fails

Expected behavior

The above test should pass

Additional context
I wonder if this is related to the OOM we saw in #69317