Re: Large Database Design Help

Поиск
Список
Период
Сортировка
Искать
От
Ragnar
Тема
Re: Large Database Design Help
Дата
Msg-id
1139611194.17929.105.camel@localhost.localdomain
Ответ на
Список
Дерево обсуждения
Large Database Design Help Orion Henry <lab@orangekids.org>
Re: Large Database Design Help "Jim C. Nasby" <jnasby@pervasive.com>
Re: Large Database Design Help Markus Schaber <schabi@logix-tt.com>
Re: Large Database Design Help Ragnar <gnari@hive.is>
Re: Large Database Design Help Scott Marlowe <smarlowe@g2switchworks.com>
Re: Large Database Design Help Greg Stark <gsstark@mit.edu>
Re: Large Database Design Help Markus Schaber <schabi@logix-tt.com>
Re: Large Database Design Help Matthew Nuzum <mattnuzum@gmail.com>
Re: Large Database Design Help PFC <lists@peufeu.com>
On Fri, 2006-02-10 at 11:24 +0100, Markus Schaber wrote:

> For lots non-read-only database workloads, RAID5 is a performance
> killer. Raid 1/0 might be better, or having two mirrors of two disks
> each, the first mirror holding system, swap, and the PostgreSQL WAL
> files, the second one holding the data.

I was under the impression that it is preferable to keep the WAL on 
its own spindles with no other activity there, to take full advantage
of the sequential nature of the WAL writes.

That would mean one mirror for the WAL, and one for the rest.
This, of course, may sometimes be too much wasted disk space, as the WAL
typically will not use a whole disk, so you might partition this mirror
into a small ext2 filesystem for WAL, and use the rest for files seldom 
accessed, such as backups. 

gnari


В списке pgsql-performance по дате отправления
От: Tim Jones
Дата:
От: Scott Marlowe
Дата:
FAQ