Geoffrey <[EMAIL PROTECTED]> writes:
> Program terminated with signal 11, Segmentation fault.
> #0 exec_stmt (estate=0xfeff8a90, stmt=0x0) at pl_exec.c:928
> in pl_exec.c
> #0 exec_stmt (estate=0xfeff8a90, stmt=0x0) at pl_exec.c:928
> #1 0x0083f005 in exec_stmts (estate=0xfeff8a90, stmts=0x90fa9e0)
> at pl_exec.c:903
> #2 0x0083f4f2 in exec_stmt_if (estate=0xfeff8a90, stmt=0x90fab78)
> at pl_exec.c:1139
It seems you've got a corrupt "compiled statements" data structure for
a plpgsql trigger function. Offhand this does not look like any of the
known post-7.4.7 bug fixes. Can you show us the source code for that
trigger?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
