Re: ALTER TABLE ... SET STORAGE does not propagate to indexes

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER TABLE ... SET STORAGE does not propagate to indexes
Date: 2020-04-21 23:56:36
Message-ID: 20200421235636.GA29434@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'm surprised that this hasn't applied yet, because:

On 2020-Apr-09, Peter Eisentraut wrote:

> One thing to remember is that the current situation is broken. While you
> can set index columns to have different storage than the corresponding table
> columns, pg_dump does not preserve that, because it dumps indexes after
> ALTER TABLE commands. So at the moment, having these two things different
> isn't really supported.

So I have to ask -- are you planning to get this patch pushed and
backpatched?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-04-22 00:13:06 Re: Remove non-fast promotion Re: Should we remove a fallback promotion? take 2
Previous Message Alvaro Herrera 2020-04-21 23:54:22 Re: 2pc leaks fds