pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: pg12 release notes
Date: Thu, 9 May 2019 19:19:59 -0500
Message-ID: <20190510001959.GK3925@telsasoft.com> (raw)
In-Reply-To: <20190510000853.xfw2djge3evzlkjq@momjian.us>
References: <20190508203204.GA25482@telsasoft.com>
	<20190510000853.xfw2djge3evzlkjq@momjian.us>

On Thu, May 09, 2019 at 08:08:53PM -0400, Bruce Momjian wrote:
> On Wed, May  8, 2019 at 03:32:04PM -0500, Justin Pryzby wrote:
> > I think these should also be mentioned?
> > 
> > f7cb284 Add plan_cache_mode setting
> > 387a5cf Add pg_dump --on-conflict-do-nothing option.
> 
> Applied patch attached, docs updated:

Thanks, comments:

> +Author: Peter Eisentraut <peter_e@gmx.net>
> +2018-07-16 [f7cb2842b] Add plan_cache_mode setting
> +-->
> +
> +<para>
> +Allow contol over when generic plans are used for prepared statements (Pavel Stehule)

control

> +<para>
> +The server variable plan_cache_mode enables this control.

"This is controlled by the plan_cache_mode parameter".

>  Author: Tom Lane <tgl@sss.pgh.pa.us>
>  2018-12-30 [b5415e3c2] Support parameterized TidPaths.
>  Author: Tom Lane <tgl@sss.pgh.pa.us>
> @@ -2456,6 +2471,21 @@ Add --exclude-database option to pg_dumpall (Andrew Dunstan)
>  
>  <listitem>
>  <!--
> +Author: Thomas Munro <tmunro@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 ?

Justin





view thread (41+ messages)  latest in thread

Message-ID: <20190510001959.GK3925@telsasoft.com>
Permalink:  ../20190510001959.GK3925@telsasoft.com/
Also on:    postgresql.org/message-id/20190510001959.GK3925@telsasoft.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, bruce@momjian.us
  Subject: Re: pg12 release notes
  In-Reply-To: <20190510001959.GK3925@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox