Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Vacuums on large busy databases
- From: Francisco Reyes <lists(at)stringsutils(dot)com>
- To: Jim C. Nasby <jimn(at)enterprisedb(dot)com>
- Cc: Pgsql performance <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: Vacuums on large busy databases
- Date: Mon, 18 Sep 2006 20:21:16 -0400
- Message-id: <cone(dot)1158625276(dot)426992(dot)91426(dot)5001(at)35st-server(dot)simplicato(dot)com>
Jim C. Nasby writes:
BTW, on some good raid controllers (with battery backup and write-caching), putting pg_xlog on a seperate partition doesn't really help, so you might want to try combining everything.
Planning to put a busy database on second raid or perhaps some index files. So far the second raid is highly under utilized.
Even if you stay with 2 partitions, I'd cut pg_xlog back to just a simple mirror.
I am considering to put the pg_xlog back to the main raid. Primarily because we have two hot spares.. on top of RAID 10.. so it is safer.
- References:
- Vacuums on large busy databases
- From: Francisco Reyes
- Re: Vacuums on large busy databases
- From: Jim C. Nasby
- Vacuums on large busy databases
- Prev by Date: LIKE query problem
- Next by Date: Re: Large tables (was: RAID 0 not as fast as expected)
- Previous by thread: Re: Vacuums on large busy databases
- Next by thread: RAID 0 not as fast as expected
- Indexes: