Hello, It appears that native streaming and logical replication in postgres disallows the use of NOTIFY on the master (fired by a trigger) propagating to a LISTENer on a slave. (In the former case it is not implemented, and in the latter it is buggy with no signs of a fix.)
How does slony-i fare in this department? I would hope that the same trigger would exist on the slave and that an update to a slave table would trigger it, causing the slave LISTENer to receive it. Not sure why this is such a problem with native logical replication? Also, how do I search the list archives? Thanks, John
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
