[Slony1-general] NOTIFY/LISTEN for cache invalidation in clients of slony-i slaves

[John Muehlhausen]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slony.info/pipermail/slony1-general/attachments/20200228/d86f489e/attachment.htm>