From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John A Meinel <john(at)arbash-meinel(dot)com> |
Cc: | KeithW(at)narrowpathinc(dot)com, PostgreSQL Perform <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Moving pg_xlog |
Date: | 2005-06-02 06:06:31 |
Message-ID: | 10259.1117692391@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
John A Meinel <john(at)arbash-meinel(dot)com> writes:
> Tom Lane wrote:
>> Now that I think about it, you were (if I understood your layout
>> correctly) proposing to put the xlog on your system's root disk.
>> This is probably a bad idea for performance, ...
> I certainly agree with what you wrote. But my understanding is that if
> you only have 2 arrays, then moving xlog onto the array not on the
> database is better than having it with the database. It isn't optimum,
> but it is better. Because that way there isn't as much contention
> between the database and xlog.
If the machine isn't doing much else than running the database, then
yeah, that may be the best available option. If there are other things
going on then you have to think about how much competition there is for
the root disk.
But the impression I had from the OP's df listing is that he has several
disks available ... so he ought to be able to find one that doesn't need
to do anything except xlog.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Grega Bremec | 2005-06-02 06:32:00 | Re: 'Fastest' PC's are slowest in the house |
Previous Message | William Yu | 2005-06-02 05:00:09 | Re: Adaptec/LSI/?? RAID |