On Fri, Oct 10, 2014 at 2:17 PM, Jim Nasby <jim.na...@bluetreble.com> wrote: > That said, since the use case for UPSERT is different than both INSERT and > UPDATE maybe it would be a good idea to have a separate trigger for them > anyway.
-1. I think that having a separate UPSERT trigger is a bad idea. I'll need to change the statement-level behavior to match what Kevin described (fires twice, always, when INSERT ON CONFLICT UPDATE is used). -- 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
