| From: | nolan(at)celery(dot)tssi(dot)com |
|---|---|
| To: | shridhar_daithankar(at)persistent(dot)co(dot)in (Shridhar Daithankar) |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Physical Database Configuration |
| Date: | 2003-06-26 14:25:19 |
| Message-ID: | 20030626142519.32753.qmail@celery.tssi.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> That should be
>
> Tablespaces
> databases
> schemas
> objects
>
> with each of them implemented as a directory and data files under it. If we
> could get a quota check propogated in both direction, that would be pretty
> good, may be a warning when things start getting close to limit.
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.
--
Mike Nolan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-06-26 14:35:34 | Re: Query plan question |
| Previous Message | Tom Lane | 2003-06-26 14:05:35 | Re: INSERT WHERE NOT EXISTS |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Mack | 2003-06-26 14:32:02 | Feature request: set planner flags on views |
| Previous Message | Tom Lane | 2003-06-26 14:01:59 | Re: row description for domain in 7.4 |