Re: [jforman@tecso.com.br: RES: Database comparison

Dear advocacy team,

attached find a posting from the openhealth list. The story
behind this is that a colleague of one of the posters there
(Dan Johnson at Mayo Clinics) asked the OP to help him divert
the flak he was getting at his hospital IT dept. for
proffering OS solutions. The "bad guys" compared MS SQL and
MySQL concluding the latter and thusly all OS DBs are crap
(find details in the openhealth archives).

In the course of discussion someone posted the attached
comparison between PG and MySQL (note, it is not the poster's
work). There are gaping errors in there that I wanted to bring
to your attention.

Now, the people on openhealth are typically very clever and
well-mannered if that has any influence on how you might react
to the attached posting should you choose to do so.

I already posted the URL to your site and the URL to the MySQL
Gotcha's site.

Oh, me personally, I hear you say ? Well, I am just a humble
developer with GnuMed (http://www.gnumed.org) -- based on
PostgreSQL, of course :-)

Karsten Hilbert, MD
GnuMed i18n coordinator
Leipzig, Germany
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

On Wed, Apr 21, 2004 at 10:52:40AM +0200, Karsten Hilbert wrote:

> In the course of discussion someone posted the attached
> comparison between PG and MySQL (note, it is not the poster's
> work). There are gaping errors in there that I wanted to bring
> to your attention.

This comparison is to be found in the MySQL manual. No wonder it's
somewhat biased towards their end.

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
Essentially, you're proposing Kevlar shoes as a solution for the problem
that you want to walk around carrying a loaded gun aimed at your foot.
(Tom Lane)

Karen,

I've written up some brief answers regarding the list availabel at
http://www.danlj.org/~danlj/OpenSource/Database_Comparisons.doc.html
perhaps you could forward it on?

PostgreSQL

Price: Free for commercial or non-commercial use. Extended versions are
available from several vendors as commercial offerings as well.

Relational Database: Yes

Support Views: Yes. Updatable view support is available using the PostgreSQL
Rules system.

Stored Procedures: Yes. We have an oracle like implementation in plpgsql and
also have implementations in more than half a dozen additional languages such
as plperl,plpython,pltcl,plphp,pljava, and plr

Foreign Keys: Yes

Job Schedular: No. (Due to our mostly *nix oriented install base, we
generally recommend using cron)

Multiple CPU support for Insert/Select,Update,Delete,Index: No (assuming this
is reffering to multiple CPU used on one query. We certainly support
multiple CPU's otherwise)

Send messages to DBA based on Alerts: No. (Similar to cron this is unix
functionality that we currently do not duplicate)

Data Transformations Services: Yes.

Transaction Support: Yes.

Referential Integrity: Yes.

Clustering: Commercial solutions are available from 3rd party vendors.

Robert Treat

On Wednesday 21 April 2004 04:52, Karsten Hilbert wrote:
> Dear advocacy team,
>
> attached find a posting from the openhealth list. The story
> behind this is that a colleague of one of the posters there
> (Dan Johnson at Mayo Clinics) asked the OP to help him divert
> the flak he was getting at his hospital IT dept. for
> proffering OS solutions. The "bad guys" compared MS SQL and
> MySQL concluding the latter and thusly all OS DBs are crap
> (find details in the openhealth archives).
>
> In the course of discussion someone posted the attached
> comparison between PG and MySQL (note, it is not the poster's
> work). There are gaping errors in there that I wanted to bring
> to your attention.
>
> Now, the people on openhealth are typically very clever and
> well-mannered if that has any influence on how you might react
> to the attached posting should you choose to do so.
>
> I already posted the URL to your site and the URL to the MySQL
> Gotcha's site.
>
> Oh, me personally, I hear you say ? Well, I am just a humble
> developer with GnuMed (http://www.gnumed.org) -- based on
> PostgreSQL, of course :-)
>
> Karsten Hilbert, MD
> GnuMed i18n coordinator
> Leipzig, Germany

--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

On Tue, 27 Apr 2004, Robert Treat wrote:

> Send messages to DBA based on Alerts: No. (Similar to cron this is
> unix functionality that we currently do not duplicate)

Just a side note, but with pgmail and triggers, can't this be done?

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

On Tue, 2004-04-27 at 12:13, Marc G. Fournier wrote:
> On Tue, 27 Apr 2004, Robert Treat wrote:
>
> > Send messages to DBA based on Alerts: No. (Similar to cron this is
> > unix functionality that we currently do not duplicate)
>
> Just a side note, but with pgmail and triggers, can't this be done?
>

I *think* what the above is referring to is something like "if an sql
query tosses an error, email the dba" or "if there is an authentication
failure email the dba". It might also refer to "if we have less than 5%
of disk space left email the DBA". I don't think we can do all of those
things directly inside postgresql, at least not easily (and I would be
willing to except pgmail/triggers as easy since I use them all the time
for other types of alerts) Perhaps someone with more m$ experience can
shed some light?

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

wow... i am operating on about 3 hours of sleep here... on my original
posting I need a s/Karen/Karsten/ and an apology for missing that... on
the email below i need an s/except/accept/

yeesh

Robert Treat

On Tue, 2004-04-27 at 13:58, Robert Treat wrote:
> On Tue, 2004-04-27 at 12:13, Marc G. Fournier wrote:
> > On Tue, 27 Apr 2004, Robert Treat wrote:
> >
> > > Send messages to DBA based on Alerts: No. (Similar to cron this is
> > > unix functionality that we currently do not duplicate)
> >
> > Just a side note, but with pgmail and triggers, can't this be done?
> >
>
> I *think* what the above is referring to is something like "if an sql
> query tosses an error, email the dba" or "if there is an authentication
> failure email the dba". It might also refer to "if we have less than 5%
> of disk space left email the DBA". I don't think we can do all of those
> things directly inside postgresql, at least not easily (and I would be
> willing to except pgmail/triggers as easy since I use them all the time
> for other types of alerts) Perhaps someone with more m$ experience can
> shed some light?
>
> Robert Treat
> --
> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL