Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: Tim Conrad <tim@timconrad.org>,
 "Marc G. Fournier" <scrappy@postgresql.org>
Subject: Re: Upcoming Features WAS: What can we learn from MySQL?
Date: Tue, 27 Apr 2004 10:39:52 -0700
User-Agent: KMail/1.4.3
Cc: PostgreSQL advocacy <pgsql-advocacy@postgresql.org>
References: <200404262213.44601.jm@poure.com>
	<20040427165746.GA1873@external.timconrad.org>
	<200404271030.28173.josh@agliodbs.com>
In-Reply-To: <200404271030.28173.josh@agliodbs.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200404271039.52552.josh@agliodbs.com>

Tim, Folks:
> I guess there's a perception that we are "above" the marketeering of MySQL
> and Microsoft, where features are promised as much as 6 years before they
> appear, or are heavily publicized while still in alpha.   So the most you'd
> be likely to get the community to commit to is maintaining a list of
> easy-to-read "Major Features in Development".

Actually, I really like this idea.  It could go like:

Feature				Lead			Status	
Improved Memory Use		Jan Wieck		Complete, Committed for 7.5
HA M-S Replication		Jan Wieck		Alpha testing
PITR					Simon Riggs	Early Development
Tablespaces			Gavin Sherry	Late Development
Integrated pg_autovacuum	Matthew O'Con.	Planning
Server Clustering		None			Developer Needed
etc.

As well as giving the press something to look at, this would give programmers 
and corporate sponsors an idea of where their time/money would be of use.  
And it could put to bed the myth that we're not constantly improving.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco