Mon May 26 14:42:53 PDT 2008
- Previous message: [Slony1-general] "Cannot get node list"
- Next message: [Slony1-general] Removing Listen/Notify Usage for events
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I have removed code that generates + listens to LISTEN/NOTIFY events for Events + Confirms. remote_listen.c now functions solely via polling, which we already knew worked fine, as we have had a polling mode for quite a while in the 2.0 (e.g. - CVS HEAD) code tree. http://lists.slony.info/pipermail/slony1-commit/2008-May/002288.html http://lists.slony.info/pipermail/slony1-commit/2008-May/002289.html The slon _Restart LISTEN/NOTIFY handling has been left alone, as the effects are quite independent. Making sure that *that* is handled rightly will be left as a further exercise to be handled separately. Note that we *do* need to revise that, probably to remove the _Restart; in PostgreSQL 8.4, there will no longer be a pg_listener table, with the result that some of the usages surrounding the "slon restart" notification type will break. Note Andrew Dunstan's presentation at PGCon: <http://www.pgcon.org/2008/schedule/events/107.en.html> -- (reverse (concatenate 'string "gro.mca" "@" "enworbbc")) http://cbbrowne.com/info/sgml.html "... the open research model is justified. There is a passage in the Bible (John 8:32, and on a plaque in CIA HQ), "And ye shall know the truth, and the truth shall set ye free." -- Dave Dittrich
- Previous message: [Slony1-general] "Cannot get node list"
- Next message: [Slony1-general] Removing Listen/Notify Usage for events
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list