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

Re: Caching by Postgres

From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Caching by Postgres
Date: 2005-08-23 20:41:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Donald(dot)Courtney(at)Sun(dot)COM (Donald Courtney) writes:
> I mean well with this comment -
> This whole issue of data caching is  a troubling issue with postreSQL
> in that even if you ran postgreSQL on a 64 bit address space
> with larger number of CPUs you won't see much of a scale up
> and possibly even a drop.   I am not alone in having the *expectation*
> that a database should have some cache size parameter and
> the option to skip the file system.   If I use oracle, sybase, mysql
> and maxdb they all have the ability to size a data cache and move
> to 64 bits.
> Is this a crazy idea - that a project be started to get this
> adopted?  Is it too big and structural to contemplate?

This project amounts to "Implement Your Own Operating System," because
it requires that the DBMS take over the things that operating systems
normally do, like:
 a) Managing access to filesystems and
 b) Managing memory

The world is already sufficiently filled up with numerous variations
of Linux, BSD 4.4 Lite, and UNIX System V; I can't see justification for
reinventing this wheel still again.
(format nil "~S(at)~S" "cbbrowne" "")
Rules of  the Evil Overlord #196.  "I will hire an  expert marksman to
stand by the entrance to my  fortress. His job will be to shoot anyone
who rides up to challenge me."  <>

In response to

pgsql-performance by date

Next:From: Chris BrowneDate: 2005-08-23 21:17:42
Subject: Re: Caching by Postgres
Previous:From: Michael StoneDate: 2005-08-23 20:29:32
Subject: Re: Caching by Postgres

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