Should the text include a mention of synchronous vs. asynchronous? Or
does master-master imply synchronous?
Regards,
Jeff Davis
On Sun, 2005-04-24 at 08:01 -0400, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Tue, 16 Nov 2004, Robert Treat wrote:
> >
> > > On Sunday 14 November 2004 16:33, Bruce Momjian wrote:
> > >> Log Message:
> > >> -----------
> > >> Remove replicaiton FAQ item.
> > >>
> > >> Modified Files:
> > >> --------------
> > >> pgsql/doc:
> > >> FAQ (r1.269 -> r1.270)
> > >>
> > >> (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.269&r2=
> > >> 1.270) pgsql/doc/src/FAQ:
> > >> FAQ.html (r1.227 -> r1.228)
> > >>
> > >> (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ.html.diff
> > >> ?r1=1.227&r2=1.228)
> > >
> > > While the answer may have been a little dated, this still seems to be an FAQ.
> > > Was there a discussion on removing this? If so I'll go read that, but ISTM
> > > this question should remain.
> >
> > agreed, this definitly does fall under a "Very FAQ" kinda thing ...
> > pointers to the various methods that are currently in use, at a minimum,
> > would be good ...
>
> Yep, big mistake my removing the replication FAQ item. I have re-added a
> new one:
>
> 4.21) What replication solutions are available?
>
> Though "replication" is a single term, there are two major replication
> technologies. Multi-master replication allows read/write queries to be
> sent to multiple replicated computers. Using this capability has a
> serious performance impact. Pgcluster is the most popular such solution
> available for PostgreSQL. Master-slave replication allows a single
> master to receive read/write queries, with slaves able to accept only
> read/SELECT queries. The most popular master-slave PostgreSQL
> replication solution is Slony. There are also commercial and
> hardware-based replication solutions available.
>
