BUG #15479: Documentation claims that client_min_messages is related to logging

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: clemens(at)ladisch(dot)de
Subject: BUG #15479: Documentation claims that client_min_messages is related to logging
Date: 2018-11-01 08:36:29
Message-ID: 15479-ef0f4cc2fd995ca2@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 15479
Logged by: Clemens Ladisch
Email address: clemens(at)ladisch(dot)de
PostgreSQL version: 11.0
Operating system: any

Step 1: User wants to reduce the amount of logging, looks into section
19.8.2 "When To Log".
Step 2: Sets "client_min_messages = fatal".
Step 3: The server sends no ErrorResponse, so erroneous SQL statements
appear to succeed.


The problem is that client_min_messages has *no relation whatsoever* with
the server's logging.
This variable affects the client connection, so its documentation should be
moved into section 19.11 "Client Connection Behaviour".
(And the word "messages" might still be misleading; maybe use "network
protocol messages".)


Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-11-01 09:15:33 BUG #15480: psql 11 array concatenation in CASE takes on values from the CASE expression when using enum_range
Previous Message Pavel Stehule 2018-11-01 08:04:23 Re: BUG #15477: Procedure call with named inout refcursor parameter - "invalid input syntax for type boolean" error