From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
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:23:02 |
Message-ID: | AANLkTikdRfr5exHWhwQ+6pAM_RqaQ3R1jBL9PfSqvU1B@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
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.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2011-01-19 21:30:49 | Re: pg_listener table errors with slony |
Previous Message | Guillaume Lelarge | 2011-01-19 20:20:52 | Re: pg_listener table errors with slony |