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 17:54:00
Message-ID: BANLkTiktoCJT513pin4yxSVsvdVEBsy5og@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Apr 7, 2011 at 10:45 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Chris Curvey <chris(at)chriscurvey(dot)com> writes:
> > And voila! Here is the backtrace:
>
> > #0 0x00000000006ce317 in GetMemoryChunkSpace (pointer=0x347cc70) at
> > mcxt.c:264
> > #1 0x00000000006d3d56 in writetup_index (state=0x26fc530, tapenum=<value
> > optimized out>, stup=<value optimized out>) at tuplesort.c:2924
> > #2 0x00000000006d2af7 in dumptuples (state=0x26fc530, alltuples=0
> '\000')
> > at tuplesort.c:2068
> > #3 0x00000000006d392f in puttuple_common (state=0x26fc530,
> > tuple=0x7fff1e21d3b0) at tuplesort.c:1097
> > #4 0x00000000006d3c4c in tuplesort_putindextuple (state=0x26fc530,
> > tuple=<value optimized out>) at tuplesort.c:943
> > #5 0x0000000000472cac in btbuildCallback (index=<value optimized out>,
> > htup=0x26f4460, values=<value optimized out>, isnull=<value optimized
> out>,
> > tupleIsAlive=1 '\001', state=0x7fff1e21d870) at nbtree.c:194
>
> That is damn peculiar.

You clearly haven't met me yet :)

> The tuple handed to writetup_index would have
> been copied just moments before in tuplesort_putindextuple, so there is
> no way that GetMemoryChunkSpace ought to fail. If you do the run
> several times over, do you get the exact same stack trace every time?
>
> regards, tom lane
>

I don't get the same trace every time. I ran this again to see if I could
duplicate it, and everything worked. Then I ran it again, and got this
trace. (Segfault in same location, but a different path to it.)

0 0x00000000006ce31b in GetMemoryChunkSpace (pointer=0x246eae0) at
mcxt.c:264
#1 0x00000000006d3d56 in writetup_index (state=0x22cd460, tapenum=<value
optimized out>, stup=<value optimized out>) at tuplesort.c:2924
#2 0x00000000006d2af7 in dumptuples (state=0x22cd460, alltuples=1 '\001')
at tuplesort.c:2068
#3 0x00000000006d304f in tuplesort_performsort (state=0x22cd460) at
tuplesort.c:1164
#4 0x0000000000476023 in _bt_leafbuild (btspool=<value optimized out>,
btspool2=0x246eae0) at nbtsort.c:206
#5 0x0000000000472b5a in btbuild (fcinfo=<value optimized out>) at
nbtree.c:139
#6 0x00000000006b8ba1 in OidFunctionCall3 (functionId=<value optimized
out>, arg1=140165585988880, arg2=140156762410992, arg3=36255616) at
fmgr.c:1610
#7 0x00000000004ab804 in index_build (heapRelation=0x7f7ad7f66d10,
indexRelation=0x7f78ca094ff0, indexInfo=0x2293780, isprimary=1 '\001') at
index.c:1427
#8 0x00000000004ad43e in index_create (heapRelationId=<value optimized
out>, indexRelationName=<value optimized out>, indexRelationId=<value
optimized out>, indexInfo=0x2293780, indexColNames=<value optimized out>,
accessMethodObjectId=<value optimized out>, tableSpaceId=0,
classObjectId=0x22939d0, coloptions=0x22939e8, reloptions=0, isprimary=1
'\001', isconstraint=1 '\001', deferrable=0 '\000', initdeferred=0 '\000',
allow_system_table_mods=<value optimized out>, skip_build=0 '\000',
concurrent=0 '\000') at index.c:959
#9 0x0000000000514ec2 in DefineIndex (heapRelation=<value optimized out>,
indexRelationName=<value optimized out>, indexRelationId=<value optimized
out>, accessMethodName=<value optimized out>, tableSpaceName=<value
optimized out>, attributeList=0x0, predicate=0x0, options=0x0,
exclusionOpNames=0x0, unique=1 '\001', primary=1 '\001', isconstraint=1
'\001', deferrable=<value optimized out>, initdeferred=<value optimized
out>, is_alter_table=1 '\001', check_rights=1 '\001', skip_build=0 '\000',
quiet=0 '\000', concurrent=<value optimized out>) at indexcmds.c:484
#10 0x0000000000522b7b in ATExecAddIndex (tab=<value optimized out>,
rel=<value optimized out>, stmt=<value optimized out>, is_rebuild=0 '\000')
at tablecmds.c:4576
#11 0x000000000052b422 in ATExecCmd (wqueue=<value optimized out>) at
tablecmds.c:2744
#12 ATRewriteCatalogs (wqueue=<value optimized out>) at tablecmds.c:2670
#13 0x000000000052c0d7 in ATController (rel=0x7f7ad7f66d10, cmds=<value
optimized out>, recurse=<value optimized out>) at tablecmds.c:2421
#14 0x0000000000604415 in standard_ProcessUtility (parsetree=<value
optimized out>, queryString=0x2246b80 "ALTER TABLE ONLY erelated_base\n
ADD CONSTRAINT erelated_base_pkey PRIMARY KEY (id);", params=0x0,
isTopLevel=1 '\001', dest=0x2247b40, completionTag=0x7fffc180d440 "") at
utility.c:717
#15 0x00000000006000a7 in PortalRunUtility (portal=0x21bdf90,
utilityStmt=0x2247800, isTopLevel=0 '\000', dest=0x2247b40,
completionTag=0x7fffc180d440 "") at pquery.c:1191
#16 0x00000000006010ec in PortalRunMulti (portal=0x21bdf90, isTopLevel=1
'\001', dest=0x2247b40, altdest=0x2247b40, completionTag=0x7fffc180d440 "")
at pquery.c:1296
#17 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
#18 0x00000000005fde0b in exec_simple_query (query_string=<value optimized
out>) at postgres.c:1058
#19 0x00000000005fee47 in PostgresMain (argc=<value optimized out>,
argv=<value optimized out>, username=<value optimized out>) at
postgres.c:3931
#20 0x00000000005cc3b9 in BackendRun () at postmaster.c:3555
#21 BackendStartup () at postmaster.c:3242
#22 ServerLoop () at postmaster.c:1431
#23 0x00000000005cea1c in PostmasterMain (argc=35397488, argv=0x219d8f0) at
postmaster.c:1092
#24 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 Steve Crawford 2011-04-07 18:01:04 Understanding "unknown" data type
Previous Message Scott Marlowe 2011-04-07 17:45:39 Re: Protecting stored procedures