Re: Segmentation fault with core dump - Mailing list pgsql-general

From Andres Freund
Subject Re: Segmentation fault with core dump
Date
Msg-id 20130410231358.GC7547@awork2.anarazel.de
Whole thread Raw
In response to Re: Segmentation fault with core dump  (Joshua Berry <yoberi@gmail.com>)
Responses Re: Segmentation fault with core dump
Re: Segmentation fault with core dump
List pgsql-general
On 2013-04-10 17:31:09 -0500, Joshua Berry wrote:
> > Ok, so while we have a valid resource owner up to here, portal->resonwer
> > is NULL.
> >
> > Could you 'up' until youre in this frame and then do 'print *portal'?
> >
>
> #7  0x0000000000638c78 in PortalRun (portal=0x2aa9360, count=10,
>     isTopLevel=1 '\001', dest=0x2a50c40, altdest=0x2a50c40,
>     completionTag=0x7fffd193d0f0 "") at pquery.c:787
> 787                                     nprocessed =
> PortalRunSelect(portal, true, count, dest);
> (gdb) print *portal
> $1 = {name = 0x2a3fe78 "SQL_CUR017CB040", prepStmtName = 0x0,
>   heap = 0x2aca6f0, resowner = 0x0, cleanup = 0x535d30 <PortalCleanup>,
>   createSubid = 0,
>   sourceText = 0x2d141b8 "declare \"SQL_CUR017CB040\" cursor with hold for
> SELECT
>
anl.LAB,anl.JOB,anl.COMPANYCODE,anl.SAMPLETYPE,anl.COMPANYLAB,anl.CYLNO,anl.CONTAINERCODE,anl.DATEGCANALYSIS,anl.DATEREPORT,anl.SAMPLENAME,anl.FIE"...,
>   commandTag = 0x828f32 "SELECT", stmts = 0x2d145e8, cplan = 0x0,
>   portalParams = 0x0, strategy = PORTAL_ONE_SELECT, cursorOptions = 52,
>   status = PORTAL_ACTIVE, portalPinned = 0 '\000', queryDesc = 0x0,
>   tupDesc = 0x2e7fc50, formats = 0x0, holdStore = 0x2d0d430,
>   holdContext = 0x2f4e290, atStart = 0 '\000', atEnd = 0 '\000',
>   posOverflow = 0 '\000', portalPos = 10, creation_time = 418933112934458,
>   visible = 1 '\001'}
> (gdb)

Ok, I might be seeing whats going on here. Could you go to 'printtup'
and print *myState, *myState->attrinfo, *typpeinfo?

Tom: It looks to me like printtup_prepare_info won't normally be called
in an held cursor. But if some concurrent DDL changed the number of
columns in typeinfo vs thaose in the the receiver that could explain the
issue and why its not seen all the time, right?

Greetings,

Andres Freund

--
 Andres Freund                       http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Segmentation fault with core dump
Next
From: Andres Freund
Date:
Subject: Re: Segmentation fault with core dump