From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Reducing the log spam |
Date: | 2024-03-05 13:08:25 |
Message-ID: | CAFj8pRB40fwicFAv6S8_6b6U+XmsVp+mbd==cN14G_j1YrkdrQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
út 5. 3. 2024 v 13:55 odesílatel Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
napsal:
> Inspired by feedback to [1], I thought about how to reduce log spam.
>
> My experience from the field is that a lot of log spam looks like
>
> database/table/... "xy" does not exist
> duplicate key value violates unique constraint "xy"
>
> So what about a parameter "log_suppress_sqlstates" that suppresses
> logging ERROR and FATAL messages with the enumerated SQL states?
>
> My idea for a default setting would be something like
>
> log_suppress_sqlstates = '23505,3D000,3F000,42601,42704,42883,42P01'
>
+1 in this form
the overhead of this implementation should be small
Regards
Pavel
> but that's of course bikeshedding territory.
>
> Yours,
> Laurenz Albe
>
>
>
> [1]:
> https://postgr.es/m/b8b8502915e50f44deb111bc0b43a99e2733e117.camel%40cybertec.at
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2024-03-05 13:14:20 | Re: [PATCH] Exponential backoff for auth_delay |
Previous Message | Yugo NAGATA | 2024-03-05 13:05:52 | Remove unnecessary code from psql's watch command |