agora inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feedFrom: Justin Pryzby <pryzby@telsasoft.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Alexey Kondratov <a.kondratov@postgrespro.ru>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Cc: Steve Singer <steve@ssinger.info>
Cc: pgsql-hackers@lists.postgresql.org, Robert Haas <robertmhaas@gmail.com>
Cc: Alexander Korotkov <a.korotkov@postgrespro.ru>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Jose Luis Tallon <jltallon@adv-solutions.net>
Subject: Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly
Date: Wed, 3 Feb 2021 00:53:42 -0600
Message-ID: <20210203065342.GX7450@telsasoft.com> (raw)
In-Reply-To: <YBpEsxZxIVn0zyFM@paquier.xyz>
References: <20210127213658.GA736@alvherre.pgsql>
<55c6c1526b94d2caf54c33262fe00674@postgrespro.ru>
<e15777decc533006c9dbe4988bd66d31@postgrespro.ru>
<YBTC0IYIGmyYfiIn@paquier.xyz>
<1c506564e2a732ec17790bd8c34f042e@postgrespro.ru>
<YBiro+n0767QDXSA@paquier.xyz>
<YBpEsxZxIVn0zyFM@paquier.xyz>
On Wed, Feb 03, 2021 at 03:37:39PM +0900, Michael Paquier wrote:
> index 627b36300c..4ee3951ca0 100644
> --- a/doc/src/sgml/ref/reindex.sgml
> +++ b/doc/src/sgml/ref/reindex.sgml
> @@ -293,8 +311,30 @@ REINDEX [ ( <replaceable class="parameter">option</replaceable> [, ...] ) ] { IN
> respectively. Each partition of the specified partitioned relation is
> reindexed in a separate transaction. Those commands cannot be used inside
> a transaction block when working on a partitioned table or index.
> + If a <command>REINDEX</command> command fails when run on a partitioned
> + relation, and <literal>TABLESPACE</literal> was specified, then it may not
> + have moved all indexes to the new tablespace. Re-running the command
> + will rebuild again all the partitions and move previously-unprocessed
remove "again"
> + indexes to the new tablespace.
> + </para>
> +
> + <para>
> + When using the <literal>TABLESPACE</literal> clause with
> + <command>REINDEX</command> on a partitioned index or table, only the
> + tablespace references of the partitions are updated. As partitioned indexes
I think you should say "of the LEAF partitions ..". The intermediate,
partitioned tables are also "partitions" (partitioned partitions if you like).
> + are not updated, it is recommended to separately use
> + <command>ALTER TABLE ONLY</command> on them to achieve that.
Maybe say: "..to set the default tablespace of any new partitions created in
the future".
--
Justin
view thread (154+ messages) latest in thread
Message-ID: <20210203065342.GX7450@telsasoft.com>
Permalink: ../20210203065342.GX7450@telsasoft.com/
Also on: postgresql.org/message-id/20210203065342.GX7450@telsasoft.com
reply
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: pryzby@telsasoft.com, michael@paquier.xyz, a.kondratov@postgrespro.ru, alvherre@alvh.no-ip.org, peter.eisentraut@enterprisedb.com, masahiko.sawada@2ndquadrant.com, steve@ssinger.info, robertmhaas@gmail.com, a.korotkov@postgrespro.ru, sawada.mshk@gmail.com, jltallon@adv-solutions.net
Subject: Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly
In-Reply-To: <20210203065342.GX7450@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox