On 5/9/2006 8:32 AM, Gavin Hamill wrote:
> 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? :)
In gdb:
frame 2
print *((TriggerData)*fcinfo->context)->tg_relation->rd_rel
In that output you will find the tablename that caused this log trigger
call right in the first line {data = "_table_name_here_" ...
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== [EMAIL PROTECTED] #
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
