| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16276: Server crash on an invalid attempt to attach a partition to an index |
| Date: | 2020-02-27 02:31:20 |
| Message-ID: | 20200227023120.GC1969@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Feb 26, 2020 at 05:06:24PM +0900, Michael Paquier wrote:
> Attempting to attach a table to a partitioned index? Nice thought.
> Without the assertion, RangeVarCallbackForAttachIndex complains that
> the relation is not an index, which is right, so I would be tempted to
> just remove the culprit assertion. Any thoughts?
FWIW, one can note that ALTER TABLE ATTACH PARTITION with indexes
correctly registers partition indexes without partition bounds in
pg_class, even if the grammar cannot accept ALTER TABLE without any
bounds defined:
create table idxpart(a int) partition by list (a);
create table idxpart1 partition of idxpart for values in (1);
create index idxpart_idx on only idxpart(a);
create index idxpart1_idx on only idxpart1(a);
alter table idxpart_idx attach partition idxpart1_idx for values in (0);
So I would rather not issue an error in that case on compatibility
ground.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2020-02-27 08:14:28 | Re: BUG #16276: Server crash on an invalid attempt to attach a partition to an index |
| Previous Message | Andreas Lennartsson | 2020-02-26 18:44:50 | Re: BUG #16277: xmlelement allows invalid XML characters when XML version is set to 1.0 |