| From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
| Date: | 2004-08-23 03:48:14 |
| Message-ID: | 20040823004522.G93178@ganymede.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Mon, 23 Aug 2004, Philip Warner wrote:
> At 01:04 PM 23/08/2004, Marc G. Fournier wrote:
>
>> not having ALTER SCHEMA to move tablespaces is not a bug
>
> But it does make pg_dump/restore more inclined to fail, so increases the
> incidence of another bug, which can not be fixed without a global SET
> DEFAULT TABLESPACE or an ALTER SCHEMA.
'k, you lost me on that one ... how can not having ALTER SCHEMA to move a
tablespace cause a pg_dump/restore to fail? Won't the dump/restore
"store" a "CREATE SCHEMA" onto the new tablespace? Why would a
dump/restore issue an ALTER SCHEMA part way through?
Or am I missing something?
----
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 | Philip Warner | 2004-08-23 03:57:38 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
| Previous Message | Philip Warner | 2004-08-23 03:24:46 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2004-08-23 03:57:38 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |
| Previous Message | Philip Warner | 2004-08-23 03:24:46 | Re: [PATCHES] ALTER SCHEMA ... SET TABLESPACE |