Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: Robert Treat <xzilla@users.sourceforge.net>,
	Alexey Borzov <borz_off@cs.msu.su>
Subject: Re: [pgsql-advocacy] What can we learn from MySQL?
Date: Fri, 23 Apr 2004 12:13:15 -0700
User-Agent: KMail/1.4.3
Cc: Rod Taylor <pg@rbt.ca>, pgsql-www@postgresql.org
References: <200404230409.i3N49jC02890@candle.pha.pa.us>
	<40893F5A.50607@cs.msu.su> <1082746966.25537.1155.camel@camel>
In-Reply-To: <1082746966.25537.1155.camel@camel>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200404231213.16003.josh@agliodbs.com>

Folks,

> > * Recommended replication solution (erserver?)
> > * Recommended full-text search solution (tsearch?)
> > * Recommended GUI / web frontend (PGAdmin / phpPgAdmin)
> > * Drivers: ODBC, JDBC, whatever
> > * PostGIS
> > * Banners to put on the website
> > * A description of what to find in the contrib dir

I'm really nervous about pointing to "recommended" solutions where we have 
several.   I'd rather have links to all mature projects in that category.

Replication is actually several different problems demanding several different 
solutions.   So no one replication solution is going to cover all needs, 
ever.

For GUIs, we have an embarassment of them, and I would not want to be 
responsible for telling anyone their project is "not recommended".  That's an 
effective way of making a lot of enemies in the OSS community.   Instead, I 
might suggest listing all OSS GUIs in order of popularity -- which still lets 
PGAdmin & phpPGAdmin float to the top, but without telling Xpg or PGAccess to 
take a flying leap into the void.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco