Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"
Date: 2014-07-20 15:17:39
Message-ID: alpine.DEB.2.10.1407201710580.16752@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> That's because PREPARE isn't executed as it's own statement, but done on
>> the protocol level (which will need noticeably fewer messages). There's
>> no builtin logic to ignore actual PREPARE statements.
>
> ISTM that there is indeed a special handling in function
> pgss_ProcessUtility for PREPARE and EXECUTE:
>
> [...]

For completeness purpose, here is the one-liner patch to handle DEALLOCATE
as PREPARE & EXECUTE are handled. It is cleaner than the other one, but
then DEALLOCATE disappear from the table, as PREPARE and EXECUTE do.

--
Fabien.

Attachment Content-Type Size
pgss-norm-deallocate-simple.patch text/x-diff 956 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-07-20 15:28:04 Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"
Previous Message Fabien COELHO 2014-07-20 15:01:50 Re: pg_stat_statements cluttered with "DEALLOCATE dbdpg_p*"