Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1qnJTp-00AZ4j-Ph
	for pgsql-bugs@arkaria.postgresql.org; Mon, 02 Oct 2023 14:01:01 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1qnJTn-00FPfk-As
	for pgsql-bugs@arkaria.postgresql.org; Mon, 02 Oct 2023 14:00:59 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1qnJTn-00FPfD-1d
	for pgsql-bugs@lists.postgresql.org; Mon, 02 Oct 2023 14:00:59 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1qnJTk-007nMd-OP
	for pgsql-bugs@lists.postgresql.org; Mon, 02 Oct 2023 14:00:57 +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 392E0toH2016507;
	Mon, 2 Oct 2023 10:00:55 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: info@dataselfservice.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18142: strange behaviour of "UPDATE" with id_encode()
In-reply-to: <18142-b2cd722a4a74a712@postgresql.org>
References: <18142-b2cd722a4a74a712@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 02 Oct 2023 08:01:30 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2016505.1696255255.1@sss.pgh.pa.us>
Date: Mon, 02 Oct 2023 10:00:55 -0400
Message-ID: <2016506.1696255255@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/2016506.1696255255%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> In short: why is `UPDATE...id_encode()` missbehaving and behaving
> differently in case a single `SET` or multiple `SET` on the same line are
> done?

[ shrug... ]  This is evidently a matter of the behavior of your
id_encode function, which you've not shown us.  (Or if it's not yours,
you need to be complaining to its author.  But there's no such
function in standard Postgres.)

			regards, tom lane