#0Â 0x00000031a147c15c in memcpy () from /lib64/libc.so.6
#1Â 0x0000000000450cb8 in __memcpy_ichk (tuple=0x7fffb29ac900) at /usr/include/bits/string3.h:51
#2Â heap_copytuple (tuple=0x7fffb29ac900) at heaptuple.c:592
#3Â 0x0000000000543d4c in EvalPlanQualFetchRowMarks (epqstate=0x3cd85ab8) at execMain.c:1794
#4Â 0x00000000005440db in EvalPlanQual (estate=0x1e0db420, epqstate=0x3cd85ab8, relation=<value optimized out>, rti=4, tid=0x7fffb29aca20, priorXmax=<value optimized out>) at execMain.c:1401
#5Â 0x00000000005592eb in ExecUpdate (node=0x3cd85a28) at nodeModifyTable.c:527
#6Â ExecModifyTable (node=0x3cd85a28) at nodeModifyTable.c:748
#7Â 0x0000000000545953 in ExecProcNode (node=0x3cd85a28) at execProcnode.c:359
#8Â 0x0000000000544881 in ExecutePlan (queryDesc=0x1e727990, direction=1039265768, count=0) at execMain.c:1190
#9Â standard_ExecutorRun (queryDesc=0x1e727990, direction=1039265768, count=0) at execMain.c:280
#10 0x00002ab002c0f2b5 in explain_ExecutorRun (queryDesc=0x1e727990, direction=ForwardScanDirection, count=0) at auto_explain.c:203
#11 0x00000000005f9c81 in ProcessQuery (plan=0x2112ad60,
ÂÂÂ sourceText=0x1b3e59e0 "update v_messages set status = 'S', updated_on = now() where id in (select id from v_messages where author_id = 33138761 and status != 'S' limit 10000)",
ÂÂÂ params=<value optimized out>, dest=0x2112ae40, completionTag=0x7fffb29ace20 "") at pquery.c:197
#12 0x00000000005f9e99 in PortalRunMulti (portal=0x1b32aed0, isTopLevel=1 '\001', dest=0x2112ae40, altdest=0x2112ae40, completionTag=0x7fffb29ace20 "") at pquery.c:1268
#13 0x00000000005fa965 in PortalRun (portal=0x1b32aed0, count=9223372036854775807, isTopLevel=1 '\001', dest=0x2112ae40, altdest=0x2112ae40, completionTag=0x7fffb29ace20 "") at pquery.c:822
#14 0x00000000005f7455 in exec_simple_query (
ÂÂÂ query_string=0x1b3e59e0 "update v_messages set status = 'S', updated_on = now() where id in (select id from v_messages where author_id = 33138761 and status != 'S' limit 10000)")
ÂÂÂ at postgres.c:1058
#15 0x00000000005f7d14 in PostgresMain (argc=<value optimized out>, argv=<value optimized out>, username=<value optimized out>) at postgres.c:3929
#16 0x00000000005c7ce5 in ServerLoop () at postmaster.c:3555
#17 0x00000000005c89ec in PostmasterMain (argc=5, argv=0x1b31ea00) at postmaster.c:1092
#18 0x00000000005725fe in main (argc=5, argv=<value optimized out>) at main.c:188
On Thu, Dec 30, 2010 at 7:32 PM, Tom Lane-2 [via PostgreSQL] <[hidden email]> wrote:
Gordon Shannon <[hidden email]> writes:> I'd love to send you a stack trace. Any suggestions on how to get one? ÂIt
> has since happened again, on the same update command, so I'm guessing I can
> repeat it.            regards, tom lane
--
Sent via pgsql-general mailing list ([hidden email])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
View message @ http://postgresql.1045698.n5.nabble.com/seg-fault-crashed-the-postmaster-tp3323117p3323177.html
To unsubscribe from seg fault crashed the postmaster, click here.
--
If I had more time, I could have written you a shorter letter. (Blaise Pascal)
View this message in context: Re: seg fault crashed the postmaster
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
