Re: ALTER TABLE ... SET STORAGE does not propagate to indexes - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: ALTER TABLE ... SET STORAGE does not propagate to indexes
Date
Msg-id 20200421235636.GA29434@alvherre.pgsql
Whole thread Raw
In response to Re: ALTER TABLE ... SET STORAGE does not propagate to indexes  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: ALTER TABLE ... SET STORAGE does not propagate to indexes  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List 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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: 2pc leaks fds
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Remove non-fast promotion Re: Should we remove a fallbackpromotion? take 2