From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Better client reporting for "immediate stop" shutdowns |
Date: | 2020-12-28 18:25:14 |
Message-ID: | 1730644.1609179914@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2020-12-26 13:37:15 -0500, Tom Lane wrote:
>>> I'd like to not log all these repeated messages into the server
>>> log. It's quite annoying to have to digg through thousands of lines of
>>> repeated "terminating connection..."
>> Hm. That's an orthogonal issue, but certainly worth considering.
>> There are a couple of levels we could consider:
>> 1. Just make the logged messages less verbose (they certainly don't
>> need the DETAIL and HINT lines).
>> 2. Suppress the log entries altogether.
> My vote would be #2, with the same reasoning as yours.
The most straightforward way to do that is to introduce a new error
level. Having to renumber existing levels is a bit of a pain, but
I'm not aware of anything that should break in source-code terms.
We make similar ABI breaks in every major release.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
suppress-log-spam-for-SIGQUIT-1.patch | text/x-diff | 4.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2020-12-28 19:14:28 | Re: Better client reporting for "immediate stop" shutdowns |
Previous Message | Tom Lane | 2020-12-28 16:42:22 | Re: pgsql: Fix memory leak in plpgsql's CALL processing. |