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()
Date: Mon, 02 Oct 2023 10:00:55 -0400
Message-ID: <2016506.1696255255@sss.pgh.pa.us> (raw)
In-Reply-To: <18142-b2cd722a4a74a712@postgresql.org>
References: <18142-b2cd722a4a74a712@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, info@dataselfservice.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18142: strange behaviour of "UPDATE" with id_encode()
In-Reply-To: <2016506.1696255255@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox