On Sat, Apr 25, 2015 at 11:50 AM, Peter Geoghegan <p...@heroku.com> wrote: > To be fair, there is one unrelated slight difference with RETURNING > and conventional UPDATEs: You cannot return the EXCLUDED tuple (in the > same way that you can reference the joined-FROM tuple within > conventional UPDATEs). This is because the pertinent information is > likely to be in the target tuple (after all, the DML statement names > the proposed-for-insertion tuples itself, directly), but more > importantly because projecting both would necessitate *always* > qualifying the RETURNING column names to resolve which tuple is > intended (UPDATE FROM will seldom be a self-join, but this will always > be like a self-join).
It also makes sense because this is the RETURNING clause of an INSERT, not an UPDATE. So the general INSERT behavior is what is expected. It ought to be irrelevant if tuples were projected by actually inserting or updating. Otherwise, your UPSERT is probably misconceived. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
