From: | QA Collective <theqacollective(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #16768: PostgreSQL 12.5 - INSERT ON CONFLICT succeeds on data INSERT but does nothing on UPDATE |
Date: | 2020-12-09 02:25:45 |
Message-ID: | CADF5g4csd1_0TzxWzJBSqozjnqrx1cx8Vpm1Z1e61u6HD17bKg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thanks for your reply Peter. If this is the case, what would be the reason
for this functionality having 'changed' over the past week or so? Code
running like this over many months has worked as expected.
On Wed, Dec 9, 2020 at 12:14 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Tue, Dec 8, 2020 at 5:02 PM PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
> > The SQL below recreates my issue. That is, the LAST insert statement
> DOES
> > NOT update the accountinfo_test table value for 'balance' to 200.0 ... it
> > remains at the previous value of 100.0.
>
> I think that you need to UPDATE using the excluded.* pseudo table. For
> example, "SET my_col = excluded.my_col". As things stand you're using
> the target table itself. Technically the row is being updated, but
> with the wrong values (the existing values rather than your intended
> new successor values).
>
> --
> Peter Geoghegan
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2020-12-09 02:34:32 | Re: BUG #16768: PostgreSQL 12.5 - INSERT ON CONFLICT succeeds on data INSERT but does nothing on UPDATE |
Previous Message | Peter Geoghegan | 2020-12-09 01:14:27 | Re: BUG #16768: PostgreSQL 12.5 - INSERT ON CONFLICT succeeds on data INSERT but does nothing on UPDATE |