Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Alexey Kondratov <a.kondratov@postgrespro.ru>
Cc: Michael Paquier <michael@paquier.xyz>, Masahiko Sawada <masahiko.sawada@2ndquadrant.com>, Steve Singer <steve@ssinger.info>, pgsql-hackers@lists.postgresql.org, Alvaro Herrera <alvherre@2ndquadrant.com>, 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-03-30T18:34:39Z
Lists: pgsql-hackers
On Mon, Mar 30, 2020 at 09:02:22PM +0300, Alexey Kondratov wrote: > Hmm, I went through the well known to me SQL commands in Postgres and a bit > more. Parenthesized options list is mostly used in two common cases: There's also ANALYZE(VERBOSE), REINDEX(VERBOSE). There was debate a year ago [0] as to whether to make "reindex CONCURRENTLY" a separate command, or to use parenthesized syntax "REINDEX (CONCURRENTLY)". I would propose to support that now (and implemented that locally). ..and explain(...) > - In the beginning for boolean options only, e.g. VACUUM You're right that those are currently boolean, but note that explain(FORMAT ..) is not boolean. > Putting it into the WITH (...) options list looks like an option to me. > However, doing it only for VACUUM will ruin the consistency, while doing it > for CLUSTER and REINDEX is not necessary, so I do not like it either. It's not necessary but I think it's a more flexible way to add new functionality (requiring no changes to the grammar for vacuum, and for REINDEX/CLUSTER it would allow future options to avoid changing the grammar). If we use parenthesized syntax for vacuum, my proposal is to do it for REINDEX, and consider adding parenthesized syntax for cluster, too. > To summarize, currently I see only 2 + 1 extra options: > > 1) Keep everything with syntax as it is in 0001-0002 > 2) Implement tail syntax for VACUUM, but with limitation for VACUUM FULL of > the entire database + TABLESPACE change > 3) Change TABLESPACE to a fully reserved word + 4) Use parenthesized syntax for all three. Note, I mentioned that maybe VACUUM/CLUSTER should support not only "TABLESPACE foo" but also "INDEX TABLESPACE bar" (I would use that, too). I think that would be easy to implement, and for sure it would suggest using () for both. (For sure we don't want to implement "VACUUM t TABLESPACE foo" now, and then later implement "INDEX TABLESPACE bar" and realize that for consistency we cannot parenthesize it. Michael ? Alvaro ? Robert ? -- Justin
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