| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER xx SET TABLESPACE (was bug in DROP TABLESPACE) |
| Date: | 2004-07-07 07:46:45 |
| Message-ID: | 40EBAA65.9040209@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne wrote:
>> Its questionable if these are to be interpreted as just changing the
>> default tablespace for subsequent creates, or also moving all objects
>> that were created using the previous tablespace. Since it's
>> indistinguishable whether an object was created using the default
>> from schema/database or given a tablespace explicitely (unless
>> default was 0), I'd opt for version one.
>
>
> I meant option one - I hadn't considered the second. The thing is
> though you have to maybe move some stuff on disk as well.
Currently not in case of schema (until we have a placeholder file); for
database, certainly the directory structure needs to be created and the
old removed if empty. AFAICS no move of data is necessary.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-07-07 07:56:02 | Re: nested-xacts cursors (was Re: Performance with new |
| Previous Message | Gavin Sherry | 2004-07-07 07:44:18 | Re: ALTER xxx SET TABLESPACE (was bug in DROP TABLESPACE) |