Re: log_min_messages per backend type - Mailing list pgsql-hackers

From surya poondla
Subject Re: log_min_messages per backend type
Date
Msg-id CAOVWO5pDcSFiWJqj5cfxzBUUuE6caavOaHQhMoOEuA6niuZBLA@mail.gmail.com
Whole thread
In response to Re: log_min_messages per backend type  (surya poondla <suryapoondla4@gmail.com>)
Responses Re: log_min_messages per backend type
List pgsql-hackers
Hi Euler,

I am still reviewing the latest patch (v11).

Quick clarification on how this feature interacts with existing per-session and per-role/database GUC settings:
If I set log_min_messages = 'warning, backend:error' at the cluster level:
  1. Can an individual session still override this with SET log_min_messages = DEBUG1?
  2. Do role/database-level settings (e.g., ALTER ROLE alice SET log_min_messages = DEBUG1) still work as expected?

I assume both would override the cluster-level backend:error setting following standard GUC precedence rules, but wanted to confirm.

Regards,
Surya Poondla

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [PING] fallocate() causes btrfs to never compress postgresql files
Next
From: Tom Lane
Date:
Subject: Re: [PING] fallocate() causes btrfs to never compress postgresql files