From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: ALTER TABLE ... SET STORAGE does not propagate to indexes
Date: Tue, 21 Apr 2020 19:56:36 -0400
Message-ID: <20200421235636.GA29434@alvherre.pgsql> (raw)
In-Reply-To: <4e53fcdd-c427-6d3b-e871-9b7af0c36b70@2ndquadrant.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, peter.eisentraut@2ndquadrant.com, kuntalghosh.2007@gmail.com
Subject: Re: ALTER TABLE ... SET STORAGE does not propagate to indexes
In-Reply-To: <20200421235636.GA29434@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox