On Thu, May 9, 2019 at 07:19:59PM -0500, Justin Pryzby wrote:
> > +Author: Thomas Munro <tmu...@postgresql.org>
> > +2018-07-13 [387a5cfb9] Add pg_dump - -on-conflict-do-nothing option.
> > +-->
> > +
> > +<para>
> > +Allow restore of INSERT statements to skip rows which would cause
> > conflicts (Surafel Temesgen)
> > +</para>
>
> restore *using* INSERT statements ?
> cause "unique index" conflicts ?
I am not sure "unique index" helps since most people think of ON
CONFLICT and not its implementation.
Applied patch attached, URL updated:
http://momjian.us/pgsql_docs/build.html
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
diff --git a/doc/src/sgml/release-12.sgml b/doc/src/sgml/release-12.sgml
index 977dc53f3e..54f66e13dc 100644
--- a/doc/src/sgml/release-12.sgml
+++ b/doc/src/sgml/release-12.sgml
@@ -722,11 +722,11 @@ Author: Peter Eisentraut <pete...@gmx.net>
-->
<para>
-Allow contol over when generic plans are used for prepared statements (Pavel
Stehule)
+Allow control over when generic plans are used for prepared statements (Pavel
Stehule)
</para>
<para>
-The server variable plan_cache_mode enables this control.
+This is controlled by the plan_cache_mode server variable.
</para>
</listitem>
@@ -2476,7 +2476,7 @@ Author: Thomas Munro <tmu...@postgresql.org>
-->
<para>
-Allow restore of INSERT statements to skip rows which would cause conflicts
(Surafel Temesgen)
+Allow restoration of an INSERT-statement dump to skip rows which would cause
conflicts (Surafel Temesgen)
</para>
<para>
