First off, welcome to the club. We're primarily an Oracle shop, but due to Oracle's pricing we are using PostGreSql for web based applications.
Why PostGreSql. Well first off it provides a much smaller learning curve for our developers than MySql does. MySql, until this last iteration, did not support stored procedures, packages, triggers, etc..... PostGreSql does and with the simple "create language plpgsql" command and one additional line in the Oracle procedure it works in PostGreSql just fine. PostGreSql can also be backed up hot, pg_dump, whereas MySql has to be shutdown. PostGreSql likes Java stored procedures, little bit more work to get initially setup, but then after your Oracle Java procedures move over almost effortlessly. Again PostGreSql handles data in a very similar fashion to Oracle. Read consistent view is there, don't count on that with MySql without the add on.
So if you or your boss is looking for a comparison it kinda falls like this:
Open Source Commercial equivalent
MySql Sql*Server or more appropriately Access.
BTW: the admin and tuning needs on PostGreSql appear to be less than Oracle, that is assuming you've setup Oracle in the usual non intelligent way.
Senior Oracle DBA
Oracle Certified 8i DBA
From: Philippe Lefevre [mailto:philippe(dot)lefevre(at)barclays(dot)co(dot)uk]
Sent: Wednesday, January 14, 2004 5:10 AM
Subject: [ADMIN] How to manage/tune PostGres
My company mainly use Oracle as database but we would like to make some
tries with some open source database.
I think PostGreSQL might be candidate for our project.
I read several documents on it, but I wasn't able to find any infos on what
are exactly the needs, in term of administration,
and, if any, how to manage/tune that database in a production context. Are
there any graphical tools to do this ?
(like OEM for example)
MySQL, an other open source database, is available. What are the reasons
that makes me happy to put my choice on PostGreSQL ?
Thank you in advance for any info.
Internet communications are not secure and therefore the Barclays Group
does not accept legal responsibility for the contents of this message.
Although the Barclays Group operates anti-virus programmes, it does not
accept responsibility for any damage whatsoever that is caused by
viruses being passed. Any views or opinions presented are solely those
of the author and do not necessarily represent those of the Barclays
Group. Replies to this email may be monitored by the Barclays Group
for operational or business reasons.
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
pgsql-admin by date
|Next:||From: Ashok Chauhan||Date: 2004-01-16 20:22:42|
|Subject: check for null value|
|Previous:||From: email@example.com||Date: 2004-01-16 18:10:11|
|Subject: Re: Is it possible in PostgreSQL?|