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

Re: [HACKERS] Replication documentation addition

From: Markus Schaber <schabi(at)logix-tt(dot)com>
To:
Cc: PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Replication documentation addition
Date: 2006-10-25 14:16:14
Message-ID: 453F71AE.5070106@logix-tt.com (view raw or flat)
Thread:
Lists: pgsql-docspgsql-hackers
Hi, Cesar,

Cesar Suga wrote:
> If people (who read the documentation) professionally work with
> PostgreSQL, they may already have been briefed by those commercial
> offerings in some way.
> 
> I think only the source and its tightly coupled (read: can compile along
> with, free as PostgreSQL) components should be packaged into the tarball.
> 
> However, I find Bruce's unofficial wiki idea a good one for comparisons.

My suggestion is that the docs should mention only the pure existence of
important third-party packages and projects in those places where it
talks about the deficits that are supposedly fixed by those.

E. G. "There are some third-party packages and projects that aim to
provide multi-master replication, you can search for more information at
http://[unofficial wiki page url] or your favourite search engine.

This way, the docs stay neutral, but point the user to possible
solutions of his problem.

HTH,
Markus
-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org

In response to

pgsql-docs by date

Next:From: Joshua D. DrakeDate: 2006-10-25 14:20:14
Subject: Re: [HACKERS] Replication documentation addition
Previous:From: Joshua D. DrakeDate: 2006-10-25 14:13:57
Subject: Re: [HACKERS] Replication documentation addition

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2006-10-25 14:20:14
Subject: Re: [HACKERS] Replication documentation addition
Previous:From: Tom LaneDate: 2006-10-25 14:15:03
Subject: Re: [JDBC] server process (PID 1188) exited with exit code

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