Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vr8xR-00072X-Ic for pgsql-docs@arkaria.postgresql.org; Thu, 12 Dec 2013 16:17:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Vr8xR-0005Vl-1B for pgsql-docs@arkaria.postgresql.org; Thu, 12 Dec 2013 16:17:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vr8xQ-0005Vf-F3 for pgsql-docs@postgresql.org; Thu, 12 Dec 2013 16:17:48 +0000 Received: from mout.gmx.net ([212.227.15.19]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vr8xM-0006NY-Gw for pgsql-docs@postgresql.org; Thu, 12 Dec 2013 16:17:48 +0000 Received: from GK1C05 ([80.130.244.62]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MHokD-1VpmRe1M7B-003ddU for ; Thu, 12 Dec 2013 17:17:43 +0100 Date: Thu, 12 Dec 2013 17:18:02 +0100 From: Wolfgang Keller To: pgsql-general@postgresql.org Cc: pgsql-docs@postgresql.org Subject: Re: postgresql.org inconsistent (Re: [GENERAL] PG replication across DataCenters) Message-Id: <20131212171802.51bf444e2cb0cace64d7b256@gmx.net> In-Reply-To: References: <52A5EB31.7070505@nybeta.com> <9F208972-32D3-4295-A30D-BCDAEF139E9F@silentmedia.com> <20131210174738.a530d930b8fd1e972d84f234@gmx.net> <52A74907.8040400@hogranch.com> <20131210202425.4e54580731cba8190987d525@gmx.net> <24304.1386704630@sss.pgh.pa.us> <20131211191911.856d8850f2e3bfc6e21eca4b@gmx.net> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.10.14; i686-pc-mingw32) Mail-Copies-To: never Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:jmOpFXULstJbQHdleeGE+Hg3KphfAAaeBYLYQIPv6/VV7+GYSw3 2C1rD5bHQnLfsjTv4WhhKvL6vgEXDtSGNM5vErUPHI12G/ioZ8v/pg+OmiQNRONAJwOnpwG 16jI1AzONZOID5/2eo6HGM9mltTieyDOXtalwoB2AyoB5zstBNvg1B1yqkdtVvImjsatUL5 H744hrNQLFeC9KXVLoytQ== X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org I should have cross-posted this to pgsql-docs from the beginning, sorry for the mistake. For pgsql-docs readers: The issue is that the official documentation misleadingly omits the existence of Postgresql-XC: http://www.postgresql.org/docs/9.3/static/different-replication-solutions.html? > Synchronous Multimaster Replication *snip* > PostgreSQL does not offer this type of replication (...) Whereas the wiki says in http://wiki.postgresql.org/wiki/Postgres-XC > Project Overview *snip* > Features of PG-XC include: *snip* > 2. Synchronous multi-master configuration Now back to the original thread: > Knowing the number of forks/projects based on Postgres, maintaining a > list on a wiki list the one below is just easier for everybody: > http://wiki.postgresql.org/wiki/Replication,_Clustering,_and_Connection_Pooling That one doesn't even list PostgreSQL-XC. For how man years has it been around now... Can't even remember any more. Instead it lists Postgres-R, which has been in koma for how long now... Can't even remember any more. BTW; No, I don't suffer from that brain disease that makes you lose your memory (can't remember the name of it any more... ;-). > Perhaps this list is not completely up-to-date, To call that an understatement would be an euphemism. It's simply misleading. And misleading potential users in search of solutions for their needs is *bad* for the PostgreSQL project. > but not adding that in the core documentation facilitates the work of > core maintainers. It gives you all the information you need as well. Guys, are you really not aware to *that* point how badly you shoot yourself (and the PostgreSQL project as a whole) in the foot with that single - wrong - phrase in the "official" documentation: "PostgreSQL does not offer this type of replication" Reading that phrase, the average O***** DBA looking for a cheaper replacement will stop considering PostgreSQL and that's it. You're out of business. They won't look any further. Just stop arguing and put *one* *single* *phrase* in the official documentation instead like: "PostgreSQL itself does not provide this as a built-in functionality at the current stage, but there is an open-source "fork" freely available under the same license as PostgreSQL that does, for details read: http://wiki.postgresql.org/wiki/Postgres-XC" Is that really too much work? Heck, give me write-authority on the documentation and I'll do it for you then. You've already wasted *way* more brain bandwidth and precious time arguing why that phrase is *not* there than it would take to put it there once for good. That's the kind of pointy-haired dysfunctionality I'd expect from a managed corporation, not from an open-source project. In fact I would guess that given how closely PostgreSQL-XC follows the releases of "pure" PostgreSQL and the fact that they use the same license, at some stage it may be merged entirely. Sincerely, Wolfgang -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs