From: | "Weber, Johann (ISS Kassel)" <jweber(at)iss(dot)net> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Data and logs on different physical drives - advantage? |
Date: | 2005-10-10 14:40:39 |
Message-ID: | B8ADDBDA8696F546BDAC69B469D7F0511DABF5@kasmaiexcp01.iss.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks, after playing around a little I found that placing the indices
on a different drive gave a real performance increase in my scenario.
Johann
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, October 10, 2005 4:35 PM
To: Weber, Johann (ISS Kassel)
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Data and logs on different physical drives -
advantage?
"Weber, Johann (ISS Kassel)" <jweber(at)iss(dot)net> writes:
> Is this true for PostgreSQL (V 8.0 on ReadHat)? My tests do not show
> any speed gained when placing pg_clog and pg_xlog on a different
drive.
The conventional wisdom is that it's a win to have pg_xlog on a drive by
itself. The above is not that. pg_clog is more in the nature of data,
and in any case you lose the advantage as soon as the drive handling
pg_xlog has to move the head away from the current xlog file.
Whether any particular test case would show an advantage is another
question of course. In a heavy-write scenario I would think you could
probably measure a win.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-10-10 16:31:32 | Re: Compression of text columns |
Previous Message | Tom Lane | 2005-10-10 14:34:50 | Re: Data and logs on different physical drives - advantage? |