Re: Reducing the log spam

From: Greg Sabino Mullane <htamfids(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-06 15:50:14
Message-ID: CAKAnmmK-vuhfPa-SiO2_yHUwwtft019kOyoJ5OtboL99e9WkZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Tell me about a system that logs different classes of errors to different
log files, and I'm interested again.

Cheers,
Greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Sabino Mullane 2024-03-06 15:59:52 Logging which interface was connected to in log_line_prefix
Previous Message Tomas Vondra 2024-03-06 15:34:41 Re: remaining sql/json patches