From: | "Lane Van Ingen" <lvaningen(at)esncc(dot)com> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Question About Tablespaces in Windows Environment under PostgreSQL 8.0 |
Date: | 2005-08-24 14:32:43 |
Message-ID: | EKEMKEFLOMKDDLIALABIMEMBCBAA.lvaningen@esncc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
One of the environments we are using PostgreSQL 8.0 in is Windows 2003,
single-disk, non-logging environment.
- Can somebody comment on the advantages of using / not using pg_default vs.
a separate tablespace for non-template databases, outside of the ability to
control separation tables and indexes into two separate tablespaces, etc. ?
Are there any disadvantages outside of not being able to place a tablespace
on a separate disk?
- If I do not use pg_default, how do I get the file system attributes right
for a new tablespace? Being as the installation is to be completely
automated, does anybody know what DOS commands (like ATTRIB) have to be used
to set up a new tablespace location (directory) properly for PostgreSQL use?
Are there considerations as to what user the .bat file install file is run
by, being as it seems that PostgreSQL prefers that the username under which
an install is done may not be the same username that exercises the DBA
functions ?
From | Date | Subject | |
---|---|---|---|
Next Message | Ivan | 2005-08-24 15:50:44 | help me to explain database behaviour after vacuum. |
Previous Message | Aldor | 2005-08-24 13:56:22 | Re: ERROR: _mdfd_getrelnfd: cannot open relation pg_class: |