From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | nolan(at)celery(dot)tssi(dot)com |
Cc: | shridhar_daithankar(at)persistent(dot)co(dot)in (Shridhar Daithankar), pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Physical Database Configuration |
Date: | 2003-06-26 14:52:02 |
Message-ID: | 25058.1056639122@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
nolan(at)celery(dot)tssi(dot)com writes:
> I disagree. Just as you can have multiple schemas within one database
> you can have multiple tablespaces within one database.
> And the tablespace is irrelevant as far as specifying an object is concerned.
> A fully qualified object would be:
> database.schema.object,
> not tablespace.database.schema.object or database.tablespace.schema.object.
Right, the tablespace structure is really orthogonal to the
database/schema structure.
I would envision tablespaces as being named by database-cluster-wide
names, just as users and groups are. Any given table could be placed
in any tablespace (although perhaps we want to invent some permission
mechanism here).
Physically a tablespace is a directory with sub-directories for
databases under it --- so $PGDATA/base plays the role of the default
tablespace for a cluster. (The reason you need per-database
sub-directories is mostly to support DROP DATABASE, which has to be
able to nuke a database without knowing exactly what's in it.) But
this structure doesn't have anything to do with the logical structure
of the database cluster.
There are a bunch of interesting locking issues to be solved, but the
storage layout ideas are pretty clear in my mind.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | greg | 2003-06-26 14:57:27 | Re: selecting the record before the last one |
Previous Message | Tom Lane | 2003-06-26 14:35:34 | Re: Query plan question |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2003-06-26 15:18:43 | Re: A portable code question |
Previous Message | Ryan Mack | 2003-06-26 14:32:02 | Feature request: set planner flags on views |