Horton
Menu

Re: pg_stat_statements: calls under-estimation propagation

Sameer Thakur <samthakur74@gmail.com>

View thread
From: Sameer Thakur <samthakur74@gmail.com>
To: Daniel Farina <daniel@heroku.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Fujii Masao <masao.fujii@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2013-11-05T13:30:08Z
Lists: pgsql-hackers

Attachments

Hello,
Please find attached pg_stat_statements-identification-v9.patch.
I have tried to address the following review comments
1. Use version PGSS_TUP_V1_2
2.Fixed total time being zero
3. Remove 'session_start' from the view and use point release number
to generate queryid
4. Hide only queryid and query text and not all fields from unauthorized user
5. Removed introduced field from view and code as statistics session
concept is not being used
6. Removed struct Instrumentation usage
7. Updated sgml to reflect changes made. Removed all references to
statistics session, and introduced fields.

regards
Sameer

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.