| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Steve Singer <ssinger(at)ca(dot)afilias(dot)info> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Ben Carbery <ben(dot)carbery(at)gmail(dot)com>, pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: pg_listener table errors with slony |
| Date: | 2011-06-01 20:31:39 |
| Message-ID: | 1306960300.28411.49.camel@laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Uckun | 2011-06-01 22:08:09 | Re: Pgadmin III loses connection with remote database and then hangs for a long time. |
| Previous Message | Steve Singer | 2011-06-01 20:18:25 | Re: pg_listener table errors with slony |