On Wed, 2011-06-01 at 16:18 -0400, Steve Singer wrote: > On 11-06-01 04:01 PM, Guillaume Lelarge wrote: > > > > > Yes, we are still trying to scan the sl_trigger table which seems to > > have been dropped in Slony 2.0. See pgadmin/slony/dlgRepSet.cpp and > > pgadmin/slony/slTable.cpp. > > > > In 2.0 slony no longer manages enabling triggers on slaves. > The slony commands store trigger, drop trigger have gone away along with > sl_trigger. >
Makes sense. I guess we only need to check Slony version, and use sl_trigger only with 1.2. It should be pretty easy on slTable at least. > users can use the ENABLE/DISABLE TRIGGER commands in PostgreSQL 8.3+ to > get similar behaviour (running triggers on slaves). > -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
