| From: | baron(at)xaprb(dot)com |
|---|---|
| To: | pgsql-docs(at)postgresql(dot)org |
| Subject: | pg_stat_statements max size clarification |
| Date: | 2017-07-16 00:31:47 |
| Message-ID: | [email protected] |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/pgstatstatements.html
Description:
pg_stat_statements.max (integer)
pg_stat_statements.max is the maximum number of statements tracked by the
module (i.e., the maximum number of rows in the pg_stat_statements view). If
more distinct statements than that are observed, information about the
least-executed statements is discarded. The default value is 5000. This
parameter can only be set at server start.
I wonder if "least-executed" is correct. I'm not an expert and haven't
convinced myself of this by examining the code, but I think after N distinct
queryid's have been seen, then any additional ones are ignored. But that may
not be "least-executed" at all. It's "most-recent" instead. I think we need
a new phrase here.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2017-07-16 01:59:01 | Re: pg_stat_statements max size clarification |
| Previous Message | Conor McNally | 2017-07-14 13:29:36 | Re: Canonical url for latest document set? |