I'd like to create a setup where there are exactly 2 masters which
need to be synchronized against each other. The two masters should
have read+write access, but don't have a permanent connection to each
other. One will be on a LAN-server, the other instance will be
installed on a Windows-client-laptop which can be taken along the
road. When coming back to the office, we need to sync the changed
data.

is there any tool that will allow me to do so ?





---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On Mon, Nov 13, 2006 at 10:21:40PM +0100, TomDB wrote:
>
> I'd like to create a setup where there are exactly 2 masters which
> need to be synchronized against each other. The two masters should
> have read+write access, but don't have a permanent connection to each
> other. One will be on a LAN-server, the other instance will be
> installed on a Windows-client-laptop which can be taken along the
> road. When coming back to the office, we need to sync the changed
> data.
>
> is there any tool that will allow me to do so ?

If you got *really* clever you could maybe pull it off with Slony, but
in general, no, this isn't possible.
--
Jim Nasby jim@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

hmm - I was hoping to have it in a database supported by PHP,
preferably freely available. MySQL would be OK too, but I didn't find
it there either.

Strange, cause to my knowledge 'even' MS Access offers it - I used it
before in the Access 97 version. And Access it not what I'd call a
decent database.


> [Offline multi master replication]
>> If you got *really* clever you could maybe pull it off with Slony, but
>> in general, no, this isn't possible.

> If this is an option, FrontBase offers support for that. You might
> contact them directly.

> http://www.frontbase.com




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

would there be any default available field (like the OID of the
records) that would be unique in the two versions of the datbase?
there isn't "by accident" something like a unique UID like an MD5 or
something... ?

cause if there is no replication available, I'd consider this
(together with PHP)

a) replacing the serial fields by generated UID's (md5 of ID + a
string that depends on the install)
or
b) start the autoincrement field at a high number in the second
install (since I can estimate that there will never by > 10 000
records)

+ store all queries that were performed & run them in the
network-master afterwards.




>>
>> I'd like to create a setup where there are exactly 2 masters which
>> need to be synchronized against each other. The two masters should
>> have read+write access, but don't have a permanent connection to each
>> other. One will be on a LAN-server, the other instance will be
>> installed on a Windows-client-laptop which can be taken along the
>> road. When coming back to the office, we need to sync the changed
>> data.
>>
>> is there any tool that will allow me to do so ?

> If you got *really* clever you could maybe pull it off with Slony, but
> in general, no, this isn't possible.



--
Best regards,
TomDB mailto:tomdb@uk2.net


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Why not just have a primary key with 2 columns, one of which is a serial and the other is a "siteid" or "installid" that is different for each server?

TomDB wrote:

would there be any default available field (like the OID of the records) that would be unique in the two versions of the datbase? there isn't "by accident" something like a unique UID like an MD5 or something... ? cause if there is no replication available, I'd consider this (together with PHP) a) replacing the serial fields by generated UID's (md5 of ID + a string that depends on the install) or b) start the autoincrement field at a high number in the second install (since I can estimate that there will never by > 10 000 records) + store all queries that were performed & run them in the network-master afterwards.



I'd like to create a setup where there are exactly 2 masters which need to be synchronized against each other. The two masters should have read+write access, but don't have a permanent connection to each other. One will be on a LAN-server, the other instance will be installed on a Windows-client-laptop which can be taken along the road. When coming back to the office, we need to sync the changed data. is there any tool that will allow me to do so ?







If you got *really* clever you could maybe pull it off with Slony, but in general, no, this isn't possible.