X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id F261AD1D1D5
	for <pgsql-advocacy-postgresql.org@localhost.postgresql.org>;
	Fri, 23 Apr 2004 19:31:14 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 06408-02
	for <pgsql-advocacy-postgresql.org@localhost.postgresql.org>;
	Fri, 23 Apr 2004 19:31:15 -0300 (ADT)
Received: from curie.credativ.org (credativ.com [217.160.209.18])
	by svr1.postgresql.org (Postfix) with ESMTP id 108B1D1D076
	for <pgsql-advocacy@postgresql.org>;
	Fri, 23 Apr 2004 19:31:13 -0300 (ADT)
Received: from localhost (localhost [127.0.0.1])
	by curie.credativ.org (Postfix) with ESMTP
	id 6B95155EFA; Sat, 24 Apr 2004 00:31:15 +0200 (CEST)
Received: from colt.pezone.net (dsl-082-082-234-094.arcor-ip.net
	[82.82.234.94]) (using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by curie.credativ.org (Postfix) with ESMTP
	id B90EE55EF7; Sat, 24 Apr 2004 00:31:14 +0200 (CEST)
From: Peter Eisentraut <peter_e@gmx.net>
To: Alexey Borzov <borz_off@cs.msu.su>, Rod Taylor <pg@rbt.ca>
Subject: Re: What can we learn from MySQL?
Date: Sat, 24 Apr 2004 00:31:13 +0200
User-Agent: KMail/1.5.1
Cc: Postgresql Advocacy <pgsql-advocacy@postgresql.org>
References: <200404230409.i3N49jC02890@candle.pha.pa.us>
	<1082730417.95625.41.camel@jester> <40893F5A.50607@cs.msu.su>
In-Reply-To: <40893F5A.50607@cs.msu.su>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200404240031.13661.peter_e@gmx.net>
X-Virus-Scanned: by AMaViS at credativ.com
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200404/174
X-Sequence-Number: 4146

Alexey Borzov wrote:
> I think that PostgreSQL's "download" page should point to at least
> * 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

A couple of months ago I grew tired of having to find all the PostgreSQL 
pieces all over the net, plus having to get them to get along with each 
other and the rest of the system.  So I started packaging and 
collecting them here: <http://www.unitedpostgresql.org/>.  It's already 
saved me a bunch of time.  Feel free to take from it.