| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Missing INFO on client_min_messages |
| Date: | 2024-11-24 16:57:01 |
| Message-ID: | 1046003.1732467421@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Sunday, November 24, 2024, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:
>> If I try to set client_min_messages with a wrong value it raises an error
>> and its hint is
>> "Available values: debug5, debug4, debug3, debug2, debug1, log, notice,
>> warning, error."
>> Why is not INFO option on this hint ?
> The definition of info is:
> Provides information implicitly requested by the user
> Requested information by the client should not be allowed to be suppressed
> by the client.
Yeah. You can set it to INFO if you like, but the behavior is not
different from setting it to NOTICE. So apparently we decided long
ago that showing INFO as a possible option was more confusing than
not showing it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2024-11-24 18:04:38 | Re: Parallel CREATE INDEX for GIN indexes |
| Previous Message | David G. Johnston | 2024-11-24 14:56:54 | Re: Missing INFO on client_min_messages |