Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
Peter Geoghegan <pg@heroku.com>
From: Peter Geoghegan <pg@heroku.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Bruce Momjian <bruce@momjian.us>,
Josh Berkus <josh@agliodbs.com>, Kevin Grittner <kgrittn@ymail.com>,
Andres Freund <andres@2ndquadrant.com>,
Heikki Linnakangas <hlinnakangas@vmware.com>,
Pg Hackers <pgsql-hackers@postgresql.org>,
Craig Ringer <craig@2ndquadrant.com>
Date: 2014-10-27T18:43:25Z
Lists: pgsql-hackers
On Mon, Oct 27, 2014 at 11:12 AM, Simon Riggs <simon@2ndquadrant.com> wrote: > 1. Take the specific docs that relate to the patch and put them in one > place, so that everybody can read and understand and agree the > behaviour of the patch. So that someone reading that can see *exactly* > what is being proposed, not read through pages of other unchanged > material hoping to catch the few points that really differ. I'm afraid I don't follow. I have links to the user-visible documentation (v1.3) on the Wiki: https://wiki.postgresql.org/wiki/UPSERT#Documentation The documentation is complete. I link to every interesting page from the documentation directly from the Wiki, too. Of course, I also describe the issues in more detail for those with an interest in the implementation on the Wiki page itself (and list open issues). I have isolation tests that illustrate the new facets of visibility for READ COMMITTED, too. How, specifically, have I failed to do what you ask here? If you want to see exactly what has changed, in a differential fashion, well, that's what a diff is for. I'm not aware of any existing way of rendering to html for readability, while highlighting what is new. -- Peter Geoghegan
Commits
-
Change the way we mark tuples as frozen.
- 37484ad2aace 9.4.0 cited
-
Add documentation for data-modifying statements in WITH clauses.
- 0ef0b3020402 9.1.0 cited