Re: BUG #13413: pg_stat_statements don't statistics "DEALLOCATE ALL" statements

From: q <held911(at)163(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13413: pg_stat_statements don't statistics "DEALLOCATE ALL" statements
Date: 2015-06-10 02:38:21
Message-ID: 168d1439.1affc.14ddb552ca6.Coremail.held911@163.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

This is my fault.I read the 9.4 release partly,not all .
I read the document about the pg_stat_stament like follow:

F.29. pg_stat_statements

The pg_stat_statements module provides a means for tracking execution statistics of all SQL statements executed by a server.

So, I misunderstand it.

Thans for your reply.
best regards

At 2015-06-08 23:08:34, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>held911(at)163(dot)com writes:
>> this function is ok in pg 9.3.5. But , it does not work in pg 9.4.1.
>
>This is not a bug, it's an intentional behavioral change. See the 9.4
>release notes:
>
> * Make pg_stat_statements ignore DEALLOCATE commands (Fabien Coelho)
>
> It already ignored PREPARE, as well as planning time in general,
> so this seems more consistent.
>
>
> regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message dineshrapidflow 2015-06-10 10:50:51 BUG #13425: Not able to import osm data into database
Previous Message Tom Lane 2015-06-09 13:50:02 Re: BUG #13420: Array function contains with null