Re: Simplifying wal_sync_method - Mailing list pgsql-hackers

From mark@mark.mielke.cc
Subject Re: Simplifying wal_sync_method
Date
Msg-id 20050810055657.GA18549@mark.mielke.cc
Whole thread Raw
In response to Re: Simplifying wal_sync_method  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Aug 09, 2005 at 11:01:36PM -0400, Tom Lane wrote:
> Andrew - Supernews <andrew+nonews@supernews.com> writes:
> >> If a SCSI drive reports write complete when it hasn't actually put the
> >> bits on the platter yet, then it's simply broken.
> > I guess you haven't read the spec much, then.
> [ shrug... ]  I have seen that spec before: I was making a living by
> implementing SCSI device drivers in the mid-80's.  I think that anyone
> who uses WCE in place of tagged command queueing is not someone whose
> code I would care to rely on for mission-critical applications.  TCQ
> is a design that just works; WCE is someone's attempt to emulate all
> the worst features of IDE.

They're relying on you, not you on them.

Is their reliance founded upon reasonable logic, or are they unreasonably
putting the fault in your court? Depends on the issue...

Many people would not like to need to know these 'under the hood' type
issues. This doesn't mean they deserve to have their databases
corrupted to teach them the hard way why these 'under the hood' type
details are useful to know... :-)

Cheers,
mark

-- 
mark@mielke.cc / markm@ncf.ca / markm@nortel.com     __________________________
.  .  _  ._  . .   .__    .  . ._. .__ .   . . .__  | Neighbourhood Coder
|\/| |_| |_| |/    |_     |\/|  |  |_  |   |/  |_   | 
|  | | | | \ | \   |__ .  |  | .|. |__ |__ | \ |__  | Ottawa, Ontario, Canada
 One ring to rule them all, one ring to find them, one ring to bring them all                      and in the darkness
bindthem...
 
                          http://mark.mielke.cc/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Simplifying wal_sync_method
Next
From: Adrian Maier
Date:
Subject: Re: Simplifying wal_sync_method