| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, 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 03:49:30 |
| Message-ID: | 360a26b8-4867-68b5-c172-127595f9b541@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Jonathan
| Attachment | Content-Type | Size |
|---|---|---|
| 20181108updaterelease.md | text/markdown | 4.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2018-11-06 03:51:34 | Re: Code of Conduct plan |
| Previous Message | Andrey Lepikhov | 2018-11-06 03:46:17 | Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages) |