diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2022-04-02 19:08:34 +0200 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2022-04-02 19:08:34 +0200 |
| commit | cfdd03f45e6afc632fbe70519250ec19167d6765 (patch) | |
| tree | aaa33106f858b9170192561addd9359417e9ac71 /src/backend/access/gist/gistget.c | |
| parent | b7c485fb93726cb04b858442d73043b56e603711 (diff) | |
| download | postgresql-cfdd03f45e6afc632fbe70519250ec19167d6765.tar.gz postgresql-cfdd03f45e6afc632fbe70519250ec19167d6765.zip | |
Allow CLUSTER on partitioned tables
This is essentially the same as applying VACUUM FULL to a partitioned
table, which has been supported since commit 3c3bb99330aa (March 2017).
While there's no great use case in applying CLUSTER to partitioned
tables, we don't have any strong reason not to allow it either.
For now, partitioned indexes cannot be marked clustered, so an index
must always be specified.
While at it, rename some variables that were RangeVars during the
development that led to 8bc717cb8878 but never made it that way to the
source tree; there's no need to perpetuate names that have always been
more confusing than helpful.
Author: Justin Pryzby <pryzby@telsasoft.com>
Reviewed-by: Matthias van de Meent <boekewurm+postgres@gmail.com>
Discussion: https://postgr.es/m/20201028003312.GU9241@telsasoft.com
Discussion: https://postgr.es/m/20200611153502.GT14879@telsasoft.com
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions