From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bug in DROP TABLESPACE |
Date: | 2004-07-10 07:59:14 |
Message-ID: | 40EFA1D2.8070900@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> The latter is relatively trivial as long as you interpret it as just
> changing the default TS for tables created later in that schema.
> (On the other hand, you can fake that with a simple UPDATE to
> pg_namespace, so I'm not sure it qualifies as a "must have".)
>
> The former is a real mess since it would require moving some of the
> system catalogs. (At least the nailed-in-cache ones, but I'm not sure
> we've yet determined which ones *have* to be in the database's default
> tablespace.) It'll be fairly entertaining to move pg_class in
> particular, but I doubt you can build such a thing out of the available
> spare parts at all.
>
> My vote would be to postpone any such patch to 7.6 (or 8.1 as the case
> may be), because it's a nontrivial addition of functionality and we had
> no prototype as of July 1.
It seems to me that we have mixed up two concepts: the tablespaces that
a database is IN and the default tablespaces for any schemas created in
that tablespace. This will probably cause trouble further down the track :(
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-07-10 08:08:19 | Re: Weird new time zone |
Previous Message | Andreas Pflug | 2004-07-10 07:50:32 | Re: Nested Transactions, Abort All |