Sender: clark@capecod.net
Message-ID: <36F81ED9.FD1F83C3@manhattanproject.com>
Date: Tue, 23 Mar 1999 23:08:09 +0000
From: Clark Evans <clark.evans@manhattanproject.com>
MIME-Version: 1.0
To: Frank Morton <fmorton@base2inc.com>
CC: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Other JDBC Performance Question
References: <003c01be7469$23fb6a60$8355e5ce@base2inc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Frank Morton wrote:
> Is there any way to force the database to be RAM
> resident? Either with this package or something
> else?

Perhaps you could make a virtual drive, copy 
over your database, and then point postgresql to
that database.

I would make two databases... the first one
is your 'transaction' database on the hard
drive, and the second one is a 'report' database
for frequent queries.

You can have a cron job update the report database
from the transaction database on a periodic basis.

Also, I'd take advantage of the opportunity and
de-normalize the reporting database to make
the queries even faster.

Just suggestions,

:) Clark