Re: First-draft release notes for back-branch releases - Mailing list pgsql-hackers

From Amit Langote
Subject Re: First-draft release notes for back-branch releases
Date
Msg-id adb7754d-dc85-a65c-46cc-75bd96facc87@lab.ntt.co.jp
Whole thread Raw
In response to Re: First-draft release notes for back-branch releases  ("Jonathan S. Katz" <jkatz@postgresql.org>)
Responses Re: First-draft release notes for back-branch releases
List pgsql-hackers
Hi,

On 2018/11/06 12:49, Jonathan S. Katz wrote:
> On 11/5/18 9:58 PM, Amit Langote wrote:
>> On 2018/11/06 11:25, Noah Misch wrote:
>>> On Mon, Nov 05, 2018 at 04:01:59PM -0500, Jonathan S. Katz wrote:
>>>> Attached is a draft of the press release for review. Please let me know
>>>> if there are any corrections/suggestions.
>>>> * Disallows the creation of a new partition from a trigger that is attached to its parent table to prevent a
crash;this behavior could be modified in a future release
 
>>>> * Fix that prevents crashes in triggers on tables with recently added columns
>>>
>>> I would replace these two with "Fix crashes in triggers".  The details are too
>>> esoteric, for the first especially, to list here.
>>
>> +1
> 
> Thanks for the feedback. I made the suggested changes upthread as well
> as the above. Please see attached.
> 
> Funny enough I had a simplified version of the "trigger crashes" in my
> first draft, but I thought about expanding it given that future behavior
> could change.
> 
> I still feel inclined to elaborate on the "Prevent creation of a
> partition in a trigger attached to its parent table" but perhaps in
> future release we will just mention that this behavior is again available.

Maybe, it's enough that that detail is present in the release note item?

Thanks,
Amit



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Tid scan improvements
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Two pass CheckDeadlock in contentent case