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

Alvaro Herrera <alvherre@2ndquadrant.com>

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>

Date: 2020-03-30T16:17:20Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Propagate ALTER TABLE ... SET STORAGE to indexes
- 03a8a5f2d4a1 11.8 landed
- bf7233ee4a54 12.3 landed
- 501e41dd3cb9 13.0 landed

On 2020-Feb-25, Peter Eisentraut wrote:

> An alternative would be that we make this situation fully supported. Then
> we'd probably need at least ALTER INDEX ... ALTER COLUMN ... SET STORAGE,
> and some pg_dump support.

I think this is a more promising direction.

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