Re: BUG #15728: an index that created with keyword ONLY, when add newpartition ,should not be auto created - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #15728: an index that created with keyword ONLY, when add newpartition ,should not be auto created
Date
Msg-id CAKFQuwZh1yq8FBdBZte8TG9d_PjXMkSysoUMns9=z=Bh8g-yiw@mail.gmail.com
Whole thread Raw
In response to BUG #15728: an index that created with keyword ONLY, when add new partition ,should not be auto created  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Tue, Apr 2, 2019 at 4:04 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      15728
Logged by:          DamionZ Zhao
Email address:      zhq651@126.com
PostgreSQL version: 11.2
Operating system:   linux
Description:       
[...]
we see that index on population is created automaticly. Does it make sense?
ONLY's means is different between  created partiton and new partition.

Documented behavior.

"""
If the ONLY option is specified, no recursion is done, and the index is marked invalid. (ALTER INDEX ... ATTACH PARTITION marks the index valid, once all partitions acquire matching indexes.) Note, however, that any partition that is created in the future using CREATE TABLE ... PARTITION OF will automatically have a matching index, regardless of whether ONLY is specified.
"""


David J.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15728: an index that created with keyword ONLY, when add new partition ,should not be auto created
Next
From: Tom Lane
Date:
Subject: Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker