Re: BUG #18142: strange behaviour of "UPDATE" with id_encode() - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18142: strange behaviour of "UPDATE" with id_encode()
Date
Msg-id 2016506.1696255255@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18142: strange behaviour of "UPDATE" with id_encode()  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18143: pg_upgrade fails to use port 50432 even with firewall disabled
Next
From: "David G. Johnston"
Date:
Subject: BUG #18142: strange behaviour of "UPDATE" with id_encode()