Re: log_min_messages per backend type

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Euler Taveira <euler(at)eulerto(dot)com>
Cc: japin <japinli(at)hotmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Subject: Re: log_min_messages per backend type
Date: 2025-12-09 16:30:29
Message-ID: 202512090935.k3xrtr44hxkn@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

BTW another thing I realized while looking this over, is that we quite
uselessly transform the integer backend type to a string, pass it as a
string using the --forkchild= argument to the child process, then parse
the string back to an int to use as an array index. It would be much
easier to just use the integer value everywhere, as the attached shows.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"I love the Postgres community. It's all about doing things _properly_. :-)"
(David Garamond)

Attachment Content-Type Size
0001-Use-integers-not-strings-to-identify-backend-type.patch.nocfbot text/plain 4.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Srirama Kucherlapati 2025-12-09 16:50:40 RE: AIX support
Previous Message Adam Brusselback 2025-12-09 16:27:58 Re: [Patch] Add WHERE clause support to REFRESH MATERIALIZED VIEW