Date: Sun, 12 Nov 2006 04:14:04 -0800 From: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com> To: Vivek Khera <vivek@khera.org> Cc: stable@freebsd.org Subject: Re: Running large DB's on FreeBSD Message-ID: <0E89703C-987A-45A6-8281-D714FF9D4036@develooper.com> In-Reply-To: <3720CF60-DC4E-47E4-BA87-3CF8D335D286@khera.org> References: <453D49D2.1010705@rogers.com> <3861E2E8-4232-4C46-8D0A-1B6079BCA07D@mac.com> <453D53ED.5050403@rogers.com> <3720CF60-DC4E-47E4-BA87-3CF8D335D286@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 24, 2006, at 7:27 AM, Vivek Khera 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. If you've configured it properly you can just do "optimize table foo". > 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... Not MySQL if you configure/ask it not to. - ask -- http://www.askbjoernhansen.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0E89703C-987A-45A6-8281-D714FF9D4036>