From owner-freebsd-isp Tue Aug 15 0:48:23 2000 Delivered-To: freebsd-isp@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id A213437B712 for ; Tue, 15 Aug 2000 00:47:54 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id OAA32871; Tue, 15 Aug 2000 14:46:06 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 15 Aug 2000 14:46:06 +0700 (NSS) From: Max Khon To: Steve Reid Cc: freebsd-isp@FreeBSD.ORG Subject: Re: FreeBSD database server questions In-Reply-To: <20000814181031.B13301@grok.localnet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, there! On Mon, 14 Aug 2000, Steve Reid wrote: > 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. we have found database corruption in PostgreSQL 7.0.2 running under FreeBSD 3.5 (and 4.x) when using secondary keys in our tables. > 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? no, no /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message