pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: scott.marlowe <scott.marlowe@ihs.com>
To: Peter Galbavy <peter.galbavy@knowtion.net>
Cc: Iain <iain@mst.co.jp>
Cc: Shane Wright <me@shanewright.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: hanging for 30sec when checkpointing
Date: Mon, 9 Feb 2004 09:58:34 -0700 (MST)
Message-ID: <Pine.LNX.4.33.0402090956580.23974-100000@css120.ihs.com> (raw)
In-Reply-To: <009101c3ed69$1e637790$24e0a8c0@sonylaptop>
On Sat, 7 Feb 2004, Peter Galbavy wrote:
> scott.marlowe wrote:
> > Also, running on SCSI drives will be much faster than running on IDE
> > drives if the IDE drives have their caches disabled like they should,
> > since they lie otherwise. Since SCSI disks don't usually lie, and are
> > designed to handle multiple requests in parallel, they are much
> > faster as parallel load increases. If you're writing a lot, you
> > should either have a great number of IDE drives with the write cache
> > turned off, like some of the newer storage devices made of ~100 IDE
> > drives, or you should have SCSI. SCSI's advantage won't be as great
> > as the number of drives approaches infinity. But for 1 to 10 drives
> > my guess is that SCSI is gonna be a clear winner under parallel load.
>
> Nice to see old fashioned misinformation being spread around the place...
I don't know who you think you are, but I've physically tested the stuff
I'm talking about. Care to qualify what you mean?
IDE drives (all the ones I've ever tested) LIE about their write caches
and fsync. don't believe me? Simple, hook one up, initiate 100 parallel
transactions, pull the power plug, watch your database fail to come back
up due to the corruption caused by the LYING IDE drives.
Do the same with SCSI. watch the database come right back to life.
If you're gonna accuse me of lying, you damned well better have the balls
AND evidence to back it up.
view thread (33+ messages) latest in thread
Message-ID: <Pine.LNX.4.33.0402090956580.23974-100000@css120.ihs.com> Permalink: ../Pine.LNX.4.33.0402090956580.23974-100000@css120.ihs.com/ Also on: postgresql.org/message-id/Pine.LNX.4.33.0402090956580.23974-100000@css120.ihs.com ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-admin@postgresql.org Cc: scott.marlowe@ihs.com, peter.galbavy@knowtion.net, iain@mst.co.jp, me@shanewright.co.uk Subject: Re: hanging for 30sec when checkpointing In-Reply-To: <Pine.LNX.4.33.0402090956580.23974-100000@css120.ihs.com> References: <009101c3ed69$1e637790$24e0a8c0@sonylaptop> <Pine.LNX.4.33.0402090956580.23974-100000@css120.ihs.com> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox