{document.title}
\n {teaser > 0 && document.text.length > 0 &&\n \n }\n {document.tags && document.tags.map(tag => (\n {tag}\n ))}\n {teaser > 0 && missing.length > 0 &&\n\n {translation(\"search.result.term.missing\")}: {...missing}\n
\n }\ndiff --git a/main/404.html b/main/404.html index be073cc..2447558 100644 --- a/main/404.html +++ b/main/404.html @@ -13,7 +13,7 @@ - + @@ -21,7 +21,7 @@ - + @@ -32,8 +32,9 @@ + - + @@ -175,10 +176,10 @@
pg_stat_monitor
enables users to track a que
Histogram (the resp_calls
parameter) provides a visual representation of query performance. With the help of the histogram function, you can view a timing/calling data histogram in response to an SQL query.
Learn more about using histograms from the usage example.
pg_stat_monitor
provides the following views:
pg_stat_monitor
is the view where statistics data is presented.pg_stat_monitor_settings
view shows available configuration options which you can change.pg_stat_monitor
provides the following views:
+* pg_stat_monitor
is the view where statistics data is presented.
+* pg_stat_monitor_settings
view shows available configuration options which you can change.
pg_stat_monitor
view¶The statistics gathered by the module are made available via the view named pg_stat_monitor
. This view contains one row for each distinct combination of metrics and whether it is a top-level statement or not (up to the maximum number of distinct statements that the module can track). For details about available counters, refer to the pg_stat_monitor
view reference.
The following are the primary keys for pg_stat_monitor:
@@ -1298,14 +1311,6 @@ With this information,pg_stat_monitor
enables users to track a que
pg_stat_monitor
enables users to track a que
pg_stat_monitor
enables users to track a que
pg_stat_monitor
enables users to track a que
Values:
-Values: +- Min: 1 +- Max: 1000 +- Default: 100
This parameter defines the limit of shared memory (in MB) for pg_stat_monitor
. This memory is used by buckets in a circular manner. The memory is divided between the buckets equally, at the start of the PostgreSQL. Requires the server restart.
Values:
-Values: +- Min: 1024 +- Max: 2147483647 +- Default: 1024
Sets the maximum size of the query. This parameter can only be set at the start of PostgreSQL. For long queries, the query is truncated to that particular length. This is to avoid unnecessary usage of shared memory. Requires the server restart.
-Type: boolean. Default: 1
-Enables or disables the monitoring. “Disable” (0) means that pg_stat_monitor
will not collect the statistics for the whole cluster.
Type: boolean. Default: 1
This parameter controls whether utility commands are tracked by the module. Utility commands are all those other than SELECT
, INSERT
, UPDATE
, and DELETE
.
pg_stat_monitor
enables users to track a que
Type: boolean. Default: 1
By default, the query shows the actual parameter instead of the placeholder. It is quite useful when users want to use that query and try to run that query to check the abnormalities. But in most cases users like the queries with a placeholder. This parameter is used to toggle between the two said options.
Values:
-Values: +- Min: 1 +- Max: 10 +- Default: 10
pg_stat_monitor
accumulates the information in the form of buckets. All the aggregated information is bucket based. This parameter is used to set the number of buckets the system can have. For example, if this parameter is set to 2, then the system will create two buckets. First, the system will add all the information into the first bucket. After its lifetime (defined in the pg_stat_monitor.pgsm_bucket_time parameter) expires, it will switch to the second bucket, reset all the counters and repeat the process.
Requires the server restart.
Values:
-Values: +- Min: 1 +- Max: 2147483647 +- Default: 60
This parameter is used to set the lifetime of the bucket. System switches between buckets on the basis of pg_stat_monitor.pgsm_bucket_time.
Requires the server restart.
Values:
-Values: +- Min: 0 +- Max: 2147483647 +- Default: 0
pg_stat_monitor
also stores the execution time histogram. This parameter is used to set the lower bound of the histogram (in ms).
Requires the server restart.
Values:
-Values: +- Min: 10 +- Max: 2147483647 +- Default: 100000
This parameter sets the upper bound of the execution time histogram (in ms). Requires the server restart.
Values:
-Values: +- Min: 2 +- Max: 2147483647 +- Default: 10
This parameter sets the maximum number of histogram buckets. Requires the server restart.
Values:
-Values: +- Min: 1 +- Max: 10000 +- Default: 20
This parameter defines the shared memory limit (in MB) allocated for a query tracked by pg_stat_monitor
. Requires the server restart.
Type: boolean. Default: 1
@@ -1486,6 +1480,17 @@ With this information,pg_stat_monitor
enables users to track a que
Type: boolean. Default: 1
Enables or disables query plan monitoring. When the pgsm_enable_query_plan
is disabled (0), the query plan will not be captured by pg_stat_monitor
. Enabling it may adversely affect the database performance. Requires the server restart.
This parameter controls which statements are tracked by pg_stat_monitor
.
Values:
+top
: Default, track only top level queries (those issued directly by clients).all
: Track top along with sub/nested queries. As a result, some SELECT statement may be shown as duplicates. none
: Disable query monitoring.Type: boolean. Default: 0
+This parameter controls whether to enable or disable extracting comments from queries.
Type: boolean. Default: 0
This parameter instructs pg_stat_monitor
to monitor query planning statistics. Requires the server restart.
bucket_start_time
shows the start time of the bucket.
Last update:
- 2022-01-19
+ 2022-03-25
@@ -1884,10 +1889,10 @@ The bucket_start_time
shows the start time of the bucket.
\n {translation(\"search.result.term.missing\")}: {...missing}\n
\n }\n