Date: Tue, 5 May 2020 14:53:12 -0500
From: Justin Pryzby <pryzby@telsasoft.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
Message-ID: <20200505195312.GE28974@telsasoft.com>
References: <20200505183716.GH21185@momjian.us>
 <20200505194437.GA20275@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200505194437.GA20275@alvherre.pgsql>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On Tue, May 05, 2020 at 03:44:37PM -0400, Alvaro Herrera wrote:
> On 2020-May-05, Bruce Momjian wrote:
> > On Tue, May  5, 2020 at 12:50:11PM -0500, Justin Pryzby wrote:
> > > Do you want to include any of these?
> > > 
> > > 5823677acc Provide pgbench --show-script to dump built-in scripts.
> > > ce8f946764 Report the time taken by pgbench initialization steps.
> > 
> > I am kind of unclear how much of pgbench changes to put in the release
> > notes since the use seems so specialized, but maybe that is wrong.
> 
> Maybe it would make sense to group all pgbench changes in a subsection
> of their own?
> 
> > > a01e1b8b9d Add new part SQL/MDA to information_schema.sql_parts 33e27c3785c5ce8a3264d6af2550ec5adcebc517
> > > 2fc2a88e67 Remove obsolete information schema tables
> > 
> > Uh, that didn't seem significant.
> 
> Maybe have one item "modernize information_schema", and then describe
> all the changes together in a single item.

FYI, I did the same as last year, so I found these from output of something
like git log --cherry-pick REL_12_STABLE...master
I asked to avoid false negatives, not because I specifically want those commits
mentioned.

> > I used this text:
> > 
> > 	Allow vacuum commands run by vacuumdb to operate in parallel mode
> > 	(Masahiko Sawada)
> > 	
> > 	This is enabled with the new --parallel option.
> 
> I think the vacuumdb item should be merged with the item for 40d964ec9,
> since this is just about vacuumdb gaining control of the new VACUUM
> feature.  It's not something you can use separately from that.

+1

-- 
Justin