Le vendredi 9 mars 2007 15:25, Marco Gaiarin a écrit :
> Mandi! Raymond O'Donnell
> In chel di` si favelave...
>
> > I'm also a novice on Slony, but I'd imagine that if you're trying to
> > write to a slave node, then there's something wrong with your
> > architecture and you're better off knowing about it than having it
> > silently try to "fix" things for you.... :)
>
> I'm not speaking about writing on the slave, but as there's on the
> master a trigger that intercepts I/U/D query and logs for further
> processing, could be possible a trigger on slaves that simply
> 'redirect' write on master?
I think, that the answer is true : why your application will attempt to write
on a 'slave' node ?
> [there's also on postgres a 'trigger package' that permit to create
> some sort of 'link table'... ouch, i've forgot the name...]
>
>
> Probably there's tons of locking/timings/... issue, but clearly i've
> not meant to write on slave(s), i'm not mad. ;)
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
