>> Then I get this message:
>> Starting SLONY slave(fquest)<stdin>:4: NOTICE:  subscribe set:
>> omit_copy=f
>> <stdin>:4: PGRES_FATAL_ERROR select "_fquest".subscribeSet(1, 1, 2, 'f',
>> 'f');  - ERROR:  Slony-I: subscribeSet() the receiver does not exist
>> receiver id:2

>You need to add something like

>store node(id=2, event node=1);

>before the subscribe set command in your
>fquest-slave-setupmaker script

thanks a lot, this solved the "receiver does not exist"-problem. both master
and slave start without any errors now.


>> Further I get this error when clicking on the cluster in pgadmin:
>> 2011-07-26 10:58:42 CEST fquest postgres ERROR:  relation "pg_listener"
>> does
>> not exist at character 25
>> 2011-07-26 10:58:42 CEST fquest postgres STATEMENT:  SELECT listenerpid
>> FROM
>> pg_listener WHERE relname = '_fquest_Event'

>This error is unrelated, but might be because the version of pgadmin you 
>have is older than the version of postgresql you are using.
>
>AI will also warn you that many (maybe even the last released one) 
>versions of pgadmin don't properly work with slony 2.0.x

read about that already. will keep it in mind. but pgadmin is for now the
best way for me to check what is going on. further comparing the old and the
new server replication wise.



What still bothers me, is that the replication set on the master-DB states
24 tables. this is ok. but the replication set on the slave does not state
any abonnements/subscriptions (to these tables). I think there should be an
abonnement/subscription. like this (on the old server - pgadmin sql field):

-- subscribe replication set

 SELECT _fquest.subscribeset(1, 1, 2, false);

thanks for your help, really appreciated.

Cheers,
Marcus
-- 
View this message in context: http://old.nabble.com/subscribeSet%28%29-the-receiver-does-not-exist-receiver-id%3A2-tp32138395p32169512.html
Sent from the Slony-I -- General mailing list archive at Nabble.com.