Sun Dec 9 13:21:57 PST 2007
- Previous message: [Slony1-general] Delayed replication: Explicitly creating a slony-I backlog, and then telling the slon daemon to replicate changes all at once.
- Next message: [Slony1-general] Delayed replication: Explicitly creating a slony-I backlog, and then telling the slon daemon to replicate changes all at once.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Dec 08, 2007 at 05:52:16PM +0000, Peter Geoghegan wrote: > Hello, > > I'm using slony to power a point-of-sale system - changes in the > back-office are replicated amongst tills (subscribers). For > business logic reasons, I'd like to be able to create a backlog of > changes, and then have the slon daemon replicate all such changes > upon being explicitly told to do so, rather then having the daemon > automatically replicate all changes to the replication set. > > Is this possible? How so? If it's possible for you to box all those changes into a single transaction, Slony will just Do The Right Thing(TM). If not, I suppose you could kill all the slons before doing the change set, then restart them afterwards, but that seems horrifically kludgey. Cheers, David. -- David Fetter <david at fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter at gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
- Previous message: [Slony1-general] Delayed replication: Explicitly creating a slony-I backlog, and then telling the slon daemon to replicate changes all at once.
- Next message: [Slony1-general] Delayed replication: Explicitly creating a slony-I backlog, and then telling the slon daemon to replicate changes all at once.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list