pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Synchronized Replication
2+ messages / 2 participants
[nested] [flat]

* Synchronized Replication
@ 2006-05-09 00:37 Ketema Harris <ketema@gmail.com>
  2006-05-15 19:35 ` Re: Synchronized Replication Jim C. Nasby <jnasby@pervasive.com>
  0 siblings, 1 reply; 2+ messages in thread

From: Ketema Harris @ 2006-05-09 00:37 UTC (permalink / raw)
  To: pgsql-admin

Hello.  I have been reading up on Sony Replication, and at first I thought
Master/Slave between two offices would be perfect for my situation.  After I
got more info though I believe it may not suit my needs.  If I want the two
databases to be in synchronization (meaning they have the same tables, and
if an insert occurs on one it is replicated in such a way that unique ids
from sequences are not duplicated) is this something that Slony can
accomplish?  If not what other options are out there?

Thanks.

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Synchronized Replication
  2006-05-09 00:37 Synchronized Replication Ketema Harris <ketema@gmail.com>
@ 2006-05-15 19:35 ` Jim C. Nasby <jnasby@pervasive.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Jim C. Nasby @ 2006-05-15 19:35 UTC (permalink / raw)
  To: Ketema Harris <ketema@gmail.com>; +Cc: pgsql-admin

On Mon, May 08, 2006 at 08:37:32PM -0400, Ketema Harris wrote:
> Hello.  I have been reading up on Sony Replication, and at first I thought
> Master/Slave between two offices would be perfect for my situation.  After I
> got more info though I believe it may not suit my needs.  If I want the two
> databases to be in synchronization (meaning they have the same tables, and
> if an insert occurs on one it is replicated in such a way that unique ids
> from sequences are not duplicated) is this something that Slony can
> accomplish?  If not what other options are out there?

For slony, depening on how your application is setup, you might be able
to have each site write to a set of local tables that are then
replicated back to a single office. The database at that office would
then need to merge all of that together and publish it back out via a
different table.

Your only other option is one of the command-based syncronous
replication schemes, but you have to be very careful about what commands
you issue with those. They also tend not to handle communication
interruptions very well, making them ill-suited for replicating over a
WAN.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2006-05-15 19:35 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-05-09 00:37 Synchronized Replication Ketema Harris <ketema@gmail.com>
2006-05-15 19:35 ` Jim C. Nasby <jnasby@pervasive.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox