From: Peter Eisentraut <peter_e@gmx.net>
To: Bruce Momjian <pgman@candle.pha.pa.us>,
	PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: What can we learn from MySQL?
Date: Fri, 23 Apr 2004 15:45:49 +0200
User-Agent: KMail/1.5.4
Cc: PostgreSQL advocacy <pgsql-advocacy@postgreSQL.org>
References: <200404230409.i3N49jC02890@candle.pha.pa.us>
In-Reply-To: <200404230409.i3N49jC02890@candle.pha.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200404231545.49523.peter_e@gmx.net>

Am Freitag, 23. April 2004 06:09 schrieb Bruce Momjian:
> 	o  Are we marketing ourselves properly?
> 	o  Are we focused enough on ease-of-use issues?
> 	o  How do we position ourselves against a database that some
> 	   say is "good enough" (MySQL), and another one that some
> 	   say is "too much"  (Oracle)
> 	o  Are our priorities too technically driven?

Success is not measured by absolute number of installations.  You can measure 
success by having enough users so that the project can continue, enough users 
so you can make a living, more satisfied users than unsatisfied ones, more 
heavy-duty installations than personal database-driven websites, and by 
having a product that you feel good about.  The only way to position 
ourselves is as the relational database with the best price/performance 
ration (price = TOC, performance = features + speed).  And the only way to 
achieve any of these goals is by focussing on technology and ease of use.  
For the crowd out there, PostgreSQL is an exciting and growing topic.  That's 
more important than the installation count.