Re: pg_stat_statements: calls under-estimation propagation

Fujii Masao <masao.fujii@gmail.com>

From: Fujii Masao <masao.fujii@gmail.com>
To: Sameer Thakur <samthakur74@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2013-09-18T17:49:56Z
Lists: pgsql-hackers
On Thu, Sep 19, 2013 at 2:41 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Wed, Sep 18, 2013 at 2:41 PM, Sameer Thakur <samthakur74@gmail.com> wrote:
>>>> >You seem to have forgotten to include the pg_stat_statements--1.2.sql
>>>> >and pg_stat_statements--1.1--1.2.sql in the patch.
>>>> Sorry again. Please find updated patch attached.
>>
>> I did not add pg_stat_statements--1.2.sql. I have added that now and updated
>> the patch again.

pg_stat_statements--1.1.sql should be removed.

+      <entry><structfield>queryid</structfield></entry>
+      <entry><type>bigint</type></entry>
+      <entry></entry>
+      <entry>Unique value of each representative statement for the
current statistics session.
+       This value will change for each new statistics session.</entry>

What does "statistics session" mean?

Regards,

-- 
Fujii Masao


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Improve management of "sticky" entries in contrib/pg_stat_statements.