On 7/25/2005 11:21 AM, Christopher Kings-Lynne wrote:

> There is no multi master solution for PostgreSQL - at all AFAIK.  What 
> you want is impossible unless you wait no small amount of time for Slony II.

I am not even sure that Slony-II will be a solution for Andy. It is 
planned as a synchronous multimaster system and that will naturally suck 
big times in a WAN setup with network roundtrip times hundreds of times 
what you can expect in a gigabit or better LAN.

What would be required here is some asynchronous multimaster with 
conflict resolution. I am not aware of any existing solution like that.


Jan

> 
> Chris
> 
> 
> Andy wrote:
>> Well, everybody's in vacation (I hope so) or there is no solution for me???
>> 
>> Best regards,
>> Andy.
>> 
>> 
>> ----- Original Message ----- From: "Andy" <frum at ar-sd.net>
>> To: "Scott Marlowe" <smarlowe at g2switchworks.com>
>> Cc: <slony1-general at gborg.postgresql.org>
>> Sent: Friday, July 22, 2005 9:46 AM
>> Subject: Re: [Slony1-general] Slony >> Multi Master Replication???
>> 
>> 
>>>> Well, there's always some kludgy answer to such problems.  But, are you
>>>> sure you really need true multi-master replication?  Mayhaps you could
>>>> describe what it is you are trying to do first, then allow the group to
>>>> help you come up with an answer.
>>>
>>> Ok. Here is my story:
>>>
>>> We develop a contract management software, we use a Postgre database, 
>>> which has around 100 tables. Our compnay wants so open 2 more 
>>> offices(in September) in Europe where the employees will have to work 
>>> with this management software. And we are looking for a solution that 
>>> we can install this software on local servers in this offices.
>>>
>>> In this offices will be performed some major tasks like: add a 
>>> contract, planifications, report writings etc. We already use Slony 
>>> for a datatransfer to a client, but he can only read the data's and it 
>>> is ok so. But in this offices will be a lot of writing in the 
>>> database. That is why I wanted a multi master replications. Most of 
>>> the tables are "static" tables. I mean that they contain lists... that 
>>> somehow are "fix"... can be user as "read_only" in these offices. But 
>>> a task like: add a contract writes data in at least 8 tables, planning 
>>> in 3, report writing in 6 or 7 didn't count them exactly.
>>>
>>> So, my problem is this: how to replicate the database and also keep 
>>> these tables "writable"??? The solution that I see is to duplicate 
>>> these tables and replicate them reversily(from slave to master) and to 
>>> read the data with scripts... but somehow I don't like it very much. 
>>> The other problem with this solution is that we'll have 2 offices 
>>> now... what about the future...
>>>
>>> I will appriciate any ideeas, solutions etc.
>>>
>>> Best regards,
>>> Andy.
>>>
>>>
>>> ----- Original Message ----- From: "Scott Marlowe" 
>>> <smarlowe at g2switchworks.com>
>>> To: "Andy" <frum at ar-sd.net>
>>> Cc: <slony1-general at gborg.postgresql.org>
>>> Sent: Thursday, July 21, 2005 7:04 PM
>>> Subject: Re: [Slony1-general] Slony >> Multi Master Replication???
>>>
>>>
>>>> On Thu, 2005-07-21 at 05:05, Andy wrote:
>>>>
>>>>> I know that with Slony I is not possible to make a multi master
>>>>> replication.
>>>>>
>>>>> Probably some of you have more experience with Postgre Replication and
>>>>> I really need to make a multi master replication. I heard that slony
>>>>> II will be able to do this... but I don't know iof there is any
>>>>> release date or somthing more specific about it.
>>>>>
>>>>> Or... other replication solution?
>>>>>
>>>>
>>>> Well, there's always some kludgy answer to such problems.  But, are you
>>>> sure you really need true multi-master replication?  Mayhaps you could
>>>> describe what it is you are trying to do first, then allow the group to
>>>> help you come up with an answer.  There may be an inobvious fix no one
>>>> will think of until they know what objectives you're trying to reach.
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Slony1-general mailing list
>>> Slony1-general at gborg.postgresql.org
>>> http://gborg.postgresql.org/mailman/listinfo/slony1-general
>>>
>>>
>> 
>> _______________________________________________
>> Slony1-general mailing list
>> Slony1-general at gborg.postgresql.org
>> http://gborg.postgresql.org/mailman/listinfo/slony1-general
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #