Re: Fwd: Problem with a "complex" upsert - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: Fwd: Problem with a "complex" upsert
Date
Msg-id CAH2-WzmTn9h8GzbEd4aW8gvs+_gDt_otaFhvud0CTFgpzojpXg@mail.gmail.com
Whole thread Raw
In response to Re: Fwd: Problem with a "complex" upsert  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-bugs
On Fri, Aug 3, 2018 at 2:40 AM, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
> This patch also allows access to view columns that aren't in the
> underlying base relation. The rationale for the result in the new test
> case where it attempts to insert (1,'y') into columns (aa,bb) of the
> view is that the new view row that would have resulted if the insert
> had succeeded is ('y',1,(1,'y')), hence that's what excluded.* should
> be for the view in the "on conflict" action, and there should be no
> problem referring to any part of that excluded view tuple.

I agree with your rationale. And, I don't think that it's just a
theoretical point; it actually really matters to affected users.

-- 
Peter Geoghegan


pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Fwd: Problem with a "complex" upsert
Next
From: Andres Freund
Date:
Subject: Re: Fwd: Problem with a "complex" upsert