Robert Treat <[EMAIL PROTECTED]> writes: > Perhaps a better option would be to implement Merge per spec, and then > implement a "replace into" command for the oltp scenario. This way you keep > the spec behavior for the spec syntax, and have a clearly non-spec command > for non-spec behavior.
In that case, it's a fair question to ask just who will use the "spec" syntax. As far as I can tell from years of watching the mailing lists, there is plenty of demand for a concurrent-safe insert-or-update behavior, and *exactly zero* demand for the other. I challenge you to find even one request for the "spec" behavior in the mailing list archives. (Simon doesn't count.) I recently came across the expression "YAGNI", and think it's probably pretty relevant to this discussion: http://en.wikipedia.org/wiki/You_Ain't_Gonna_Need_It regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
