Re: Fixed length data types issue - Mailing list pgsql-hackers

From mark@mark.mielke.cc
Subject Re: Fixed length data types issue
Date
Msg-id 20060908133358.GB24823@mark.mielke.cc
Whole thread Raw
In response to Re: Fixed length data types issue  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Fri, Sep 08, 2006 at 08:50:57AM +0200, Peter Eisentraut wrote:
> Gregory Stark wrote:
> > But it's largely true for OLTP applications too. The more compact the
> > data the more tuples fit on a page and the greater the chance you
> > have the page you need in cache.
> But a linear amount of more RAM is still more affordable than a CPU that 
> is 100 times faster, which is about what some of the proposed schemes 
> would require.

100 times faster?

I don't think it has been proven that a change in how data is stored
would result in an increase in CPU usage. It's an assumption. It might
be correct. It might not.

I guess this is where patches speak louder than words... :-)

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: Gregory Stark
Date:
Subject: Re: postgresql shared buffers
Next
From: Praveen Kumar N
Date:
Subject: Re: postgresql shared buffers