Re: Postgres 14 update clause bug

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Jüri Tali <Jyri(dot)Tali(at)agri(dot)ee>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgres 14 update clause bug
Date: 2022-02-10 08:28:27
Message-ID: 20220210082827.dalmm3paxdvpd7xf@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Feb 10, 2022 at 07:29:54AM +0000, Jüri Tali wrote:
>
> Postgres 14 probably have Update clause bug
>
> If I write Update clause little bit wrong:
>
> UPDATE "table name" SET column1=1 and column2=2
> WHERE id=1; there is a syntax error, in set part columns must be delimited with comma
>
> Then postgres 14 do not give a error message and show that Update is successful, but without no updated columns.
> POstgres 12 gives a error.

Can you show the definition of the table on both system? Also did you add some
extension or created some casts? I'm wondering if your problem is that you're
actually executing something like that:

UPDATE table_name SET column1 = (1::bool AND column2 = 2) WHERE id = 1;

due to implicit int - bool cast, which aren't present in you pg12 instance (and
shouldn't be present in vanilla postgres).

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Silaparasetti, Ramesh 2022-02-10 13:13:27 RE: Very URGENT REQUEST - Postgresql error : PANIC: could not locate a valid checkpoint record
Previous Message Jüri Tali 2022-02-10 07:29:54 Postgres 14 update clause bug