| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Michel SALAIS <msalais(at)msym(dot)fr> |
| Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: sql execution time in pg_stat_statements |
| Date: | 2021-09-10 05:18:29 |
| Message-ID: | CAOBaU_Zn5V7vsFaTZKjJgFCb5hQPAQNqV1ro-Kw-VE9n5zBzVQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Sep 10, 2021 at 2:49 AM Michel SALAIS <msalais(at)msym(dot)fr> wrote:
>
> I think that total_time in pg_stat_statements is cpu time + possible waits. So, can I say that:
>
> Total_sql_time = total_time + blk_read_time + blk_write_time
>
> Documentation is not clear at all on that.
In version 12 and below, total_time is the elapsed time between the
execution start and stop, so it includes all underlying events. That
includes any IO activity, wait events or nested statements (if
pg_stat_statemetns.track is set to all). This corresponds to the new
total_exec_time field in version 13 and later.
> Just to say that for PostgreSQL 13, total_time is replaced by “total_exec_time + total_plan_time”
Indeed, as this version also tracks planning activity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2021-09-10 10:58:19 | Re: PostgreSql 9.4 Database connection failure |
| Previous Message | Michel SALAIS | 2021-09-09 18:49:32 | RE: sql execution time in pg_stat_statements |