| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*" |
| Date: | 2014-07-20 12:25:02 |
| Message-ID: | 53CBB51E.2030000@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2014-07-20 12:43:27 | Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*" |
| Previous Message | Andres Freund | 2014-07-20 12:06:20 | Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*" |