On Wed, Oct 8, 2014 at 3:47 AM, Peter Geoghegan <p...@heroku.com> wrote: > It seems like what you're talking about here is just changing the > spelling of what I already have.
I think there's a subtle difference in expectations too. The current BEFORE INSERT trigger behavior is somewhat defensible with an INSERT-driven syntax (though I don't like it even now [1]). But the MERGE syntax, to me, strongly implies that insertion doesn't begin before determining whether a conflict exists or not. [1] http://www.postgresql.org/message-id/CABRT9RD6zriK+t6mnqQOqaozZ5z1bUaKh+kNY=o9zqbzfoa...@mail.gmail.com Regards, Marti -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
