Indeed, there are applications where this is true. Postgres will try to
keep as much in the buffers as possible. You always have to take your
application into account when tuning the database. Your case where the
database may fit entirely in RAM is quite different from a server holding
many gigabytes of data and associated index files.
--
Randy Hall - Red Hat Certified Engineer - Ex-Great Bridge PostgreSQL Expert
Resume: http://members.home.net/rthall3
----- Original Message -----
From: "Dr. Evil" <drevil@sidereal.kz>
To: <pgsql-general@postgresql.org>
Sent: Tuesday, September 11, 2001 12:12 AM
Subject: Re: [GENERAL] How to make a REALLY FAST db server?
> > As far as disks go. You cannot have too many spindles. But the number
of
> > spindles you have available depends on which pieces of postgres get
split
> > onto dedicated spindles.
>
> But if you have enough RAM that the entire DB can be held in RAM, and
> if the DB acess pattern is 90% read, 10% write (which is usually the
> case) then do you really need to worry about disk performance?
>
> It seems like for most applications, it is possible to hold all the
> data in RAM, and RAM is cheap these days.
