Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> I'd expect that if I have three disks and 50 databases, then I make three
> tablespaces and assign the databases to them.
In our last installment, you were complaining that you didn't want to
be bothered with that ;-)
But I don't see any reason why CREATE DATABASE couldn't take optional
parameters indicating where to create the new DB's default tablespace.
We already have a LOCATION option for it that does something close to
Come to think of it, it would probably make sense to adapt the existing
notion of "location" (cf initlocation script) into something meaning
"directory that users are allowed to create tablespaces (including
databases) in". If there were an explicit table of allowed locations,
it could be used to address the protection issues you raise --- for
example, a location could be restricted so that only some users could
create tablespaces/databases in it. $PGDATA/data would be just the
first location in every installation.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2000-07-01 17:55:56|
|Subject: Re: [PATCHES] TABLEOID patch |
|Previous:||From: Peter Eisentraut||Date: 2000-07-01 15:04:04|
|Subject: Re: config.h (was Re: Misc. consequences of backend memory