Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id E0E0A4764AB; Thu, 11 Apr 2002 19:16:30 -0400 (EDT) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9) with HTTP id 1236976; Thu, 11 Apr 2002 16:16:32 -0700 From: "Josh Berkus" Subject: Re: [SQL] Transactional vs. Read-only (Retrieval) database To: "Samuel J. Sutjiono" , , X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Thu, 11 Apr 2002 16:16:32 -0700 Message-ID: In-Reply-To: <003801c1e15a$c03c5450$110a010a@headquarters.wcgroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200204/606 X-Sequence-Number: 23321 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