On Wed, May  8, 2019 at 03:32:04PM -0500, Justin Pryzby wrote:
> I noticed you added release notes at bdf595adbca195fa54a909c74a5233ebc30641a1,
> thanks for writing them.
> 
> I reviewed notes; find proposed changes attached+included.
> 
> I think these should also be mentioned?
> 
> f7cb284 Add plan_cache_mode setting
> 387a5cf Add pg_dump --on-conflict-do-nothing option.

I am confused how I missed these.  There is only one commit between
them, and I suspect I deleted them by accident.  I hope those are the
only ones.

> a6da004 Add index_get_partition convenience function

A C function just isn't normally mentioned in the release notes.

> 17f206f Set pg_class.relhassubclass for partitioned indexes

I need help with this one.  I know the system column existed in previous
releases, so how is it different now?  Do we document system table
changes that are implementation-behavior in the release notes?  Usually
we don't.

Applied patch attached, docs updated:

        http://momjian.us/pgsql_docs/release-12.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 816c8309e5..8bffb0ae03 100644
--- a/doc/src/sgml/release-12.sgml
+++ b/doc/src/sgml/release-12.sgml
@@ -717,6 +717,21 @@ forced by specifying NOT MATERIALIZED.  Previously, CTEs 
were never inlined and
 
 <listitem>
 <!--
+Author: Peter Eisentraut <pete...@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)
+</para>
+
+<para>
+The server variable plan_cache_mode enables this control.
+</para>
+</listitem>
+
+<listitem>
+<!--
 Author: Tom Lane <t...@sss.pgh.pa.us>
 2018-12-30 [b5415e3c2] Support parameterized TidPaths.
 Author: Tom Lane <t...@sss.pgh.pa.us>
@@ -2456,6 +2471,21 @@ Add --exclude-database option to pg_dumpall (Andrew 
Dunstan)
 
 <listitem>
 <!--
+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>
+
+<para>
+The pg_dump option is --on-conflict-do-nothing.
+</para>
+</listitem>
+
+<listitem>
+<!--
 Author: Tom Lane <t...@sss.pgh.pa.us>
 2018-09-14 [548e50976] Improve parallel scheduling logic in pg_dump/pg_restore.
 -->

Reply via email to