| From: | "Birchall, Austen" <austen(dot)birchall(at)metoffice(dot)gov(dot)uk> |
|---|---|
| To: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | tablespace - datafile location |
| Date: | 2013-08-15 09:59:07 |
| Message-ID: | 4E154FB60786D74BB4DFDC97BF991CAC08A92C@EXXCMPD1DAG2.cmpd1.metoffice.gov.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
9.2 on Red Hat 6
Up to now I have been creating the sub-directories that (hold) the OS level files that are associated with individual tablespaces directly under the
..../psql/data directory i.e.
db=# create tablespace test owner test_admin location '/var/lib/pgsql/data/test';
Is this standard/best practise - I can see that the data directory could get 'cluttered' in a db that has many tablespaces.
Is there a standard/recommended alternative for tablespace location for db which have many tablespaces?
Thanks in advance as always
Austen
Austen Birchall Senior Database Administrator
Met Office
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Athanasios Kostopoulos | 2013-08-15 14:04:01 | Re: sudo/access to the postres OS user |
| Previous Message | Birchall, Austen | 2013-08-15 09:51:58 | sudo/access to the postres OS user |