Re: [GENERAL] upsert and update filtering - Mailing list pgsql-general

From armand pirvu
Subject Re: [GENERAL] upsert and update filtering
Date
Msg-id 7D07CFE1-BDE5-437D-B948-392F444EEAB6@gmail.com
Whole thread Raw
In response to Re: [GENERAL] upsert and update filtering  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-general
aaaa
That's because the access on this case is done to the existing row using the table's name / alias , and to the rows
thatwe attempt to insert using the excluded  

Thank you Peter


Armand

> On Jul 31, 2017, at 4:31 PM, Peter Geoghegan <pg@bowt.ie> wrote:
>
> armand pirvu <armand.pirvu@gmail.com> wrote:
>> But what if in the conflict situation I want to performa the update ONLY if the record is different. The update
seemsto happen no matter what 
>> In other words is there anyway I can filter the update to happen (based on the sample date) only for 112 since col2
isdifferent ? 
>
> That's quite possible. An ON CONFLICT's UPDATE accepts a WHERE clause,
> which can reference both existing and excluded tuples. That WHERE clause
> can back out of the UPDATE based on whatever criteria you like.
>
> --
> Peter Geoghegan



pgsql-general by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [GENERAL] upsert and update filtering
Next
From: Scott Marlowe
Date:
Subject: Re: [GENERAL] Manage slot in logical/pglogical replication