From owner-freebsd-stable@FreeBSD.ORG Tue Oct 24 14:27:26 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F146716A415 for ; Tue, 24 Oct 2006 14:27:26 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id A337143D5C for ; Tue, 24 Oct 2006 14:27:13 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id BF116B81F for ; Tue, 24 Oct 2006 10:27:06 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <453D53ED.5050403@rogers.com> References: <453D49D2.1010705@rogers.com> <3861E2E8-4232-4C46-8D0A-1B6079BCA07D@mac.com> <453D53ED.5050403@rogers.com> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-3-856716149; protocol="application/pkcs7-signature" Message-Id: <3720CF60-DC4E-47E4-BA87-3CF8D335D286@khera.org> From: Vivek Khera Date: Tue, 24 Oct 2006 10:27:05 -0400 To: stable@freebsd.org X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Running large DB's on FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2006 14:27:27 -0000 --Apple-Mail-3-856716149 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Oct 23, 2006, at 7:44 PM, Mike Jakubik wrote: > I believe the front-end application is MySQL dependent, but what is > so much better about PostgreSQL? I understand that it has some more > advanced features, but if they are not used, then what is the > advantage? (I really like the InnooDB storage in MySQL) So after billions and billions of inserts/updates/deletes, how do you reclaim all that lost space in innodb? dump + reload is what I hear. also, do you value your data? ie, if you insert data which cannot be stored should the DB silently alter it or should it throw back an error for your application to decide what to do? guess which DB does which... we can go on forever on this tangent. i'd recommend finding the "gotchas" pages for both mysql and postgres and decide which is the lesser of evils for your app and go with it. for me, mysql has never won the argument :-) --Apple-Mail-3-856716149--