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 65241c7f-78c6-0ee1-2ffc-c291e6cc6de9@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/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



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: move PartitionBoundInfo creation code
Next
From: Peter Eisentraut
Date:
Subject: Re: Why do pg_upgrade's test use the serial schedule?