Re: [proposal] pg_stat_statements: extension timing instrumentation - Mailing list pgsql-general

From legrand legrand
Subject Re: [proposal] pg_stat_statements: extension timing instrumentation
Date
Msg-id 1540160070161-0.post@n3.nabble.com
Whole thread Raw
In response to [proposal] pg_stat_statements: extension timing instrumentation  (legrand legrand <legrand_legrand@hotmail.com>)
List pgsql-general
An other way is to use "waits" reporting ...
something like :

pgss_store (...)
    pgstat_report_wait_start(PG_WAIT_EXTENSION);
        ...
    pgstat_report_wait_end();

gives waits of type "Extension", name "Extension" when spending time in this
part of pgss.

This can help those working with waits sampling
as found in pg_stat_activity, pg_wait_sampling or pgsentinel.

note: some of the contentions are already reported as  "LWLock" /
"pg_stat_statements"

Regards
PAscal




--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html


pgsql-general by date:

Previous
From: Tim Clarke
Date:
Subject: Re: archive items not in correct section order
Next
From: legrand legrand
Date:
Subject: Re: no queryId in post_parse_analyze hook when row is locked