On 3 Oct 99, at 22:55, Scott Perkins wrote:
> fm Scott Perkins Atlanta, GA
> Guys I'd just like to say what a "luxury" problem it is to have the choice
> between two mature and proven products. In this world of Gatesville there is
> obviously plenty of market share to go around and I don't view PostgreSQL and
> Mysql as competitors but complementors. Nevertheless, it is competitivism sp?
> that is sometimes inspiring this discussion. Let's recognize this as GOOD.
> Having said that and I am still interested in learning even more about both.
> I think a fair analogy is something like the world of auto racing.
> Locally among linux devotees we have preliminarily concluded that Mysql is kind
> of the Dragster King and PostgreSQL is sort of the
> King. They each are winners. . . And you can't say which is better.
> It's like "is a saw or a hammer better ?" . . FOR WHAT? you say . . Exactly!
> No one can argue that there are clear cut environments where one will perform
> better and that is most likely a reflection of early design objectives.
> Clearly each are specialists, just like the cars. Fortunately for us as
> developers, something I have not seen mentioned because I don't think there is a
> difference is that both camps are dynamically and aggressively moving forward
> such that a big problem as we have seen is keeping up with the improvements.
> Things could be worse - huh?
> Lets focus on updating the relative comparison info so when we make the choice
> our informed decisions are based accurately.
> In this dialog, one of the most concise summaries of the two products
> was located at :
> Which admittedly contains a "dated comparison between msql, mysql, and
> The format I like. Let's point out the inaccuracies that may now exist and
> correct them.
> Surely we can find an impartial location to post the updated document if not in
> the archives of these discussions. At least at that point we can apply our own
> individual degrees of significance to the agreed upon differences.
> I have pasted the full text below relative to MYSQL AND POSTGRESQL
> let's try to use this as a working document and update it.
allmost everything is already in the crash-me test which will show
you what mysql can do and what postgres can do along other db's.
One year ago I believe or maybe longer ago I asked the hackers
mailing list of postgres to help us extending the crash-me test.
MySQL is testing a new version with it to see if everything is still
working like it should be. The crash-me test perl script can easily
extended so it won't be that hard to add some extra tests for some
specific things in postgres.
a summary will then be easily written when you have a good and
complete comparison chart of what every db can do or can't.