From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg12 release notes |
Date: | 2019-05-10 00:38:39 |
Message-ID: | 20190510003839.mkvh4t6nzaau4dqm@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 9, 2019 at 07:19:59PM -0500, Justin Pryzby wrote:
> > +Author: Thomas Munro <tmunro(at)postgresql(dot)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 <bruce(at)momjian(dot)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 +
Attachment | Content-Type | Size |
---|---|---|
diff | text/plain | 900 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Alex | 2019-05-10 00:52:45 | Re: any suggestions to detect memory corruption |
Previous Message | Michael Paquier | 2019-05-10 00:36:26 | Re: copy-past-o comment in lock.h |