On 1 October 2014 13:43, Heikki Linnakangas <hlinnakan...@vmware.com> wrote:
>> That does sound interesting, but I am concerned the semantics may cause >> issues. >> >> If I go to insert a row for 'UK' and find an existing row for >> 'Europe', do we really want to update the population of Europe to be >> the population of the UK, simply because the UK and Europe have an >> exclusion conflict? > > Clearly not, but you might want to insert the tuple to another table > instead, or skip it altogether. Or you might want to UPDATE Europe into > Continental Europe, and then insert the row for UK. Not trying to catch you out, just trying to make sure we don't make technical decisions based upon unachievable ideas. I can't see value in having upsert work against exclusion constraint indexes; thus this only needs to work for btrees, or similar exact indexes. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
