RE: Planning counters in pg_stat_statements (using pgss_store)

From: legrand legrand <legrand_legrand(at)hotmail(dot)com>
To: Sergei Kornilov <sk(at)zsrv(dot)org>, "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-22 22:46:36
Message-ID: DB6PR0301MB2135B4B1D256F547966A559B90430@DB6PR0301MB2135.eurprd03.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
Here is a rebased and corrected version .

Columns naming has not been modified, I would propose to change it to:
- plans: ok
- planning_time --> plan_time
- calls: ok
- total_time --> exec_time
- {min,max,mean,stddev}_time: ok
- new total_time (being the sum of plan_time and exec_time)

Regards
PAscal

Attachment Content-Type Size
pgss_add_planning_counters_v1.diff application/octet-stream 19.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hadi Moshayedi 2019-03-22 23:00:42 Fix foreign key constraint check for partitioned tables
Previous Message Alvaro Herrera 2019-03-22 22:15:57 Re: psql display of foreign keys