Re: postgres segfaulting on pg_restore

From: Chris Curvey <chris(at)chriscurvey(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org, martin(dot)pitt(at)ubuntu(dot)com
Subject: Re: postgres segfaulting on pg_restore
Date: 2011-04-07 18:19:02
Message-ID: BANLkTinzG_0_TugdRrDqQ7CuZM1FogTWVA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
>
>>
and, FWIW, here's another trace, which is NEARLY the same as the first one I
posted, with the difference being a slightly different line number at #3. I
will be quiet now and leave the brain trust to ponder. Let me know if there
is anything else I can get for you guys.

#0 0x00000000006ce317 in GetMemoryChunkSpace (pointer=0x292a0e0) at
mcxt.c:264
#1 0x00000000006d3d56 in writetup_index (state=0x2281670, tapenum=<value
optimized out>, stup=<value optimized out>) at tuplesort.c:2924
#2 0x00000000006d2af7 in dumptuples (state=0x2281670, alltuples=0 '\000')
at tuplesort.c:2068
#3 0x00000000006d38b7 in puttuple_common (state=0x2281670, tuple=<value
optimized out>) at tuplesort.c:1046
#4 0x00000000006d3c4c in tuplesort_putindextuple (state=0x2281670,
tuple=<value optimized out>) at tuplesort.c:943
#5 0x0000000000472cac in btbuildCallback (index=<value optimized out>,
htup=0x22eade0, values=<value optimized out>, isnull=<value optimized out>,
tupleIsAlive=1 '\001', state=0x7fffc180c8f0) at nbtree.c:194
#6 0x00000000004ab1ec in IndexBuildHeapScan (heapRelation=<value optimized
out>, indexRelation=<value optimized out>, indexInfo=<value optimized out>,
allow_sync=<value optimized out>, callback=<value optimized out>,
callback_state=<value optimized out>) at index.c:1866
#7 0x0000000000472b35 in btbuild (fcinfo=<value optimized out>) at
nbtree.c:123
#8 0x00000000006b8ba1 in OidFunctionCall3 (functionId=<value optimized
out>, arg1=140165586614672, arg2=140165586792240, arg3=36148832) at
fmgr.c:1610
#9 0x00000000004ab804 in index_build (heapRelation=0x7f7ad7fff990,
indexRelation=0x7f7ad802af30, indexInfo=0x2279660, isprimary=0 '\000') at
index.c:1427
#10 0x00000000004ad43e in index_create (heapRelationId=<value optimized
out>, indexRelationName=<value optimized out>, indexRelationId=<value
optimized out>, indexInfo=0x2279660, indexColNames=<value optimized out>,
accessMethodObjectId=<value optimized out>, tableSpaceId=0,
classObjectId=0x228ee20, coloptions=0x228ee40, reloptions=0, isprimary=0
'\000', isconstraint=0 '\000', deferrable=0 '\000', initdeferred=0 '\000',
allow_system_table_mods=<value optimized out>, skip_build=0 '\000',
concurrent=0 '\000') at index.c:959
#11 0x0000000000514ec2 in DefineIndex (heapRelation=<value optimized out>,
indexRelationName=<value optimized out>, indexRelationId=<value optimized
out>, accessMethodName=<value optimized out>, tableSpaceName=<value
optimized out>, attributeList=0x2, predicate=0x0, options=0x0,
exclusionOpNames=0x0, unique=0 '\000', primary=0 '\000', isconstraint=0
'\000', deferrable=<value optimized out>, initdeferred=<value optimized
out>, is_alter_table=0 '\000', check_rights=1 '\001', skip_build=0 '\000',
quiet=0 '\000', concurrent=<value optimized out>) at indexcmds.c:484
#12 0x0000000000603b69 in standard_ProcessUtility (parsetree=0x21a4218,
queryString=0x21a3570 "CREATE INDEX ieqansb ON eqanswer_base USING btree
(entityrole, fieldnum, memotext);", params=0x0, isTopLevel=1 '\001',
dest=0x21a45b8, completionTag=0x7fffc180d440 "") at utility.c:876
#13 0x00000000006000a7 in PortalRunUtility (portal=0x225ea10,
utilityStmt=0x21a4218, isTopLevel=0 '\000', dest=0x21a45b8,
completionTag=0x7fffc180d440 "") at pquery.c:1191
#14 0x00000000006010ec in PortalRunMulti (portal=0x225ea10, isTopLevel=1
'\001', dest=0x21a45b8, altdest=0x21a45b8, completionTag=0x7fffc180d440 "")
at pquery.c:1296
#15 0x0000000000601852 in PortalRun (portal=<value optimized out>,
count=<value optimized out>, isTopLevel=-32 '\340', dest=<value optimized
out>, altdest=<value optimized out>, completionTag=<value optimized out>) at
pquery.c:822
#16 0x00000000005fde0b in exec_simple_query (query_string=<value optimized
out>) at postgres.c:1058
#17 0x00000000005fee47 in PostgresMain (argc=<value optimized out>,
argv=<value optimized out>, username=<value optimized out>) at
postgres.c:3931
#18 0x00000000005cc3b9 in BackendRun () at postmaster.c:3555
#19 BackendStartup () at postmaster.c:3242
#20 ServerLoop () at postmaster.c:1431
#21 0x00000000005cea1c in PostmasterMain (argc=35397488, argv=0x219d8f0) at
postmaster.c:1092
#22 0x0000000000575be0 in main (argc=3, argv=0x219d8e0) at main.c:188

--
Ignoring that little voice in my head since 1966!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2011-04-07 18:29:30 Re: Understanding "unknown" data type
Previous Message Steve Crawford 2011-04-07 18:01:04 Understanding "unknown" data type