Re: pgsql: Drop unnamed portal immediately after execution to completion - Mailing list pgsql-hackers

From Mircea Cadariu
Subject Re: pgsql: Drop unnamed portal immediately after execution to completion
Date
Msg-id e0ab1ea2-7084-44c5-b6aa-f01db7be7792@gmail.com
Whole thread Raw
In response to Re: pgsql: Drop unnamed portal immediately after execution to completion  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pgsql: Drop unnamed portal immediately after execution to completion
List pgsql-hackers
On 13/11/2025 06:27, Michael Paquier wrote:

> This is new, attaching the information to a Vfd in fd.c.  Not sure
> that adding this information to this structure is a good concept.
> This layer of the code has no idea of query strings currently, so that
> feels a bit like a layer violation.

Thanks for having a look! FWIW I found a way for Plan C to work without 
including tcoprot into fd, see attached.

There's a new field in that structure indeed, but maybe not that far 
fetched, it's the query that triggered the creation of the file.

Kind regards,

Mircea Cadariu

Attachment

pgsql-hackers by date:

Previous
From: Mihail Nikalayeu
Date:
Subject: Re: [BUG?] check_exclusion_or_unique_constraint false negative
Next
From: Álvaro Herrera
Date:
Subject: Re: Few untranslated error messages in OAuth