Re: [ADMIN] best practices for separating data and logs

2008-01-03 Thread Alvaro Herrera
Chris Browne wrote: > - Alternatively, to help establish common policies, for the "less >frequent" cases. > > env: Sets up PATH, MAN_PATH, PGPORT with the values used by > the backend in "this" init file How does this work? I have my own script to do things, and one of the pai

Re: [ADMIN] best practices for separating data and logs

2008-01-02 Thread Chris Browne
[EMAIL PROTECTED] (Tom Lane) writes: > "Peter Koczan" <[EMAIL PROTECTED]> writes: >> I'm planning a lot of changes for migrating to PostgreSQL 8.3, among >> them being a better way of separating data and logs (transaction logs, >> that is). > >> Currently, the OS and log data are on one disk system

Re: [ADMIN] best practices for separating data and logs

2008-01-02 Thread Tom Lane
"Peter Koczan" <[EMAIL PROTECTED]> writes: > I'm planning a lot of changes for migrating to PostgreSQL 8.3, among > them being a better way of separating data and logs (transaction logs, > that is). > Currently, the OS and log data are on one disk system, and the data > (including configs) are on

[ADMIN] best practices for separating data and logs

2008-01-02 Thread Peter Koczan
Hi all, I'm planning a lot of changes for migrating to PostgreSQL 8.3, among them being a better way of separating data and logs (transaction logs, that is). Currently, the OS and log data are on one disk system, and the data (including configs) are on the other disk system. After creating the da