There is no solid test scenario, as it doesn't happen every time,
and I couldn't reproduce it by manually running the queries.
Not the entire thing was compiled with debugging symbols, here is
what I get for stack trace:
#0 0x00000000005492a9 in spi_printtup ()
#1 0x000000000054a0bc in SPI_execute_plan ()
#2 0x00000008692d6655 in plpgsql_compile ()
from /usr/local/lib/postgresql/plpgsql.so
#3 0x00000008692d8953 in plpgsql_exec_trigger ()
from /usr/local/lib/postgresql/plpgsql.so
#4 0x00000008692d7493 in plpgsql_compile ()
from /usr/local/lib/postgresql/plpgsql.so
#5 0x00000008692d86ce in plpgsql_exec_trigger ()
from /usr/local/lib/postgresql/plpgsql.so
#6 0x00000008692d7083 in plpgsql_compile ()
from /usr/local/lib/postgresql/plpgsql.so
#7 0x00000008692dad0d in plpgsql_exec_function ()
from /usr/local/lib/postgresql/plpgsql.so
#8 0x00000008692cf00e in plpgsql_call_handler ()
from /usr/local/lib/postgresql/plpgsql.so
#9 0x000000000052f2b7 in ExecMakeFunctionResult ()
#10 0x0000000000533e90 in ExecProject ()
#11 0x0000000000542f61 in ExecResult ()
#12 0x000000000052d657 in ExecProcNode ()
#13 0x000000000052b6a1 in ExecutorRun ()
#14 0x00000000005e01e4 in PortalSetResultFormat ()
#15 0x00000000005e09bf in PortalRun ()
#16 0x00000000005dc47b in pg_parse_query ()
#17 0x00000000005de243 in PostgresMain ()
#18 0x00000000005a2239 in ClosePostmasterPorts ()
#19 0x00000000005a400c in PostmasterMain ()
#20 0x00000000005553f6 in main ()
the system is FreeBSD 6.2 AMD64 running on Xeon 64 bit.
On Thu, 2007-12-13 at 20:08 -0500, Tom Lane wrote:
> Alex Vinogradovs <AVinogradovs@Clearpathnet.com> writes:
> > I've got a strange situation where instance may crash sometimes on
> > pgplsql function call that performs several inserts into tables with
> > triggers attached. Are there any known bugs regarding plpgsql and
> > triggers in 8.2.5 ? Thanks!
>
> Nope; can you provide a reproducible test case? Or at least a stack
> trace?
>
> regards, tom lane
