From: Tom Lane <tgl@sss.pgh.pa.us>
To: Udo Polder <udo.polder@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: Problem with "on conflict"
In-reply-to: <939e57d2-9294-4557-b436-eb5e9b268f6f@gmail.com>
References: <939e57d2-9294-4557-b436-eb5e9b268f6f@gmail.com>
Comments: In-reply-to Udo Polder <udo.polder@gmail.com>
	message dated "Wed, 26 Mar 2025 17:15:47 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1627986.1743006773.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Wed, 26 Mar 2025 12:32:53 -0400
Message-ID: <1627987.1743006773@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1627987.1743006773%40sss.pgh.pa.us>
Precedence: bulk

Udo Polder <udo.polder@gmail.com> writes:
> I had some error today at a customer and i figured out, the problem is 
> triggered by postgres doing an insert on a table with wrong data (not 
> even provided), when it should insert the data.
> After some playing around with the query, the error just went away, 
> magically ….

Hmmm...

> Postgres is:
> PostgreSQL 14.1 (Debian 14.1-1.pgdg110+1) on x86_64-pc-linux-gnu, 
> compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit

If it's really 14.1, that's quite ancient and full of known bugs.
The first thing you ought to do is update to latest minor release,
14.17.  I did not look at the release notes to see if any fixes
overlap this area, but it'd be silly to spend a lot of time
tracking down a problem only to find it's already fixed.

			regards, tom lane