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 1ce35b4e-8d37-4b2c-91ef-c70de61e63e6@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>)
Responses Re: [BUG] temporary file usage report with extended protocol and unnamed portals
List pgsql-hackers

On 4/21/25 07:46, Frédéric Yhuel wrote:
> On 4/20/25 00:42, Sami Imseih wrote:
>>> (In my testing, the "temporary file:" message comes
>>> out without any attached STATEMENT most of the time already, so this
>>> isn't losing much as far as that's concerned.)
> 
> 
> Indeed, this happens when using autocommit / implicit transactions.

Actually, this also happens with Java-style cursors, i.e. using the 
setFetchSize(<count>) method, which pgJDBC converts to using named 
portals and EXECUTE <name> <count> protocol messages.

The explanation is probably very similar to the one Sami gave for the 
implicit transaction case.

In any case, my v3 patch seems to fix all these cases.

(I'm not saying it's good enough to be committed as is. I think I should 
at least add some comments. Anything else?)




pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: jsonapi: scary new warnings with LTO enabled
Next
From: Tomas Vondra
Date:
Subject: Re: index prefetching