pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jonathan S. Katz <jkatz@postgresql.org>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: First draft of the PG 15 release notes
Date: Tue, 10 May 2022 21:48:10 -0400
Message-ID: <YnsV2uUb65m3ZNKf@momjian.us> (raw)
In-Reply-To: <35419.1652231793@sss.pgh.pa.us>
References: <YnqIT8kpiO3m6SD7@momjian.us>
	<20220510180935.GB19626@telsasoft.com>
	<YnrIgnhIq4RnHmoy@momjian.us>
	<745d3a6e-d766-8a63-0dc2-f88ae9ed4511@postgresql.org>
	<35419.1652231793@sss.pgh.pa.us>

On Tue, May 10, 2022 at 09:16:33PM -0400, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz@postgresql.org> writes:
> > On 5/10/22 4:18 PM, Bruce Momjian wrote:
> > |  Allow libpq's SSL private to be owned by the root user (David Steele)
> 
> > This was backpatched to all supported versions[1]. While I'm a huge fan 
> > of this behavior change for a plethora of reasons, I'm not sure if this 
> > should be included as part of the PG15 release notes, given it's in the 
> > 14.3 et al.
> 
> It should not.  However, the backpatch happened later than the commit
> to HEAD, and our git_changelog tool is not smart enough to match them
> up, so Bruce didn't see that there were followup commits.  That's a
> generic hazard for major-release notes; if you spot any other cases
> please do mention them.

Yes, known problem.  :-(

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson






view thread (145+ messages)  latest in thread

Message-ID: <YnsV2uUb65m3ZNKf@momjian.us>
Permalink:  ../YnsV2uUb65m3ZNKf@momjian.us/
Also on:    postgresql.org/message-id/YnsV2uUb65m3ZNKf@momjian.us

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers@postgresql.org
  Cc: bruce@momjian.us, tgl@sss.pgh.pa.us, jkatz@postgresql.org, pryzby@telsasoft.com
  Subject: Re: First draft of the PG 15 release notes
  In-Reply-To: <YnsV2uUb65m3ZNKf@momjian.us>
  References: <YnqIT8kpiO3m6SD7@momjian.us> <20220510180935.GB19626@telsasoft.com> <YnrIgnhIq4RnHmoy@momjian.us> <745d3a6e-d766-8a63-0dc2-f88ae9ed4511@postgresql.org> <35419.1652231793@sss.pgh.pa.us> <YnsV2uUb65m3ZNKf@momjian.us>

* 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