Re: Reducing the log spam

Laurenz Albe <laurenz.albe@cybertec.at>

From: Laurenz Albe <laurenz.albe@cybertec.at>

To: Greg Sabino Mullane <htamfids@gmail.com>

Cc: pgsql-hackers@lists.postgresql.org

Date: 2024-03-06T20:31:17Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

plpgsql: make WHEN OTHERS distinct from WHEN SQLSTATE '00000'.
- 58fdca2204de 18.0 cited

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.albe@cybertec.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