From: Clark Evans <clark.evans@manhattanproject.com>
To: Frank Morton <fmorton@base2inc.com>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Other JDBC Performance Question
Date: Tue, 23 Mar 1999 23:08:09 +0000
Message-ID: <36F81ED9.FD1F83C3@manhattanproject.com> (raw)
References: <003c01be7469$23fb6a60$8355e5ce@base2inc.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: clark.evans@manhattanproject.com, fmorton@base2inc.com
Subject: Re: [INTERFACES] Other JDBC Performance Question
In-Reply-To: <36F81ED9.FD1F83C3@manhattanproject.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox