| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Claudio Nasuti <caesarfive(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: server log error on conflict do nothing |
| Date: | 2024-04-05 12:05:29 |
| Message-ID: | 693e8a79b7570463b7e4914a2e31cd844bd6914c.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jaya kumar | 2024-04-05 16:29:16 | Re: Table DML status check per day |
| Previous Message | Claudio Nasuti | 2024-04-05 11:10:27 | server log error on conflict do nothing |