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-07 06:59:13 |
Message-ID: | 65241c7f-78c6-0ee1-2ffc-c291e6cc6de9@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2018/11/07 13:08, Jonathan S. Katz wrote:
> Thanks. I left it as "Fix several crashes with triggers" - please see
> attached.
Thank you. Just one more comment on the top sentence.
* Ensure that if a parent partition has an index created in a tablespace,
then all child indexes will be created in that same tablespace
I think this should be rewritten to not say "parent partition", because
it's a bit confusing to call parent a partition. Also, how about
mentioning "automatically created" for child indexes? Like this:
* Ensure that automatically created child indexes are created in the same
tablespace as the parent partitioned index
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-11-07 07:16:04 | Re: Why do pg_upgrade's test use the serial schedule? |
Previous Message | Amit Langote | 2018-11-07 06:34:38 | Re: move PartitionBoundInfo creation code |