Re: log_min_messages per backend type

Euler Taveira <euler@eulerto.com>

From: "Euler Taveira" <euler@eulerto.com>

To: "Andrew Dunstan" <andrew@dunslane.net>, "Alvaro Herrera" <alvherre@alvh.no-ip.org>

Cc: pgsql-hackers@lists.postgresql.org

Date: 2025-03-06T21:33:06Z

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, Mar 5, 2025, at 1:40 PM, Andrew Dunstan wrote:
> Just bikeshedding a bit ...
> 
> I'm not mad keen on this design. I think the value should be either a single setting like "WARNING" or a set of type:setting pairs. I agree that "all" is a bad name, but I think "default" would make sense.
> 

One of my main concerns was a clear interface. I think "default" is less
confusing than "all". Your suggestion about single or list is aligned with what
Alvaro suggested. IIUC you are suggesting default:loglevel only if it is part
of the list; the single loglevel shouldn't contain the backend type to keep the
backward compatibility. The advantage of your proposal is that it make it clear
what the fallback log level is. However, someone could be confused asking if
the "default" is a valid backend type and if there is a difference between
WARNING and default:WARNING (both is a fallback for non-specified backend type
elements).

--
Euler Taveira
EDB   https://www.enterprisedb.com/