Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Date
Msg-id CAM3SWZTjpDN5C9okmGs2vhK1WcT06Pu0ePmqsYfaZDZgkBtkkQ@mail.gmail.com
Whole thread Raw
In response to Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Wed, Nov 19, 2014 at 6:04 PM, Peter Geoghegan <pg@heroku.com> wrote:
> I think that 3 is out. It seems hard to justify not RETURNING anything
> in respect of a slot when there is a before row insert trigger that
> returns NULL on the one hand, but RETURNING something despite not
> inserting for ON CONFLICT UPDATE on the other.

I mean: despite not inserting *or updating*.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Next
From: Alvaro Herrera
Date:
Subject: Re: New Event Trigger: table_rewrite