From cc4fed199f180278b7cec91296c18329beb77c21 Mon Sep 17 00:00:00 2001 From: Michael Coburn Date: Wed, 14 Aug 2024 13:40:30 -0600 Subject: [PATCH] Update slow-extended.md fix formatting of bullets --- docs/slow-extended.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/slow-extended.md b/docs/slow-extended.md index 10b2bc76436..8527b860623 100644 --- a/docs/slow-extended.md +++ b/docs/slow-extended.md @@ -68,10 +68,9 @@ Specifies that only a fraction of `session/query` should be logged. Logging is e Logging all queries might consume I/O bandwidth and cause the log file to grow large. - * When log_slow_rate_type is `session`, this option lets you log full sessions, so you have complete records of sessions for later analysis; but you can rate-limit the number of sessions that are logged. Note that this feature will not work well if your application uses any type of connection pooling or persistent connections. Note that you change log_slow_rate_limit in `session` mode, you should reconnect for get effect. + * When log_slow_rate_type is `session`, this option lets you log full sessions, so you have complete records of sessions for later analysis; but you can rate-limit the number of sessions that are logged. Note that this feature will not work well if your application uses any type of connection pooling or persistent connections. Note that you change log_slow_rate_limit in `session` mode, you should reconnect for get effect. - - * When log_slow_rate_type is `query`, this option lets you log just some queries for later analysis. For example, if you set the value to 100, then one percent of queries will be logged. + * When log_slow_rate_type is `query`, this option lets you log just some queries for later analysis. For example, if you set the value to 100, then one percent of queries will be logged. Note that every query has global unique `query_id` and every connection can has it own (session) log_slow_rate_limit. Decision “log or no” calculated in following manner: