Thu Jul 19 21:39:37 PDT 2007
- Previous message: [Slony1-general] Slave in an insecure location
- Next message: [Slony1-general] Slave in an insecure location
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 7/19/07, Jan Wieck <JanWieck at yahoo.com> wrote: > > On 7/19/2007 12:58 AM, Mikko Partio wrote: > > No, only the slon of a real replica can actually write the log files. > However, what might work in your case is to create a "fake" replica. > Create a replica that has a slave-only trigger (using STORE TRIGGER) on > every replicated table. The trigger fires BEFORE INSERT and all it does > is RETURN NULL. And you subscribe the thing with no forwarding. That > should create an empty replica that now can write the log shipping > files. To get the initial content for the offline replica you must > however stop the application and dump from the origin. This method seems to fit my purposes nicely. My own thinking was that I'd periodically truncate the tables at the subscriber but this solution is much more elegant. Not even that. Each slon only needs superuser access to its local node. > Never does it need privileged access to the remote side. And all remote > access is read only. > Hmm this is interesting, perhaps it should be mentioned at the docs. By the way, the documention link on the web pages leads to an older version of the docs, since it doesn't have the "lowering authority" -section. Thanks a lot for the both of you for your help. Regards MP -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070720/= f7f1f16d/attachment.htm
- Previous message: [Slony1-general] Slave in an insecure location
- Next message: [Slony1-general] Slave in an insecure location
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list