From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Using ALTER TABLESPACE in pg_dump |
Date: | 2004-11-06 03:37:35 |
Message-ID: | 24570.1099712255@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> Time is at a serious premium for me at the moment (I have several projects
> all due about now); but I wrote a patch for this a few weeks back, so it
> should not be a lot of work (unless pg_dump has changed in the last couple
> of months).
If you have a preliminary patch, you could pass it along and I'll finish
it up.
> Excellent. I assume that anything that can have a tablespace (database,
> schema(?), table and index -- anything else?) should emit a 'set
> default_tablespace="ts"' before creation (and that this will affect
> auto-created indexes as appropriate, whatever that means).
default_tablespace will affect both tables and auto-created indexes.
But I was under the impression that pg_dump deliberately avoids
auto-creation of indexes... isn't each one split out as an ADD
CONSTRAINT operation?
Schemas don't have tablespaces anymore.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-11-06 04:38:52 | Release schedule plans |
Previous Message | Philip Warner | 2004-11-06 02:27:51 | Re: Using ALTER TABLESPACE in pg_dump |