Re: ALTER INDEX fails on partitioned index - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: ALTER INDEX fails on partitioned index
Date
Msg-id 201901071923.7r2xflxvncly@alvherre.pgsql
Whole thread Raw
In response to ALTER INDEX fails on partitioned index  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: ALTER INDEX fails on partitioned index  (Justin Pryzby <pryzby@telsasoft.com>)
Re: ALTER INDEX fails on partitioned index  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
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

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Doc client_min_messages patch vis. INFO message severity
Next
From: Nikolay Shaplov
Date:
Subject: Re: Problem with parallel_workers option (Was Re: [PATCH] get rid of StdRdOptions, use individual binary reloptions representation for each relation kind instead)