pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
BUG #15479: Documentation claims that client_min_messages is related to logging 2+ messages / 2 participants [nested] [flat]
Commits from this thread: 2018-11-08 041ad9a66d 88275ac199 2407d4807f 3d360e20c9 7b08b4a8ad c09daa9104 Disallow setting client_min_messages higher than ERROR.
* BUG #15479: Documentation claims that client_min_messages is related to logging @ 2018-11-01 08:36 PG Bug reporting form <noreply@postgresql.org> 2018-11-08 17:24 ` Re: BUG #15479: Documentation claims that client_min_messages is related to logging Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 2+ messages in thread From: PG Bug reporting form @ 2018-11-01 08:36 UTC (permalink / raw) To: pgsql-bugs@lists.postgresql.org; +Cc: clemens@ladisch.de The following bug has been logged on the website: Bug reference: 15479 Logged by: Clemens Ladisch Email address: clemens@ladisch.de PostgreSQL version: 11.0 Operating system: any Description: 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. Example: <https://www.postgresql.org/message-id/flat/EE586BE92A4AFB45B03310C2A0C0565D6D0EFC17%40G01JPEXMBKW03; 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".) ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #15479: Documentation claims that client_min_messages is related to logging 2018-11-01 08:36 BUG #15479: Documentation claims that client_min_messages is related to logging PG Bug reporting form <noreply@postgresql.org> @ 2018-11-08 17:24 ` Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2018-11-08 17:24 UTC (permalink / raw) To: clemens@ladisch.de; +Cc: pgsql-bugs@lists.postgresql.org =?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes: > 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". Yeah, I agree. Will do. > (And the word "messages" might still be misleading; maybe use "network > protocol messages".) I don't think that adds anything. regards, tom lane ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2018-11-08 17:24 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2018-11-01 08:36 BUG #15479: Documentation claims that client_min_messages is related to logging PG Bug reporting form <noreply@postgresql.org> 2018-11-08 17:24 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox