| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Reducing the log spam |
| Date: | 2024-03-06 20:31:17 |
| Message-ID: | f88513d4906001a599da3b5dfddee32e011fe5c8.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2024-03-06 at 10:50 -0500, Greg Sabino Mullane wrote:
> On Tue, Mar 5, 2024 at 7:55 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> > 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"
>
> Forcibly hiding those at the Postgres level seems a heavy hammer for what is ultimately an application problem.
Yes... or no. Lots of applications violate constraints routinely.
As long as the error is caught and handled, that's not a problem.
Whoever cares about the log messages can enable them. My impression
is that most people don't care about them.
But thanks for your opinion.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2024-03-06 20:34:37 | Re: [PATCH] Exponential backoff for auth_delay |
| Previous Message | Merlin Moncure | 2024-03-06 20:03:37 | Re: MERGE ... RETURNING |