On Feb 25, 2007, at 04:39 , Carlos Moreno wrote:
I do have the option to configure it in RAID-0, but I'm sort of
reluctant; I think
there's the possibility that having two filesystems that can be
accessed truly
simultaneously can be more beneficial. The question is: does
PostgreSQL
have separate, independent areas that require storage such that
performance
would be noticeably boosted if the multiple storage operations
could be done
simultaneously?
Putting the WAL (aka pg_xlog) on a separate disk will take some load
off your main database disk. See http://www.varlena.com/GeneralBits/
Tidbits/perf.html for this.
It is also possible to put individual tables and/or indexes on
separate disks by using tablespaces: "For example, an index which is
very heavily used can be placed on a very fast, highly available
disk, such as an expensive solid state device. At the same time a
table storing archived data which is rarely used or not performance
critical could be stored on a less expensive, slower disk
system." (http://www.postgresql.org/docs/8.2/interactive/manage-ag-
tablespaces.html)
In both cases, the performance benefits tend to be relative to the
amount of write activity you experience, and the latter solution
assumes you know where the hotspots are. If you have two tables that
see continuous, intense write activity, for example, putting each on
a separate disk
Alexander.
