From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: INSERT ... ON CONFLICT syntax issues |
Date: | 2015-05-07 09:01:27 |
Message-ID: | CAEzk6ffVmfF8bY=6+LvTwe6i1ZAwVoCManBzHhDGEjsNQ0E5pA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6 May 2015 at 22:30, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> On 05/07/2015 12:01 AM, Andres Freund wrote:
>
>> On 2015-05-06 23:48:18 +0300, Heikki Linnakangas wrote:
>>
>>> I'll see about fixing that. It's not just a matter of creating another
>>> alias
>>> for the same rel, I'm afraid: "foo.t" is supposed to refer to the tuple
>>> that
>>> we attempted to insert, like it does without the ON CONFLICT.
>>>
>>
>> I'm not sure what you mean here?
>>
>
> Sorry, forget about that. I was confused and mixed up EXCLUDED and TARGET.
> Looks like they really aren't very good names :-).
Could
INSERT.column
and
CONFLICT.column work?
So INSERT is the row that you were inserting, and CONFLICT is the row with
which it conflicted?
Geoff
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2015-05-07 09:42:51 | Re: Resource leak in pg_dump.c caused by transforms |
Previous Message | Amit Kapila | 2015-05-07 07:23:12 | Re: Parallel Seq Scan |