Re: [INTERFACES] Other JDBC Performance Question

From: Clark Evans <clark(dot)evans(at)manhattanproject(dot)com>
To: Frank Morton <fmorton(at)base2inc(dot)com>
Cc: pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] Other JDBC Performance Question
Date: 1999-03-23 23:08:09
Message-ID: 36F81ED9.FD1F83C3@manhattanproject.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

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

In response to

Browse pgsql-interfaces by date

  From Date Subject
Next Message Dalphin, Mark 1999-03-23 23:58:59 RE: Other JDBC Performance Question
Previous Message Matthew 1999-03-23 18:46:10 Problem using Having in a sub-query wit the Count function.