Re: Postgresql replication

From: "Welty, Richard" <richard(dot)welty(at)bankofamerica(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgresql replication
Date: 2005-08-24 13:57:07
Message-ID: 7A8D99D6C4AE9347886B31F047F26BD6045C52@ex2k.bankofamerica.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

[mailto:pgsql-general-owner(at)postgresql(dot)org]On Behalf Of Michael Meskes

>Am Mittwoch, 24. August 2005 14:21 schrieb Carlos Henrique Reimer:
>> One possible solution is replicate the headquarter DB into the two
>> branches.

>> I read about slony-i, but then the replicated DBs will be read-only.

>That's because it's a master-slave replication. If you could sync the slave
>back to the master it would be a master itself.

>> I think I´m looking for a master-slave assynchronous solution. I know
>> pgReplicator can do it, but I think the project is not active any more.

>But Slony does master/slave replication.

i think carlos is confused about master-slave vs multi-master.

carlos,
master-slave async is much easier than multi-master async. yes, pgreplicator
can in theory do multi-master async in a restricted sort of way (the
generalized multi-master async problem is fairly intractable), but you're
right in that pgreplicator is not maintained anymore (and moreover it depends
on a no-longer-maintained dialect of tcl.) if i had infinite time and energy,
i'd be working on a reimplementation of pgreplicator in C, but i don't have
either and i don't see anyone offering to pay me to do it, so it'll stay on
the list of wanna-do projects for the time being.

richard

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-08-24 15:00:49 Re: psql: server closed the connection unexpetedly
Previous Message Michael Meskes 2005-08-24 13:31:34 Re: Postgresql replication