| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER INDEX fails on partitioned index |
| Date: | 2020-02-28 00:11:14 |
| Message-ID: | 20200228001114.GA16911@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Feb-27, Justin Pryzby wrote:
> The attached allows CREATE/ALTER to specify reloptions on a partitioned table
> which are used as defaults for future children.
>
> I think that's a desirable behavior, same as for tablespaces. Michael
> mentioned that ALTER INDEX ONLY doesn't exist, but that's only an issue if
> ALTER acts recursively, which isn't the case here.
I think ALTER not acting recursively is a bug that we would do well not
to propagate any further. Enough effort we have to spend trying to fix
that already. Let's add ALTER .. ONLY if needed.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-02-28 00:44:40 | Allowing ALTER TYPE to change storage strategy |
| Previous Message | Alvaro Herrera | 2020-02-28 00:09:42 | Re: error context for vacuum to include block number |