Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: 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-04-01 14:57:25
Message-ID: 533AD3D5.5080407@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 04/01/2014 10:45 AM, Fabien COELHO wrote:
>
> Hello pgdevs,
>
> 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>

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-04-01 14:59:26 Re: Including replication slot data in base backups
Previous Message Magnus Hagander 2014-04-01 14:45:46 Re: Including replication slot data in base backups