The following bug has been logged on the website: Bug reference: 7516 Logged by: Marko Tiikkaja Email address: pgm...@joh.to PostgreSQL version: 9.1.5 Operating system: 64-bit linux Description:
Hi, We had a segmentation fault in PostgreSQL 9.1.5 with PL/PerlU. The backtrace looks like this: #0 0x00007f80be88cb04 in plperl_spi_exec_prepared (query=0x1671eb8 "0x168cd70", attr=0x0, argc=2, argv=0x19b4e40) at /build/buildd/postgresql-9.1-9.1.5/build/../src/pl/plperl/plperl.c:3373 #1 0x00007f80be88e4f0 in XS__spi_exec_prepared (my_perl=<optimized out>, cv=<optimized out>) at /build/buildd/postgresql-9.1-9.1.5/build/../src/pl/plperl/SPI.xs:141 #2 0x00007f80be5b67ff in Perl_pp_entersub () from /usr/lib/libperl.so.5.14 #3 0x00007f80be5adc96 in Perl_runops_standard () from /usr/lib/libperl.so.5.14 #4 0x00007f80be54959e in Perl_call_sv () from /usr/lib/libperl.so.5.14 #5 0x00007f80be885c55 in plperl_call_perl_func (desc=0x189a010, fcinfo=0x188c490) at /build/buildd/postgresql-9.1-9.1.5/build/../src/pl/plperl/plperl.c:2017 #6 0x00007f80be88a17c in plperl_func_handler (fcinfo=0x188c490) at /build/buildd/postgresql-9.1-9.1.5/build/../src/pl/plperl/plperl.c:2156 #7 plperl_call_handler (fcinfo=0x188c490) at /build/buildd/postgresql-9.1-9.1.5/build/../src/pl/plperl/plperl.c:1671 #8 0x0000000000707147 in fmgr_security_definer (fcinfo=0x188c490) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/utils/fmgr/fmgr.c:975 #9 0x0000000000575e45 in ExecMakeFunctionResult (fcache=0x188c420, econtext=0x188c230, isNull=0x188cec8 "id", isDone=0x188cfe0) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/executor/execQual.c:1917 #10 0x0000000000578512 in ExecTargetList (isDone=0x7fff051891ec, itemIsDone=0x188cfe0, isnull=0x188cec8 "id", values=0x188ceb0, econtext=0x188c230, targetlist=0x188cfb0) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/executor/execQual.c:5210 #11 ExecProject (projInfo=<optimized out>, isDone=0x7fff051891ec) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/executor/execQual.c:5425 #12 0x0000000000588b4a in ExecResult (node=0x188c120) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/executor/nodeResult.c:155 #13 0x00000000005713e8 in ExecProcNode (node=0x188c120) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/executor/execProcnode.c:367 #14 0x000000000056e662 in ExecutePlan (dest=0x15ae900, direction=<optimized out>, numberTuples=0, sendTuples=1 '\001', operation=CMD_SELECT, planstate=0x188c120, estate=0x188c010) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/executor/execMain.c:1440 15 standard_ExecutorRun (queryDesc=0x1464830, direction=<optimized out>, count=0) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/executor/execMain.c:314 #16 0x0000000000642ee7 in PortalRunSelect (portal=0x1421710, forward=<optimized out>, count=0, dest=0x15ae900) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/tcop/pquery.c:943 #17 0x00000000006443d0 in PortalRun (portal=0x1421710, count=9223372036854775807, isTopLevel=1 '\001', dest=0x15ae900, altdest=0x15ae900, completionTag=0x7fff05189670 "") at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/tcop/pquery.c:787 #18 0x0000000000640fba in exec_execute_message (max_rows=<optimized out>, portal_name=0x15ae4f0 "") at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/tcop/postgres.c:1965 #19 PostgresMain (argc=<optimized out>, argv=<optimized out>, username=<optimized out>) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/tcop/postgres.c:4025 #20 0x0000000000602813 in BackendRun (port=0x145b990) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/postmaster/postmaster.c:3617 #21 BackendStartup (port=0x145b990) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/postmaster/postmaster.c:3302 #22 ServerLoop () at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/postmaster/postmaster.c:1466 #23 0x0000000000603281 in PostmasterMain (argc=<optimized out>, argv=<optimized out>) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/postmaster/postmaster.c:1127 #24 0x000000000045a440 in main (argc=5, argv=0x1416170) at /build/buildd/postgresql-9.1-9.1.5/build/../src/backend/main/main.c:199 It seems to have happened when a PL/PerlU executed a prepared statement which calls another PL/PerlU function. So far we have not been able to reproduce the problem. Any thoughts? Someone seen something similar? Regards, Marko Tiikkaja -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs