| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | pgsql(at)mohawksoft(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tablespaces and DB administration |
| Date: | 2004-05-27 01:40:29 |
| Message-ID: | 40B5470D.6000804@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> BTW: Is there a public spec on what will be tablespace compatible and how?
> For instance: will is be possible to create a table on a separate
> tablespace than the DB? Will it be possible to create an index on a
> separate tablespace than the table?
(Since Gavin hasn't replied yet)
1. There are two default tablespaces, global and default. Global is for
shared catalogs, default is for all other catalog data.
2. By default databases are created in the default tablespace, you can
override this.
3. By default schemas are created in the database's tablepsace, but this
can be overridden.
5. Tables and sequences are created in the schema's tablespace by
default, but this can be overridden
6. Indexes and SERIAL sequences are created in the table's tablespace by
default, but this can be overridden.
When pg_dumping, care is taken so that the tablespace qualification is
only dumped if the object is in its 'non-default' tablespace.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-27 02:06:13 | Re: SELECT * FROM <table> LIMIT 1; is really slow |
| Previous Message | Christopher Kings-Lynne | 2004-05-27 01:36:33 | Re: SELECT * FROM <table> LIMIT 1; is really slow |