| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | <nolan(at)celery(dot)tssi(dot)com>, "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Physical Database Configuration |
| Date: | 2003-06-27 03:06:55 |
| Message-ID: | 146801c33c59$2bee0180$2800a8c0@mars |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> > 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.
Database do not exist inside tablespaces, as they are not relations. Only
tables, views, sequences and indexes will live in tablespaces. Even then, I
probably won't bother allowing it for sequences and views since they don't
occupy much space.
A database can specify a DEFAULT tablespace, as can a schema, but they do
not live in tablespaces themselves.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-06-27 03:07:06 | Re: How many fields in a table are too many |
| Previous Message | Bruce Momjian | 2003-06-27 02:47:10 | Re: How many fields in a table are too many |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-06-27 03:08:15 | Re: [GENERAL] Physical Database Configuration |
| Previous Message | Tom Lane | 2003-06-27 02:55:45 | Re: Two weeks to feature freeze |