Re: unreliable behaviour of track_functions

From: pinker <pinker(at)onet(dot)eu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: unreliable behaviour of track_functions
Date: 2018-04-01 00:17:22
Message-ID: 1522541842492-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver-4 wrote
> https://www.postgresql.org/docs/10/static/monitoring-stats.html#PG-STAT-USER-FUNCTIONS-VIEW
>
> "...But if you want to see new results with each query, be sure to do
> the queries outside any transaction block. Alternatively, you can invoke
> pg_stat_clear_snapshot(), which will discard the current transaction's
> statistics snapshot (if any). The next use of statistical information
> will cause a new snapshot to be fetched.
>
> A transaction can also see its own statistics (as yet untransmitted to
> the collector) in the views pg_stat_xact_all_tables,
> pg_stat_xact_sys_tables, pg_stat_xact_user_tables, and
> pg_stat_xact_user_functions. These numbers do not act as stated above;
> instead they update continuously throughout the transaction.
>
> "
> Adrian Klaver

> adrian.klaver@

Thank you for that, but does this strange behaviour should not be better
documented?
If somebody (like me, I have some time ago being unaware of this behaviour)
wants to build a monitoring system that base on the view
pg_stat_user_functions, should not be informed what to expect?

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-04-01 04:08:01 Re: unreliable behaviour of track_functions
Previous Message Adrian Klaver 2018-03-31 23:59:56 Re: unreliable behaviour of track_functions