From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Alexander Staubo <alex(at)bengler(dot)no> |
Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: I/O increase after upgrading to 8.3.5 |
Date: | 2009-02-14 08:49:05 |
Message-ID: | 49968581.7070205@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Alexander Staubo wrote:
> On Fri, Feb 13, 2009 at 12:53 PM, Alexander Staubo <alex(at)bengler(dot)no> wrote:
>> The upgrade was done with dump/restore using "pg_dump -Fc". The old
>> database lived on a SAN volume, whereas the new database lives on a
>> local disk volume.
>
> I need to correct myself: The Munin graphs were never set to track the
> SAN volume where the old database lived. So when the graph goes from
> "near-zero" to "lots", it's actually correct.
>
> When I compare the correct graph, however, it's apparently that I/O
> writes have, on average, doubled.
Is there any chance you had pg_xlog stored separately on your old
database, and I/O for it wasn't being recorded?
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar Mallah | 2009-02-14 11:58:32 | Re: scheduling autovacuum at lean hours only. |
Previous Message | Craig Ringer | 2009-02-14 08:46:07 | Re: dissimilar drives in Raid10 , does it make difference ? |