Scott Carey <sc...@richrelevance.com> writes:
> Great points. There is one other option that is decent for the WAL:
> If splitting out a volume is not acceptable for the OS and WAL -- absolutely
> split those two out into their own partitions. It is most important to make
> sure that WAL and data are not on the same filesystem, especially if ext3 is
> involved.
Uh, no, WAL really needs to be on its own *spindle*. The whole point
here is to have one disk head sitting on the WAL and not doing anything
else except writing to that file. Pushing WAL to a different partition
but still on the same physical disk is likely to be a net pessimization,
because it'll increase the average seek distance whenever the head does
have to move between WAL and everything-else-in-the-database.
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
