From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*" |
Date: | 2014-04-01 15:25:57 |
Message-ID: | alpine.DEB.2.10.1404011711170.2557@sto |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> I noticed that my pg_stat_statements is cluttered with hundreds of entries
>> like "DEALLOCATE dbdpg_p123456_7", occuring each only once.
>>
>> It seems to me that it would be more helful if these similar entries where
>> aggregated together, that is if the query "normalization" could ignore the
>> name of the descriptor.
>>
>> Any thoughts about this?
>
> You might find this relevant:
> <http://blog.endpoint.com/2014/02/perl-dbdpg-postgresql-prepared-statement.html>
Indeed. Thanks for the pointer. I had guessed who the culprit was, and the
new behavior mentioned in the blog entry may help when the new driver
version hits my debian box.
In the mean time, ISTM that progress can be achieved on pg_stat_statements
normalization as well.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-04-01 15:26:08 | Re: Including replication slot data in base backups |
Previous Message | Tom Lane | 2014-04-01 15:13:30 | Re: BUG #9518: temporary login failure - "missing pg_hba entry" |