Glyn Astill <glynastill at yahoo.co.uk> writes:
> I set up a replication cluster using the pgAdmin scripts, and added a
> replication set with some tables and sequences in it (table /sequence
> Ids 1 - 4). I've kept the Id numbers the same as the table Ids.
>
> Then I added another set (Id 2), and added a table and a sequence
> with Id 5.
>
> In my slony log I get the error:
>
> "remoteWorkerThread_1: node -1 not found in runtime configuration"
>
> Does anyone know what causes the error above? I've read that it
> indicates slony had a problem at a point whilst subscribing so it
> flipped the node number to -1 to stop any further steps happening,
> however this doesn't help me track down what caused it.

Hmm.  I wonder if node -1 is the virtual one that pgAdmin hacks into
place as a place to store path information for slonik-like activity...

This seems like something to ask the pgAdmin guys about...
-- 
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://www3.sympatico.ca/cbbrowne/emacs.html
"Not to oppose error, is to approve of it, and  not to defend truth is
to suppress it; not to confound evil men when we can do it, is no less
a sin than to encourage them."  -- Pope Felix III, ca. 490