From 321fa6a4a26c9b649a0fbec9fc8b019f19e62289 Mon Sep 17 00:00:00 2001 From: Fujii Masao Date: Mon, 6 Jul 2020 14:27:09 +0900 Subject: [PATCH] doc: Add note about possible performance overhead by enabling track_planning. Enabling pg_stat_statements.track_plaanning may incur a noticeable performance penalty, especially when a fewer kinds of queries are executed on many concurrent connections. This commit documents this note. Back-patch to v13 where pg_stat_statements.track_plaanning was added. Suggested-by: Pavel Stehule Author: Fujii Masao Reviewed-by: Pavel Stehule Discussion: https://postgr.es/m/CAFj8pRC9Jxa8r5i0TNBWLb8mzuaYzEoLq3QOvip0jVpHPOLbVA@mail.gmail.com --- doc/src/sgml/pgstatstatements.sgml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/src/sgml/pgstatstatements.sgml b/doc/src/sgml/pgstatstatements.sgml index 430d8bf07c4..cf2d25b7b22 100644 --- a/doc/src/sgml/pgstatstatements.sgml +++ b/doc/src/sgml/pgstatstatements.sgml @@ -607,6 +607,9 @@ pg_stat_statements.track_planning controls whether planning operations and duration are tracked by the module. + Enabling this parameter may incur a noticeable performance penalty, + especially when a fewer kinds of queries are executed on many + concurrent connections. The default value is off. Only superusers can change this setting.