Re: First-draft release notes for back-branch releases
От | Amit Langote |
---|---|
Тема | Re: First-draft release notes for back-branch releases |
Дата | |
Msg-id | 5990de1a-b282-b309-10e4-dcd1542d0fb5@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: First-draft release notes for back-branch releases (Noah Misch <noah@leadboat.com>) |
Ответы |
Re: First-draft release notes for back-branch releases
|
Список | pgsql-hackers |
On 2018/11/07 11:28, Noah Misch wrote: > On Mon, Nov 05, 2018 at 10:49:30PM -0500, 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. > > Looks good. Sorry, I looked at the updated .md file only now. * Fix several crashes with triggers on partitions One of the fixed bugs involving triggers is not related to partitions [1], so I'm not sure about mentioning the phrase "on partitions" here. Thanks, Amit [1] Fix incorrect expansion of tuples lacking recently-added columns (Andrew Dunstan, Amit Langote) This is known to lead to crashes in triggers on tables with recently-added columns, and could have other symptoms as well.
В списке pgsql-hackers по дате отправления: