Re: First-draft release notes for back-branch releases

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: First-draft release notes for back-branch releases
Date: 2018-11-06 04:10:25
Message-ID: adb7754d-dc85-a65c-46cc-75bd96facc87@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2018-11-06 04:16:00 Re: [HACKERS] Two pass CheckDeadlock in contentent case
Previous Message Tatsuo Ishii 2018-11-06 04:02:25 Re: Code of Conduct plan,Re: Code of Conduct plan