Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1pUwb9-0000fR-0J
	for pgsql-bugs@arkaria.postgresql.org; Wed, 22 Feb 2023 21:24:23 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1pUwb7-0005qM-O6
	for pgsql-bugs@arkaria.postgresql.org; Wed, 22 Feb 2023 21:24:21 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1pUwb7-0005qD-FP
	for pgsql-bugs@lists.postgresql.org; Wed, 22 Feb 2023 21:24:21 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1pUwb5-0007Yq-D2
	for pgsql-bugs@lists.postgresql.org; Wed, 22 Feb 2023 21:24:21 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 31MLOEmp290813;
	Wed, 22 Feb 2023 16:24:14 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Michael Paquier <michael@paquier.xyz>, exclusion@gmail.com,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17800: ON CONFLICT DO UPDATE fails to detect incompatible
 fields that leads to a server crash
In-reply-to: <20230222192350.wviaslfpo3w2ja3l@awork3.anarazel.de>
References: <Y/P49Yov2m+VzfFf@paquier.xyz>
 <20230221193352.mvzpuvoujfmckvr3@awork3.anarazel.de>
 <3990862.1677010571@sss.pgh.pa.us>
 <20230221204201.idad3kjv3ue7gb6s@awork3.anarazel.de>
 <3995669.1677012915@sss.pgh.pa.us>
 <20230221221602.42n3pheoafjsmouj@awork3.anarazel.de>
 <4060951.1677018870@sss.pgh.pa.us>
 <20230221233349.lj3btvtyqog5jzxd@awork3.anarazel.de>
 <4111538.1677024007@sss.pgh.pa.us>
 <20230222011705.sv75mkhvmxuqv22l@awork3.anarazel.de>
 <20230222192350.wviaslfpo3w2ja3l@awork3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Wed, 22 Feb 2023 11:23:50 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <290811.1677101054.1@sss.pgh.pa.us>
Date: Wed, 22 Feb 2023 16:24:14 -0500
Message-ID: <290812.1677101054@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/290812.1677101054%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> I did come up with a, very hacky at this point, prototype that does seems to
> fix the issue.

Hmm ... this doesn't look very much like what I was imagining.  Let
me draft a prototype and we can compare.

			regards, tom lane