Postgres-R is not ready for production, and development seems to have
stopped., and I don't know what multi-master solutions we can really
offer right now.  We do have several master/slave replication solutions.

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

Bopolissimus Platypus wrote:
> On Thursday 04 December 2003 00:34, Jan Wieck wrote:
> 
> > You must have misunderstood something there. The whole idea of
> > Postgres-R is how to "avoid" the need for 2-phase commit in a
> > synchronous replication system.
> 
> I've been looking at postgres-r and other postgres replication
> temporary solutions.  does anyone have a good *current* summary
> of postgres-r status?  from the website it looks like the working model 
> is based on 6.2.  is postgres-r 6.2 supposed to be good enough 
> for production?  that's what i'd assume "working model" means, 
> but confirmation from people who've actually stress tested it would 
> be great :).
> 
> the 7.2 version is the development version.  i don't see much detail 
> (documentation) though on how stable the 7.2 version is.  looking 
> at the docs in the download itself, everything seems to refer to generic 
> 7.2. i don't see anything that looks like postgres-r specific documentation.
> so i can't tell what things are implemented and what things still
> need to be implemented (but of course i might just not be looking
> hard enough for the data. to be honest, i'm just grepping for 
> "replication", opening files that look like they might be interesting 
> and scanning them, it's not like i've read everything in the doc 
> directory).  
> 
> in doc/TODO.detail/replication, there's a bunch of emails, but the
> last one seems to be from 2001.
> 
> there's src/backend/replication/README, but that seems to discuss
> only 6.2 work. i could do a diff, i suppose between the working model
> and 7.2, but i can't right now.  i'm behind a dialup modem and it would
> take too long to download 6.2 :).  maybe tomorrow at the office :).
> 
> but again, if someone has detailed and up-to-date information (summary
> or in detail) on the 7.2 postgres-r status, that would be incredibly
> cool :).
> 
> hmmm, there's a mailing list.  archives at:
> 
> http://gborg.postgresql.org/pipermail/pgreplication-general/
> 
> i didn't see any detailed summary of what's missing in 7.2 though.
> oh well, i'll just set up some test servers and just play with
> it for now, i guess.
> 
> thanks for any information.
> 
> tiger
> 
> -- 
> Gerald Timothy Quimpo  gquimpo*hotmail.com tiger*sni*ph
> http://bopolissimus.sni.ph
> Public Key: "gpg --keyserver pgp.mit.edu --recv-keys 672F4C78"
> 
>     for whom self-parody appears to be a form of self-realization
>           -- http://slate.msn.com/id/2090554/?0si=-
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to