Jan Wieck wrote:

> This happens in 1.1.5 when the key used as unique row identification 
> contains NULL values. If you can find out from the fcinfo argument in 
> stack frame 2 which table it is, you can check if its data contains 
> NULL values in any of the columns used by slony as the tables primary 
> key.


Thanks :) It's reassuring to know that it's a known issue - and obv none 
of our rows should have a null key, but I'll have to ask for more 
hand-holding since I'm not very familiar with gdb ... basically what do 
I type at the prompt to find out this info? :)

Cheers,
Gavin.