On 2013-10-15 11:11:24 -0400, Robert Haas wrote: > I'm not saying "go implement MERGE". I'm saying, make the > insert-or-update operation a single statement, using some syntax TBD, > instead of requiring the use of a new insert statement that makes > invisible rows visible as a side effect, so that you can wrap that in > a CTE and feed it to an update statement. That's complex and, AFAICS, > unlike how any other database product handles this.
I think we most definitely should provide a single statement variant. That's the one users yearn for. I also would like a variant where I can lock a row on conflict, for multimaster scenarios, but that doesn't necessarily have to be exposed to SQL. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
