Re: pg_listener table errors with slony

From: Steve Singer <ssinger(at)ca(dot)afilias(dot)info>
To: Guillaume Lelarge <guillaume(at)lelarge(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:18:25
Message-ID: 4DE69E91.4020209@ca.afilias.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

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.

users can use the ENABLE/DISABLE TRIGGER commands in PostgreSQL 8.3+ to
get similar behaviour (running triggers on slaves).

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Guillaume Lelarge 2011-06-01 20:31:39 Re: pg_listener table errors with slony
Previous Message Guillaume Lelarge 2011-06-01 20:01:15 Re: pg_listener table errors with slony