Date: Tue, 21 Apr 2020 19:56:36 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Kuntal Ghosh <kuntalghosh.2007@gmail.com>,
	pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: ALTER TABLE ... SET STORAGE does not propagate to indexes
Message-ID: <20200421235636.GA29434@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4e53fcdd-c427-6d3b-e871-9b7af0c36b70@2ndquadrant.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

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