From a3681e559cb69733a3b83dbd473c85439bd0c18d Mon Sep 17 00:00:00 2001 From: Pavel Stehule Date: Sun, 15 Sep 2024 07:33:19 +0200 Subject: [PATCH] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 0ef895b..1e2096c 100644 --- a/README.md +++ b/README.md @@ -553,6 +553,10 @@ but if there is not enough shared memory, then the profiler is limited just to a The profiler can be activated by calling function `plpgsql_check_profiler(true)` and disabled by calling same function with `false` argument (or with literals `on`, `off`). +The plpgsql_check should be initialized before any plpgsql function is executed. Only +early initialization ensures correct work of profiler and tracer. When you doesn't use +`shared_preloaded_libraries`, you can use command `load 'plpgsql_check'` instead. + When plpgsql_check is initialized by `shared_preload_libraries`, another GUC is available to configure the amount of shared memory used by the profiler: `plpgsql_check.profiler_max_shared_chunks`. This defines the maximum number of