public inbox for [email protected]  

help / color / mirror / Atom feed

From: Wolfgang Keller <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: postgresql.org inconsistent (Re: [GENERAL] PG replication across DataCenters)
Date: Thu, 12 Dec 2013 17:18:02 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAB7nPqQ4uq7CfsYZ3VsA7fpuFnwMVOQZYkr6-1JNnYxnxKtQdw@mail.gmail.com>
References: <CAD7Ssm9S__ZQCOq2GEN0G0rrs_4U6aqXiLaX0hh0Ts8JH_LY2w@mail.gmail.com>
	<A737B7A37273E048B164557ADEF4A58B17C5ED75@ntex2010i.host.magwien.gv.at>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAB7nPqQ4uq7CfsYZ3VsA7fpuFnwMVOQZYkr6-1JNnYxnxKtQdw@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

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 ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

view thread (36+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: postgresql.org inconsistent (Re: [GENERAL] PG replication across DataCenters)
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox