Thread: Re: [HACKERS] Replication documentation addition

Re: [HACKERS] Replication documentation addition

From
Bruce Momjian
Date:
I don't think the PostgreSQL documentation should be mentioning
commercial solutions.

---------------------------------------------------------------------------

Luke Lonergan wrote:
> Bruce,
>
> > -----Original Message-----
> > From: pgsql-hackers-owner@postgresql.org
> > [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Bruce Momjian
> > Sent: Tuesday, October 24, 2006 5:16 PM
> > To: Hannu Krosing
> > Cc: PostgreSQL-documentation; PostgreSQL-development
> > Subject: Re: [HACKERS] Replication documentation addition
> >
> >
> > OK, I have updated the URL.  Please let me know how you like it.
>
> There's a typo on line 8, first paragraph:
>
> "perhaps with only one server allowing write rwork together at the same
> time."
>
> Also, consider this wording of the last description:
>
> "Single-Query Clustering..."
>
> Replaced by:
>
> "Shared Nothing Clustering
> -----------------------
>
> This allows multiple servers with separate disks to work together on a
> each query.
> In shared nothing clusters, the work of answering each query is
> distributed among
> the servers to increase the performance through parallelism.  These
> systems will
> typically feature high availability by using other forms of replication
> internally.
>
> While there are no open source options for this type of clustering,
> there are several
> commercial products available that implement this approach, making
> PostgreSQL achieve
> very high performance for multi-Terabyte business intelligence
> databases."
>
> - Luke

--
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

Re: [HACKERS] Replication documentation addition

From
"Magnus Hagander"
Date:
> I don't think the PostgreSQL documentation should be
> mentioning commercial solutions.

I think maybe the PostgreSQL documentation should be careful about
trying to list a "complete list" of commercial *or* free solutions.
Instead linking to something on the main website or on techdocs that can
more easily be updated.

//Magnus