Date: Tue, 24 Oct 2006 10:27:05 -0400 From: Vivek Khera <vivek@khera.org> To: stable@freebsd.org Subject: Re: Running large DB's on FreeBSD Message-ID: <3720CF60-DC4E-47E4-BA87-3CF8D335D286@khera.org> In-Reply-To: <453D53ED.5050403@rogers.com> References: <453D49D2.1010705@rogers.com> <3861E2E8-4232-4C46-8D0A-1B6079BCA07D@mac.com> <453D53ED.5050403@rogers.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3720CF60-DC4E-47E4-BA87-3CF8D335D286>