Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*" - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"
Date
Msg-id 53CBB51E.2030000@joh.to
Whole thread Raw
In response to Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 2014-07-20 14:06, Andres Freund wrote:
> On 2014-07-20 13:54:01 +0200, Andres Freund wrote:
>> On 2014-04-01 16:45:29 +0200, Fabien COELHO wrote:
>>> I noticed that my pg_stat_statements is cluttered with hundreds of entries
>>> like "DEALLOCATE dbdpg_p123456_7", occuring each only once.
>>
>> Why isn't the driver using the extended query protocol? Sending
>> PREPARE/EXECUTE/DEALLOCATE wastes roundtrips...
>
> Hm. It's probably because libqp doesn't expose sending Close message for
> prepared statements :(. No idea why.

Yeah, I always considered that a missing feature, and even wrote a patch 
to add it at some point.  I wonder what happened to it.


.marko



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"
Next
From: Fabien COELHO
Date:
Subject: Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"