X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1AD4FD1BB74 for ; Fri, 23 Apr 2004 20:46:13 -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 22808-01 for ; Fri, 23 Apr 2004 20:46:06 -0300 (ADT) Received: from lakermmtao04.cox.net (lakermmtao04.cox.net [68.230.240.35]) by svr1.postgresql.org (Postfix) with ESMTP id 5F188D1CC93 for ; Fri, 23 Apr 2004 20:46:02 -0300 (ADT) Received: from [192.168.0.13] (really [24.136.37.245]) by lakermmtao04.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040423234603.MIHB19546.lakermmtao04.cox.net@[192.168.0.13]>; Fri, 23 Apr 2004 19:46:03 -0400 From: Robert Treat To: Alexey Borzov , Josh Berkus Subject: Re: [pgsql-advocacy] What can we learn from MySQL? Date: Fri, 23 Apr 2004 19:55:16 -0400 User-Agent: KMail/1.5 Cc: Rod Taylor , pgsql-www@postgresql.org References: <200404230409.i3N49jC02890@candle.pha.pa.us> <200404231213.16003.josh@agliodbs.com> <4089770D.6060306@cs.msu.su> In-Reply-To: <4089770D.6060306@cs.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404231955.16562.xzilla@users.sourceforge.net> 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/205 X-Sequence-Number: 4309 On Friday 23 April 2004 16:05, Alexey Borzov wrote: > Josh Berkus wrote: > > > > 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. > > Okay, s/recommended/mature/ > good suggestion. > > Replication is actually several different problems demanding several > > different solutions. So no one replication solution is going to cover > > all needs, ever. > > Okay, but currently *the* replication solution that's linked from every > page of postgresql.org is pgreplication. Which is either dead or just > stinks like one. > > > 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, did you see... rod taylor i think... post in advocacy about criteria for such a page. the first 6 seemed pretty good. > Who will define "popularity"? > > Of course, it is possible to just create a page for all the GUIs, but it > will require discipline or else it will degenerate to > http://www.postgresql.org/users-lounge/related.html > or > http://www.postgresql.org/users-lounge/interfaces.html you mean like http://techdocs.postgresql.org/guides/GUITools ? Robert Treat -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL