Re: [SQL] Transactional vs. Read-only (Retrieval) database - Mailing list pgsql-general

From Josh Berkus
Subject Re: [SQL] Transactional vs. Read-only (Retrieval) database
Date
Msg-id web-1236976@davinci.ethosmedia.com
Whole thread Raw
In response to Transactional vs. Read-only (Retrieval) database  ("Samuel J. Sutjiono" <ssutjiono@wc-group.com>)
List pgsql-general
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

pgsql-general by date:

Previous
From:
Date:
Subject: user question
Next
From: noy
Date:
Subject: Date precision problem