Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"

Поиск
Список
Период
Сортировка
От Marko Tiikkaja
Тема Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"
Дата
Msg-id 53CBB51E.2030000@joh.to
обсуждение исходный текст
Ответ на Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"  (Andres Freund <andres@2ndquadrant.com>)
Список 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 по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"
Следующее
От: Fabien COELHO
Дата:
Сообщение: Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"