Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Alvaro Herrera <alvherre@2ndquadrant.com>

Cc: Justin Pryzby <pryzby@telsasoft.com>, Alexey Kondratov <a.kondratov@postgrespro.ru>, Masahiko Sawada <masahiko.sawada@2ndquadrant.com>, Steve Singer <steve@ssinger.info>, pgsql-hackers@lists.postgresql.org, Robert Haas <robertmhaas@gmail.com>, Alexander Korotkov <a.korotkov@postgrespro.ru>, Masahiko Sawada <sawada.mshk@gmail.com>, Jose Luis Tallon <jltallon@adv-solutions.net>

Date: 2020-09-02T01:48:34Z

Lists: pgsql-hackers

On Tue, Sep 01, 2020 at 09:29:28PM -0400, Alvaro Herrera wrote:
> Seems sensible, but only to be done when actually needed, right?

Of course.
--
Michael

Commits

Add TABLESPACE option to REINDEX
- c5b286047cd6 14.0 landed
Refactor code in tablecmds.c to check and process tablespace moves
- 4c9c359d38ff 14.0 landed
Refactor option handling of CLUSTER, REINDEX and VACUUM
- a3dc926009be 14.0 landed
pg_dump: Don't use enums for defining bit mask values
- d2a2808eb444 14.0 landed
Refactor CLUSTER and REINDEX grammar to use DefElem for option lists
- b5913f612079 14.0 landed
Refactor parsing rules for option lists of EXPLAIN, VACUUM and ANALYZE
- 873ea9ee692e 14.0 landed
Improve tab completion of REINDEX in psql
- 1f75b454134c 14.0 landed
Fix possible crash during FATAL exit from reindexing.
- d12bdba77b0f 13.0 cited