From owner-freebsd-isp Mon Aug 14 23:57:56 2000 Delivered-To: freebsd-isp@freebsd.org Received: from toad.com (toad.com [140.174.2.1]) by hub.freebsd.org (Postfix) with ESMTP id 1661A37B724 for ; Mon, 14 Aug 2000 23:57:49 -0700 (PDT) (envelope-from sreid@sea-to-sky.net) Received: from grok.localnet (unknown@bc-van-nws-a53-02-63.look.ca [216.66.139.159]) by toad.com (8.7.5/8.7.3) with ESMTP id SAA16979 for ; Mon, 14 Aug 2000 18:11:03 -0700 (PDT) Received: by grok.localnet (Postfix, from userid 1000) id 4E5BB212E07; Mon, 14 Aug 2000 18:10:31 -0700 (PDT) Date: Mon, 14 Aug 2000 18:10:31 -0700 From: Steve Reid To: freebsd-isp@freebsd.org Subject: FreeBSD database server questions Message-ID: <20000814181031.B13301@grok.localnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I will soon be setting up a database (among other things, for now) server running FreeBSD 4.1-R. This will be doing the usual web-type transaction processing. Any tips? Specifically... I'd prefer to run an open-source RDBMS; PostgreSQL and Interbase look like the contenders (I'm not interested in MySQL). First-hand experiences? I'll probably end up testing them both but if there's anything specific I should be watching out for I'd like to know beforehand. Vinum? RAID-1 mirroring seems to be a minimum. Can I assume that RDBMSs will be able to take advantage of RAID-10 concurrency? The vinum man page has a "gotchas" section; any other foot-shooters I should be aware of? Also, what about softupdates? As I understand it, softupdates is like async writes except the writes are re-ordered so as to prevent the disk from ever being left in a corrupt state. Is it possible for this delaying and re-ordering to interfere with a RDBMS's ACIDity? Should I stick with sync writes for the RDBMS space? TIA. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message