Re: [BUGS] ON CONFLICT issie detected - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: [BUGS] ON CONFLICT issie detected
Date
Msg-id CAH2-WzkCxJRJ4BW_fRuhkXxFQHGmv_WZEbs20jaXzFeDDHDFig@mail.gmail.com
Whole thread Raw
In response to [BUGS] ON CONFLICT issie detected  (Irina Mileva <imileva@transfermate.com>)
Responses Re: [BUGS] ON CONFLICT issie detected  (Irina Mileva <imileva@transfermate.com>)
List pgsql-bugs
On Fri, Apr 21, 2017 at 4:40 AM, Irina Mileva <imileva@transfermate.com> wrote:
> “ON CONFLICT (columnName) DO UPDATE” do NOT works with FOREIGN TABLES
>
> Returns:
>
> “ERROR: there is no unique or exclusion constraint matching the ON CONFLICT
> specification”

It's unsupported, because there is no such thing as a foreign unique
constraint. Only ON CONFLICT DO NOTHING will work against a foreign
table, and only when an arbiter constraint is not inferred.

See the docs on INSERT.


--
Peter Geoghegan

VMware vCenter Server
https://www.vmware.com/


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] Incorrect type in pg_cast causes Postmaster to core dump
Next
From: Irina Mileva
Date:
Subject: Re: [BUGS] ON CONFLICT issie detected