Jan Wieck wrote:
>
> 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_" ...
>
>
Sorry to be so clueless, working with gdb is complete black magic to me,
so I'm utterly at the mercy of others:
(gdb) frame 2
#2 0x00002aaaca4ba348 in _Slony_I_logTrigger (fcinfo=0x9362bd) at
slony1_funcs.c:783
783 col_value =
slon_quote_literal(SPI_getvalue(old_row, tupdesc, i + 1));
(gdb) print *((TriggerData)*fcinfo->context)->tg_relation->rd_rel
Cannot access memory at address 0x61746f54222c226d
It doesn't look too hopeful - is this because the data would have been
in the shared memory used by all postgres instances, and therefore not
contained in the 6MB coredump?
Cheers,
Gavin.
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
