--- On Wed, 2/24/10, Dave Stevenson <dave.stevenson at pacbell.net> wrote:

From: Dave Stevenson <dave.stevenson at pacbell.net>
Subject: [Slony1-general]  Is Slony for me?
To: Slony1-general at lists.slony.info
Date: Wednesday, February 24, 2010, 11:28 AM


I'm looking for a replication solution, but I'm no DBA. My use
case is probably similar to the following, listed in Slony's online doc
as a poor match for Slony:
    Replicating a pricing database from a central server to sales staff who connect periodically to grab updates. 
 
I'm wondering what is it about Slony that makes that scenario a bad match, or what alternative might work better for me.
 
I use Postgresql as a source code repository. However, the server
is remote, and access is typically very slow. I'd like to have a
read-only local copy for comparing, reconciling, loading, etc., and
access the remote server only for writes (publish). Typical usage is
lots of reads, few writes, very rare and limited updates, even more
rare and limited deletes (few times per year?), and maybe once every
2-4 years a schema change. 
 
If I have a local clone on my laptop, it will often be offline (at
night). Is Slony a bad match because the slave would miss updates while
offline?
 
Anyone know of a better fit for my use case?
 
Thanks,
 Dave Stevenson
dave.stevenson at pacbell.net 

-----Inline Attachment Follows-----

_______________________________________________
Slony1-general mailing list
Slony1-general at lists.slony.info
http://lists.slony.info/mailman/listinfo/slony1-general

>I'd like to have a read-only local copy for comparing, reconciling, loading, 
>etc.

Good news. Slony is excellent for that situation.

>If I have a local clone on my laptop, it will often be offline (at
night). Is Slony a 
>bad match because the slave would miss updates while
offline?


Bad news.  Unless there is only a small amount of updates (DML) that will be occurring while your laptop is offline, it will take a long time for slony to synchronize and catch up with transactions that occurred. If your database is small enough, you might be better off just doing a pg_dump of the master, and then copy it to the laptop, drop the old database, make a new db  and then pg_restore the new copy.

Melvin Davidson 
  






      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20100224/ca5d0fed/attachment.htm