I didn't mean to "throw rocks" at either MySql or PostgreSQL. I really like PostgreSQL and use it myself at home. I'm just very conservative about my data. I.e. I don't think (could be wrong) that PostgreSQL has all the tools for recovering from problems that DB2 has. I.e. forward recovery logs and the like. Suppose, for instance, that I have a number of interrelated tables. Something happens to destroy the contents of one of them. My last backup is from 2 days ago. How do I forward recover that table? I am not aware of MySQL or PostgreSQL having a "transaction log" such as DB2 has. That was all that I was trying to get at. As I said, I'm paranoid about production data <grin>.
-- John McKown Senior Systems Programmer UICI Insurance Center Applications & Solutions Team +1.817.255.3225 This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. > -----Original Message----- > From: David Andrews [mailto:[EMAIL PROTECTED] > Sent: Friday, August 22, 2003 9:13 AM > To: [EMAIL PROTECTED] > Subject: Re: MySql > > > On Fri, 2003-08-22 at 09:00, McKown, John wrote: > > Another possibility, with a longer history, is PostgreSQL. > But, in all > > fairness, I would resist that as well. > > John, could you explain this? I haven't seen many people > throw rocks at > PostgreSQL. > > -- > David Andrews > A. Duda and Sons, Inc. > [EMAIL PROTECTED] >
