Skip site navigation (1) Skip section navigation (2)

Re: 500 tpsQL + WAL log implementation

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Curtis Faith <curtis(at)galtcapital(dot)com>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: 500 tpsQL + WAL log implementation
Date: 2003-05-26 18:20:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Bruce Momjian wrote:
> Jan Wieck wrote:
>>Bruce Momjian wrote:
>>>If we could somehow know the platter location, or tell the disk drive to
>>>write it in several locations, whichever is closest, I think we would
>>>have a real win.  However, I don't see any way of doing that.
>>>Imagine what we could do with 8mb of battery-backed RAM!  This is sort
>>>of what we are using WAL/disk for, and it really isn't very good at it.
>>Isn't that what modern disk drives have ... well, not exactly battery 
>>backed, but actually the energy they have in the rotation is enough to 
>>flush the "write cache" out to the surface and get the heads back into 
>>the parking position in the case of a power loss.
> That's what I am not sure about --- if those drives return a 'complete'
> before getting the actual data on the drive, then we don't have a
> rotational delay problem because it isn't waiting for the platter to
> spin into place, _and_ the data is secure.

The option is called "Immediate SCSI Error Reporting" ;-)


# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-05-26 18:23:34
Subject: Re: Removing a user's password
Previous:From: Bruce MomjianDate: 2003-05-26 18:20:06
Subject: Re: [HACKERS] ECPG thread-safety

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group