Re: BUG #18142: strange behaviour of "UPDATE" with id_encode()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: info(at)dataselfservice(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18142: strange behaviour of "UPDATE" with id_encode()
Date: 2023-10-02 14:00:55
Message-ID: 2016506.1696255255@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2023-10-02 15:02:08 BUG #18142: strange behaviour of "UPDATE" with id_encode()
Previous Message PG Bug reporting form 2023-10-02 13:49:39 BUG #18143: pg_upgrade fails to use port 50432 even with firewall disabled