From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Claudio Nasuti <caesarfive@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: server log error on conflict do nothing
Date: Fri, 05 Apr 2024 14:05:29 +0200
Message-ID: <693e8a79b7570463b7e4914a2e31cd844bd6914c.camel@cybertec.at> (raw)
In-Reply-To: <CAOnYL8Ak4Z7n4mCWFjosJCun8yULmXms4US=-ok+2skcJUeszQ@mail.gmail.com>
References: <CAOnYL8Ak4Z7n4mCWFjosJCun8yULmXms4US=-ok+2skcJUeszQ@mail.gmail.com>
On Fri, 2024-04-05 at 13:10 +0200, Claudio Nasuti wrote:
> we have a couple of concurrent application that sometimes goes in conflict performing an insert
> in a table.
> At client side they are managed with clause "on conflict do nothing" and work perfeclty.
> That said when the conflict happens it is reported in the postgresql server log.
> I would like to know (I was unable to find the info in the documentation nor in the maillist archive)
> if it is possible to configure the server to avoid that these "managed" conflict are reported as error in the server log.
That cannot be.
It must be some other constraint violations you see in the log.
Normally all errors will reach the client, unless you catch them
with an exception handler in PL/pgSQL code.
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, caesarfive@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: server log error on conflict do nothing
In-Reply-To: <693e8a79b7570463b7e4914a2e31cd844bd6914c.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox