From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: 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: <3892120.1676954966@sss.pgh.pa.us>
References: <17800-ff90866b3906c964@postgresql.org>
 <Y/P49Yov2m+VzfFf@paquier.xyz> <3892120.1676954966@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Mon, 20 Feb 2023 23:49:26 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3897699.1676957875.1@sss.pgh.pa.us>
Date: Tue, 21 Feb 2023 00:37:55 -0500
Message-ID: <3897700.1676957875@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3897700.1676957875%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> I think there may be two different bugs here.  The coredump in the
> ON CONFLICT case goes back to v11 for me (and v10 doesn't support
> the primary-key-on-partition case at all, so this error may be
> aboriginal to the feature).  But I only see this "wrong type" failure
> in v14 and later.  I didn't try bisecting yet.

Bisecting produced some interesting results: the "wrong type"
failure has existed for a pretty long time on HEAD.  The reason
I don't see it on v13 etc is that commits 3f7323cbb et al fixed
it in those branches.  That's probably accidental, but I'm too
tired to poke at it more tonight.

			regards, tom lane