Re: [HACKERS] MERGE SQL Statement for PG11
Chapman Flack <chap@anastigmatix.net>
From: Chapman Flack <chap@anastigmatix.net>
To: pgsql-hackers@lists.postgresql.org
Date: 2018-01-29T16:23:24Z
Lists: pgsql-hackers
On 01/29/2018 11:13 AM, Simon Riggs wrote: > On 29 January 2018 at 15:44, Bruce Momjian <bruce@momjian.us> wrote: >> Uh, if we know we are going to get question on this, the patch had >> better have an explanation of when to use it. Pushing the problem to >> later doesn't seem helpful. > > What problem are you referring to? > > INSERT ON CONFLICT UPDATE does ... > > MERGE allows you to ... In my reading of Pavel and Bruce, the only 'problem' being suggested is that the patch hasn't added a bit of documentation somewhere that lays out the relationship between these two things, more or less as you just did. -Chap
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