| From: | surya poondla <suryapoondla4(at)gmail(dot)com> |
|---|---|
| To: | Euler Taveira <euler(at)eulerto(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: log_min_messages per backend type |
| Date: | 2026-02-06 20:28:25 |
| Message-ID: | CAOVWO5pDcSFiWJqj5cfxzBUUuE6caavOaHQhMoOEuA6niuZBLA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-02-06 20:31:03 | Re: [PING] fallocate() causes btrfs to never compress postgresql files |
| Previous Message | Andrew Dunstan | 2026-02-06 20:16:25 | Re: [PING] fallocate() causes btrfs to never compress postgresql files |