From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: First draft of the PG 15 release notes |
Date: | 2022-05-11 02:38:26 |
Message-ID: | 8ce639d4-a9b9-2042-6a6f-5a91717be8b0@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 5/10/22 9:48 PM, Bruce Momjian wrote:
> On Tue, May 10, 2022 at 09:16:33PM -0400, Tom Lane wrote:
>> "Jonathan S. Katz" <jkatz(at)postgresql(dot)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. :-(
Got it.
I did a scan of the release notes and diff'd with the 14.[1-3] and did
not find any additional overlap.
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2022-05-11 02:41:00 | Re: First draft of the PG 15 release notes |
Previous Message | Justin Pryzby | 2022-05-11 02:38:19 | Re: First draft of the PG 15 release notes (sorting) |