Re: [proposal] pg_stat_statements: extension timing instrumentation

From: legrand legrand <legrand_legrand(at)hotmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: [proposal] pg_stat_statements: extension timing instrumentation
Date: 2018-10-21 22:14:30
Message-ID: 1540160070161-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message legrand legrand 2018-10-21 22:18:33 Re: no queryId in post_parse_analyze hook when row is locked
Previous Message Tim Clarke 2018-10-21 18:28:52 Re: archive items not in correct section order