Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] What can we learn from MySQL?

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "J(dot) Andrew Rogers" <jrogers(at)neopolitan(dot)com>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>,<pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: [HACKERS] What can we learn from MySQL?
Date: 2004-04-23 19:07:08
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB34101ADD5@Herge.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-hackers
J. Andrew Rogers wrote:
> No.  The greatest strength of Postgres, marketing-wise, are technical
> and is what drives its growth today. I think most of the ease-of-use
> issues are in the packaging of the larger Postgres product and
mid-level
> developer documentation, both of which seem to be eminently solvable
> problems.  I think improved default product packaging would remove 80%

plus, up to this point AFAIK the postgresql docs have not been quoted
here:

http://www.dbdebunk.com

which speaks volumes ;)

Merlin



pgsql-hackers by date

Next:From: Josh BerkusDate: 2004-04-23 19:13:15
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?
Previous:From: Robert TreatDate: 2004-04-23 19:04:53
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?

pgsql-advocacy by date

Next:From: Josh BerkusDate: 2004-04-23 19:13:15
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?
Previous:From: Robert TreatDate: 2004-04-23 19:04:53
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group