From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
Date: | 2004-08-23 14:41:34 |
Message-ID: | 20040823114108.O4215@ganymede.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mon, 23 Aug 2004, Bruce Momjian wrote:
> Philip Warner wrote:
>> At 03:15 PM 23/08/2004, Tom Lane wrote:
>>
>>> I thought the idea was for pg_dump to emit something like
>>>
>>> SET magic_tablespace_variable = some_ts;
>>> CREATE TABLE foo (columns...);
>>>
>>> rather than
>>>
>>> CREATE TABLE foo (columns...) TABLESPACE some_ts;
>>>
>>> the point being...
>>
>> Yep.
>
> This brings up another issue. We now dump a non-standard clause from
> pg_dump when using tablespaces:
>
> CREATE TABLE xx (
> y integer
> ) TABLESPACE tmp;
>
> We avoided this with oids but it seems we have added another. I don't
> see a good way of avoiding this like we had with oids.
Isn't that what hte proposed (or implemented?) "SET DEFAULT_TABLESPACE"
was for?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-23 14:43:25 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
Previous Message | Oliver Elphick | 2004-08-23 14:19:26 | Re: monetary bug |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-23 14:43:25 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
Previous Message | Bruce Momjian | 2004-08-23 14:09:33 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |