> I'm having a problem with long running commits appearing in my database
> logs. It may be hardware related, as the problem appeared when we moved
> the database to a new server connected to a different disk array. The
> disk array is a lower class array, but still more than powerful enough
> to handle the IO requirements. One big difference though is that the
> old array had 16 GB of cache, the new one has 4 GB.
Maybe the old disk array had battery backed up ram that was used as a
write cache and the new only has read cache? Without battery backed up ram
(or flash or whatever) then a commit need to flush data down onto the
pysical disk.
/Dennis
