Re: Many "loaded library" logs by preload libraries
| От | Tom Lane |
|---|---|
| Тема | Re: Many "loaded library" logs by preload libraries |
| Дата | |
| Msg-id | 3475.1231124735@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Many "loaded library" logs by preload libraries (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>) |
| Ответы |
Re: Many "loaded library" logs by preload libraries
|
| Список | pgsql-hackers |
ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp> writes:
> If we set shared_preload_libraries or local_preload_libraries to
> load some modules, "loaded library" messages are logged in server
> log every new connections and autovacuum workers.
> LOG: loaded library "pg_stat_statements"
Yeah, I was noticing that myself while testing pg_stat_statements.
I agree that we should fix it to reduce the message level for reloads
occurring in child processes. I'd suggest using DEBUG2 if
(IsUnderPostmaster && process_shared_preload_libraries_in_progress).
I'm not so enthused about eliminating messaging for
local_preload_libraries, though.
regards, tom lane
В списке pgsql-hackers по дате отправления: