From: | TomDB <tomdb(at)uk2(dot)net> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: replication? |
Date: | 2006-11-14 21:10:53 |
Message-ID: | 1807736772.20061114221053@uk2.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)uk2(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-11-14 21:48:20 | Re: Move indexes |
Previous Message | TomDB | 2006-11-14 20:58:50 | Re: replication? |