<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 13, 2009, at 7:52 PM, Sir Gallantmon wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Sun, Dec 13, 2009 at 8:48 PM, Bruno Wolff III <span dir="ltr"><<a href="mailto:bruno@wolff.to">bruno@wolff.to</a>></span> wrote:<br><div><br></div><div>I dunno. While I did push for the CMS project I work on to support PostgreSQL, I personally think that Postgres is huge overkill for most things. It can also be a huge PITA to set up. Whenever I have to test Postgres stuff, I usually grab EnterpriseDB's distribution because I don't want to suffer hell setting it up on the various platforms I have to test on. </div></div></blockquote><div><br></div>As a DBA / Developer, I second this... obviously I can't complain because they are both free. However the setup/configuration of postgreSQL compared to MySQL is basically something easy, versus something where I don't have a clue what is going on, and there are million ways to do it, and when I'm done I have no idea if I'm wide open to the entire world, or as secure as on MySQL. There are a few other odd bits too, I mean I really don't get the purpose of copying template1, what is that? etc etc etc... MySQL is just more intuitive.</div></body></html>