Re: Replication status

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Replication status
Date: 2002-05-29 01:33:49
Message-ID: 200205290133.g4T1Xnj24647@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Agreed. It would be nice to see both a single-master and multi-master
server included in our main tree and a clear description of when to use
each. The confusion over the various replication solutions and their
strengths/weaknesses is a major problem.

I always felt a clearer README for rserv would help greatly. We do get
lots of questions about how to get it working. README.rserv goes over
the major 'toolset' items and describes a demo, but that is it. (I
don't even know what the 'toolset' items are or how to access them, at
least from reading the README.) I thought of doing the README
improvements myself, but because I didn't write it, I left it alone.

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

Thomas Lockhart wrote:
> ...
> > rserver only does single-master, while most people want multi-master.
>
> As you probably know, rserv is not limited to only a single instance of
> a single master. Many replication problems can be described as a "single
> source" problem (or should be described as such; moving to a fully
> distributed database brings a host of other issues). So any problem
> which can be decomposed to having single sources of subsets of
> information can be handled with this system.
>
> The contrib/rserv code has received no contributions from the community
> beyond our original submission, which of course pushes all of the
> development and recurring costs back onto PostgreSQL Inc and their
> clients. We have been very low-key (imho) in representing this solution
> to the developer community, but it should be considered for applications
> matching its capabilities. Full transactional integrity across primary
> and secondary servers is not easy to come by and not offered by most
> other solutions. fwiw we have demonstrated well over 2000 updates per
> second flowing through rserv systems.
>
> - Thomas
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-05-29 01:47:19 Re: ksqo?
Previous Message Thomas Lockhart 2002-05-29 01:08:21 Re: Replication status