Re: Using ALTER TABLESPACE in pg_dump

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Using ALTER TABLESPACE in pg_dump
Date: 2004-10-25 23:15:05
Message-ID: 6.1.2.0.0.20041026090716.09131228@203.8.195.10
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 08:00 AM 26/10/2004, Tom Lane wrote:
>I don't want a GUC variable that actively changes the default
>tablespace; at least not unless you want to abandon the current
>mechanisms for default tablespace choices entirely, and go over to
>making the GUC variable be the sole arbiter.

Something consistent with Schemas does sound good to me; a tablespace
search path (or just single default), and support for a TABLESPACE clause
on table and INDEX definitions would be good.

For the three largest databases I work on, the namespace/schema that a
table resides in is irrelevant to the tablespace that it should be stored
in. So default tablespaces on the schema are a bit of a pointless feature.
The ability to have the features of schemas: default tablespace for given
users, a GUC variable, and ACLs on tablespaces would be far more valuable.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp.mit.edu:11371 |/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-10-25 23:28:46 Re: Using ALTER TABLESPACE in pg_dump
Previous Message Tom Lane 2004-10-25 23:11:05 Re: [PATCHES] ARC Memory Usage analysis