Skip site navigation (1) Skip section navigation (2)

Re: contrib vs. gborg/pgfoundry for replication solutions

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: Barry Lind <blind(at)xythos(dot)com>, Kris Jurka <books(at)ejurka(dot)com>,PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: contrib vs. gborg/pgfoundry for replication solutions
Date: 2004-04-23 18:46:15
Message-ID: 1082745975.95625.120.camel@jester (view raw or flat)
Thread:
Lists: pgsql-hackers
> The difference is that a "better" admin tool is very subjective where as
> a buffer strategy is not... or maybe the difference is really that
> everyone thinks they are qualified to pick a "better" admin tool, but
> very few can really argue as to a better buffer strategy. While I think
> your criteria is pretty close to what I would use, I still couldn't pick
> which is the best between pgtcl/pgtclng/pgintcl or pypgsql/pygresql...
> and even I did I bet some people would have a problem with my choices. 

If you have a hard time picking between those projects, imagine the
difficulties someone who has never used PostgreSQL has just tracking
down the options available to them.

We would not be removing any choices for the user. We're simply
supplying a list of suggested tools that they may have interest in.

Getting the user to download PostgreSQL and give it a shot without
becoming frustrated because the "basics" were not available (in an
obvious location) is the first step.

Step 2 is to inform the user that there are more alternatives available.
I see pgFoundary doing a good job of #2 -- but it is not going to help
with #1 (too much choice is as bad as none at all to a beginner).


In response to

Responses

pgsql-hackers by date

Next:From: J. Andrew RogersDate: 2004-04-23 18:56:42
Subject: Re: What can we learn from MySQL?
Previous:From: Bob.HenkelDate: 2004-04-23 18:30:55
Subject: Re: PITR, nested transactions, tablespaces, 2-phase commit:

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group