Re: [SQL] Transactional vs. Read-only (Retrieval) database

From: "Josh Berkus" <josh(at)agliodbs(dot)com>
To: "Samuel J(dot) Sutjiono" <ssutjiono(at)wc-group(dot)com>, <pgsql-general(at)postgresql(dot)org>, <pgsql-sql(at)postgresql(dot)org>
Subject: Re: [SQL] Transactional vs. Read-only (Retrieval) database
Date: 2002-04-11 23:16:32
Message-ID: web-1236976@davinci.ethosmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-sql

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2002-04-11 23:19:17 Re: What are functional indices good for?
Previous Message Bruce Momjian 2002-04-11 23:15:25 Re: Is there a way to look at the interactive Documentation

Browse pgsql-sql by date

  From Date Subject
Next Message Jason Earl 2002-04-12 00:00:15 Re: Inserting values into numeric fields
Previous Message Eric Carpenter 2002-04-11 22:16:37 Inserting values into numeric fields