Обсуждение: Comparison of Postgres vs MySQL

I found this on the web.(I don't know when it was published.) The comments
on the stability concerns me. Has anyone experienced this?

http://sun.med.ru/~phd/Software/SQL/PostgreSQL-vs-MySQL.html


Stoffel van Aswegen
stoffelva@bigfoot.com

It's unlucky to be superstitious.

Stoffel van Aswegen <Stoffelva@gmsi.co.za> writes:
> I found this on the web.(I don't know when it was published.) The comments
> on the stability concerns me. Has anyone experienced this?

Oleg reads the pgsql lists, or at least used to, so he may respond
himself.  (If not, try asking on pgsql-general.)  But I will note
that this page doesn't seem to have been updated since v6.5:

    : Certainly, 6.5 was MUCH better that 6.4,
    : and I hope 7.0 will be better that 6.5, but...

7.0 fixed a boatload of problems, and I expect 7.1 will fix more...

            regards, tom lane

* Stoffel van Aswegen <Stoffelva@gmsi.co.za> [001016 22:46] wrote:
> I found this on the web.(I don't know when it was published.) The comments
> on the stability concerns me. Has anyone experienced this?
>
> http://sun.med.ru/~phd/Software/SQL/PostgreSQL-vs-MySQL.html

7.0.2 has fixed all but one of our problems.

Tom Lane (one of the core members of the developement team) was
able to diagnose our final problem and provide a fix within 12
hours of us providing sufficient debugging information.

His patch should be in 7.0.3 which should come out in about a week,
there's no reason to worry about 7.0.2 unless you're doing insane
amounts of intensive activity and one will be able to upgrade to
7.0.3 by simply shutting down, installing 7.0.3 and restarting the
7.0.3 version.  (or you can compile from the -PATCHES branch from
CVS)

Yes, there were some rough edges with 6.x and the early 7.0/7.0.1
releases but it's really solid with version 7.0.2.

--
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
"I have the heart of a child; I keep it in a jar on my desk."

Alfred Perlstein <bright@wintelcom.net> writes:
> Tom Lane (one of the core members of the developement team) was
> able to diagnose our final problem and provide a fix within 12
> hours of us providing sufficient debugging information.

Now, now, it's only a proposed fix.  If you haven't seen any more
problems in a week or three, I'll start to believe it's a real fix...

            regards, tom lane