From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ALTER INDEX fails on partitioned index |
Date: | 2019-01-07 19:34:08 |
Message-ID: | 20190107193408.GD25379@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 07, 2019 at 04:23:30PM -0300, Alvaro Herrera wrote:
> On 2019-Jan-05, Justin Pryzby wrote:
>
> > 12dev and 11.1:
> >
> > postgres=# CREATE TABLE t(i int)PARTITION BY RANGE(i);
> > postgres=# CREATE INDEX ON t(i) WITH(fillfactor=11);
> > postgres=# ALTER INDEX t_i_idx SET (fillfactor=12);
> > ERROR: 42809: "t_i_idx" is not a table, view, materialized view, or index
> > LOCATION: ATWrongRelkindError, tablecmds.c:5031
> >
> > I can't see that's deliberate,
>
> Well, I deliberately ignored that aspect of the report at the time as it
> seemed to me (per discussion in thread [1]) that this behavior was
> intentional. However, if I think in terms of things like
> pages_per_range in BRIN indexes, this decision seems to be a mistake,
> because surely we should propagate that value to children.
>
> [1] https://www.postgresql.org/message-id/flat/CAH2-WzkOKptQiE51Bh4_xeEHhaBwHkZkGtKizrFMgEkfUuRRQg%40mail.gmail.com
I don't see any discussion regarding ALTER (?)
Actually, I ran into this while trying to set pages_per_range.
But shouldn't it also work for fillfactor ?
Thanks,
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2019-01-07 20:56:59 | Re: WIP: Avoid creation of the free space map for small tables |
Previous Message | Nikolay Shaplov | 2019-01-07 19:30:08 | Re: Problem with parallel_workers option (Was Re: [PATCH] get rid of StdRdOptions, use individual binary reloptions representation for each relation kind instead) |