From: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Planning counters in pg_stat_statements (using pgss_store) |
Date: | 2019-03-26 23:21:21 |
Message-ID: | DB6PR0301MB2135B8CE071A02D2D663CFA1905F0@DB6PR0301MB2135.eurprd03.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
here is a new version:
- "track_planning" GUC added
to permit to keep previous behavior unchanged
- columns names have been changed / added:
total_plan_time, total_exec_time, total_time
- trailing whitespaces and comments wider than 80 characters
not fixed
- "if (jstate.clocations_count > 0) pgss_store(pstate->p_sourcetext,..."
has been reverted
- expose query text to the planner
won't fix (out of my knowledge)
- "Assert(planning_time > 0 && total_time > 0);"
moved at the beginning of pgss_store
Regards
PAscal
Attachment | Content-Type | Size |
---|---|---|
pgss_add_planning_counters_v3 | application/octet-stream | 26.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2019-03-26 23:22:03 | Re: basebackup checksum verification |
Previous Message | Tom Lane | 2019-03-26 22:31:36 | Re: Fix XML handling with DOCTYPE |