On 2025/03/05 9:33, Euler Taveira wrote:
>> > + Valid <literal>BACKENDTYPE</literal> values are <literal>ARCHIVER</literal>,
>> > + <literal>AUTOVACUUM</literal>, <literal>BACKEND</literal>,
>> > + <literal>BGWORKER</literal>, <literal>BGWRITER</literal>,
>> > + <literal>CHECKPOINTER</literal>, <literal>LOGGER</literal>,
>> > + <literal>SLOTSYNCWORKER</literal>, <literal>WALRECEIVER</literal>,
>> > + <literal>WALSENDER</literal>, <literal>WALSUMMARIZER</literal>, and
>> > + <literal>WALWRITER</literal>.
What about postmaster?
For parallel workers launched for parallel queries, should they follow
the backend's log level or the background worker's? Since they operate
as part of a parallel query executed by a backend, it seems more logical
for them to follow the backend's setting.
+ [B_CHECKPOINTER] = "checkpointer",
+ [B_STARTUP] = "backend", /* XXX same as backend? */
I like the idea of allowing log levels to be set per process.
There were times I wanted to use debug5 specifically for
the startup process when troubleshooting WAL replay. It would be
helpful to distinguish the startup process from a regular backend,
so we can set its log level independently.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
