I concur 100%. PostgreSQL was big and scary and MySQL seemed cute and cuddly, warm and fuzzy. Then I took my undergrad CS RDBMS course (a course that focused on designing the backend software), and only then was I ready to appreciate and wield the battle axe that is PostgreSQL.
He also let me use PostgreSQL for my final project (the standard was Oracle). I got an A. :) I do have to admit that I prefer OSS (and docs) better than proprietary. I had some Informix work and that was not fun at all. So even though the MySQL is pink fuzzy bunnies, PostgreSQL is at least a brown fuzzy bunny [to me anyway]. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > scott.marlowe > Sent: Thursday, October 09, 2003 3:26 PM > To: Jeff > Cc: David Griffiths; [EMAIL PROTECTED] > Subject: Re: [PERFORM] PostgreSQL vs MySQL > > > On Thu, 9 Oct 2003, Jeff wrote: > > > On Thu, 9 Oct 2003, David Griffiths wrote: > > > > > 1) the MySQL docs are better (sorry - I found them easier to read, and > > > more comprehensive; I had an easier time finding the answers I needed) > > > > Huh. I had the opposite experience. Each to his own. > > I think everybody agrees PG needs a better tuning doc (or > pointers to it, > > or something). > > I think the issue is that Postgresql documentation is oriented > towards DBA > types, who already understand databases in general, so they can find what > they want, while MySQL docs are oriented towards dbms newbies, who don't > know much, if anything, about databases. > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match > ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
