Re: log_min_messages per backend type

Kirill Reshke <reshkekirill@gmail.com>

From: Kirill Reshke <reshkekirill@gmail.com>

To: Euler Taveira <euler@eulerto.com>

Cc: pgsql-hackers@lists.postgresql.org

Date: 2024-12-19T04:13:25Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Allow log_min_messages to be set per process type
- 38e0190ced71 19 (unreleased) landed
Assign "backend" type earlier during process start-up
- 0c8e082fba8d 19 (unreleased) landed
Use integer backend type when exec'ing a postmaster child
- f1cd34f95272 19 (unreleased) landed
Sort guc_parameters.dat alphabetically by name
- fce7c73fba4e 19 (unreleased) cited
Create a separate file listing backend types
- dbf8cfb4f02e 19 (unreleased) cited

On Wed, 18 Dec 2024 at 00:15, Euler Taveira <euler@eulerto.com> wrote:
>
> Hi,
>
> Sometimes you need to inspect some debug messages from autovacuum worker but
> you cannot apply the same setting for backends (that could rapidly fill the log
> file). This proposal aims to change log_min_messages to have different log
> levels depending on which backend type the message comes from.

Hi! Looks like a sane proposal. Correct me if I'm wrong, but with your
patch it is not possible to configure something like "everybody ERROR,
but autovac DEBUG5"? I mean,
set log_min_messages to 'ERROR:default, DEBUG5:autovacuum' (not
specifying all possible cases?)