From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, 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 19:10:49 |
Message-ID: | 19454.1089486649@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> Christopher Kings-Lynne wrote:
>> 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 :(
> As long as we interpret schema and database tablespace just as default
> for future object creation, hopefully not.
But his point is that we don't --- the database tablespace is not "just
a default", it is *the place* where the system catalogs are stored, as
well as where anything else with pg_class.reltablespace = 0.
I think what we have is fine for 7.5. Later on we could look at
separating the two concepts. I'm not entirely sure what to call them
however. Also it'd be less than clear just what CREATE DATABASE should
do with cases where the values are being changed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2004-07-10 19:20:32 | Re: Nested Transactions, Abort All |
Previous Message | Alvaro Herrera | 2004-07-10 19:03:45 | Re: Weird new time zone |