From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
---|---|
To: | Julien Tachoires <julmon(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: patch : Allow toast tables to be moved to a different tablespace |
Date: | 2011-11-16 05:49:49 |
Message-ID: | CAJKUy5iMp-NE=24WSNQt5Npp0SLkPTDkqVz9C8D9y=pdK=eFoQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 15, 2011 at 11:08 AM, Julien Tachoires <julmon(at)gmail(dot)com> wrote:
>
> Maybe I'd missed something, but the normal case is :
> ALTER TABLE ... SET TABLESPACE => moves Table + moves associated TOAST Table
> ALTER TABLE ... SET TABLE TABLESPACE => moves Table & keeps associated
> TOAST Table at its place
> ALTER TABLE ... SET TOAST TABLESPACE => keeps Table at its place &
> moves associated TOAST Table
>
it has docs, and pg_dump support which is good.
but i found a few problems with the behaviour:
1) it accepts the sintax ALTER INDEX ... SET TOAST TABLESPACE ...;
which does nothing
2) after CLUSTER the index of the toast table gets moved to the same
tablespace as the main table
3) after ALTER TABLE ... ALTER ... TYPE ...; the toast table gets
moved to the same tablespace as the main table
now, if we are now supporting this variants
ALTER TABLE SET TABLE TABLESPACE
ALTER TABLE SET TOAST TABLESPACE
why not also support ALTER TABLE SET INDEX TABLESPACE which should
have the same behaviour as ALTER INDEX SET TABLESPACE... just an idea,
and of course not necessary for this patch
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2011-11-16 07:37:43 | Re: Displaying accumulated autovacuum cost |
Previous Message | Dan Ports | 2011-11-16 05:37:38 | Re: FlexLocks |