Re: [HACKERS] MERGE SQL Statement for PG11
Tomas Vondra <tomas.vondra@2ndquadrant.com>
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Peter Geoghegan <pg@bowt.ie>, Robert Haas <robertmhaas@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>,
Alvaro Herrera <alvherre@alvh.no-ip.org>,
Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
Pavan Deolasee <pavan.deolasee@2ndquadrant.com>,
Stephen Frost <sfrost@snowman.net>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-03-01T22:22:46Z
Lists: pgsql-hackers
On 02/06/2018 03:40 PM, Tomas Vondra wrote: > > > I plan to go through the patch and this thread over the couple of > days, and summarize what the current status is (or my understanding > of it). That is (a) what are the missing pieces, (b) why are they > missing, (c) how we plan to address them in the future and (d) > opinions on these issues expressed by others on this thread. > So, I've promised a summary of the patch status about three weeks ago. I've been postponing that as Pavan was moving the patch forward pretty quickly, and now there's not much to summarize ... which is a good thing I guess. If my understanding is correct, the MERGE now supports both partitioning and RLS, and subselects should also work on various places (which is somewhat consistent with my impression claims about SQL standard prohibiting them were not entirely accurate). Which leaves us with figuring out the right concurrency behavior, and that discussion seems to be in progress. So at this point I'm not aware of any other missing features in the patch, and a more detailed summary is not really needed. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Add support for MERGE SQL command
- 7103ebb7aae8 15.0 landed
-
Add API of sorts for transition table handling in trigger.c
- 3a46a45f6f00 15.0 landed
-
Revert MERGE patch
- 08ea7a2291db 11.0 cited
-
Fix several bugs related to ON CONFLICT's EXCLUDED pseudo relation.
- ad2278379244 9.6.0 cited