Re: patch : Allow toast tables to be moved to a different tablespace - Mailing list pgsql-hackers

From Julien Tachoires
Subject Re: patch : Allow toast tables to be moved to a different tablespace
Date
Msg-id CAFEQCbESRGXLE4+tRAnazr8QmBJzfYPwc6GP1Daq0quyuyEpZQ@mail.gmail.com
Whole thread Raw
In response to Re: patch : Allow toast tables to be moved to a different tablespace  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: patch : Allow toast tables to be moved to a different tablespace  (Greg Smith <greg@2ndQuadrant.com>)
Re: patch : Allow toast tables to be moved to a different tablespace  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: patch : Allow toast tables to be moved to a different tablespace  (Jaime Casanova <jaime@2ndquadrant.com>)
List pgsql-hackers
2011/12/13 Robert Haas <robertmhaas@gmail.com>:
> On Tue, Dec 13, 2011 at 12:02 PM, Julien Tachoires <julmon@gmail.com> wrote:
>> Right, it seems to happen when the destination tablespace is the same
>> as the database's tbs, because, in this case, relation's tbs is set to
>> InvalidOid :
>> src/backend/commands/tablecmds.c line 8342
>>
>> +       rd_rel->reltablespace = (newTableSpace == MyDatabaseTableSpace) ?
>> InvalidOid : newTableSpace;
>>
>> Why don't just asign newTableSpace value here ?
>
> When a relation is stored in the default tablespace, we always record
> that in the system catalogs as InvalidOid.  Otherwise, if the
> database's default tablespace were changed, things would break.

OK, considering that, I don't see any way to handle the case raised by Jaime :(


pgsql-hackers by date:

Previous
From: Christopher Browne
Date:
Subject: Re: Command Triggers
Next
From: Alvaro Herrera
Date:
Subject: Re: libpq: PQcmdStatus, PQcmdTuples signatures can be painlessly improved