From: Josh Berkus <josh@agliodbs.com>
To: Samuel J. Sutjiono <ssutjiono@wc-group.com>
To: pgsql-general@postgresql.org
To: pgsql-sql@postgresql.org
Subject: Re: [SQL] Transactional vs. Read-only (Retrieval) database
Date: Thu, 11 Apr 2002 16:16:32 -0700
Message-ID: <web-1236976@davinci.ethosmedia.com> (raw)
In-Reply-To: <003801c1e15a$c03c5450$110a010a@headquarters.wcgroup.com>
Sam,
> I'd like to get some opinions if there are any benefits (i.e. in
> terms of performance) of creating two separate databases, one for
> transactions (insert, update, delete) and the other one is for
> retrieval/search (select).
No. Not in Postgresql, unless you wanted to get really exotic. Also,
keep in mind that you cannot join tables from seperate databases in
postgresql.
There are *lots* of performance advantages to be had by managing disk
access and memory carefully. But not through seperate databases.
-Josh Berkus
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-sql@postgresql.org
Cc: josh@agliodbs.com, ssutjiono@wc-group.com, pgsql-general@postgresql.org
Subject: Re: [SQL] Transactional vs. Read-only (Retrieval) database
In-Reply-To: <web-1236976@davinci.ethosmedia.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