Re: [BUG] temporary file usage report with extended protocol and unnamed portals - Mailing list pgsql-hackers

From Frédéric Yhuel
Subject Re: [BUG] temporary file usage report with extended protocol and unnamed portals
Date
Msg-id a946ce74-820b-45ec-a9b6-611e8adb3a0b@dalibo.com
Whole thread Raw
In response to Re: [BUG] temporary file usage report with extended protocol and unnamed portals  (Frédéric Yhuel <frederic.yhuel@dalibo.com>)
List pgsql-hackers

On 4/23/25 09:41, Frédéric Yhuel wrote:
> 
> 
> On 4/22/25 19:37, Sami Imseih wrote:
>> the patch relies on looking up queryDesc->sourceText inside DropPortal,
>> which Tom raised concerns about earlier in the thread [0]
> 
> Yes, I think I had misunderstood what Tom said. Thank you for pointing 
> that out.
> 
> However, is it really unsafe?
> 
> In exec_bind_message, the portal's query string comes from a duplicate 
> of the original string (see CreateCachedPlan). So we are safe in this case.
> 
> In exec_simple_query, the portal is dropped towards the end of this 
> function, so we are safe here too.
> 
> Am I missing something?

Note: the patch doesn't work well with server-side prepared statements: 
the PREPARE query is blamed instead of the EXECUTE one. But this is 
maybe something that can be fixed easily.



pgsql-hackers by date:

Previous
From: Devrim Gündüz
Date:
Subject: Re: What's our minimum supported Python version?
Next
From: Daniel Gustafsson
Date:
Subject: Re: jsonapi: scary new warnings with LTO enabled