Re: pg_listener table errors with slony

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: 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-01-19 21:30:49
Message-ID: 4D375809.40305@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Le 19/01/2011 22:23, Dave Page a écrit :
> On Wed, Jan 19, 2011 at 8:20 PM, Guillaume Lelarge
> <guillaume(at)lelarge(dot)info> wrote:
>> Le 14/01/2011 00:27, Guillaume Lelarge a écrit :
>>> Le 14/01/2011 00:09, Ben Carbery a écrit :
>>>> [...]
>>>> I am using slony 2.06 on a pg 9.0.2 installation with pgadmin 12.2.2.
>>>> Whenever I click on certain elements of the object browser associated with
>>>> replication I get an error:
>>>>
>>>> ERROR: relation pg_listener does not exist
>>>> LINE 1: SELECT listenerpid FROM pg_listener WHERE relname = '...
>>>>
>>>> This occur under Replication-><cluster name> for example or when clicking on
>>>> nodes under that. This also occurs on 12.2.1.
>>>>
>>>> I believe this table no longer exists in 9.0 so I guess this is technically
>>>> a bug. Should it be logged as such?
>>>>
>>>
>>> Well, pgAdmin fires this query. As you say, this table no longer exists
>>> since the rework on the listen/notify mechanism done for 9.0. So, yeah,
>>> this is a bug in pgAdmin.
>>>
>>> I'll try to work on this tomorrow.
>>>
>>
>> Got a look at this, and I reproduce the error. I don't think we have any
>> support of Slony 2.0.
>
> We did.
>

We had 1.2 support. To have 2.0, we would have to get rid of the
sl_trigger checks. Or was it dropped along the way of 2.0?

--
Guillaume
http://www.postgresql.fr
http://dalibo.com

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2011-01-19 21:33:46 Re: pg_listener table errors with slony
Previous Message Dave Page 2011-01-19 21:23:02 Re: pg_listener table errors with slony