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

From Tom Lane
Subject Re: Segmentation fault with core dump
Date
Msg-id 13612.1365636546@sss.pgh.pa.us
Whole thread Raw
In response to Re: Segmentation fault with core dump  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Segmentation fault with core dump
List pgsql-general
Andres Freund <andres@2ndquadrant.com> writes:
> On 2013-04-10 19:06:12 -0400, Tom Lane wrote:
>> And the answer is they're not testing this code path at all, because if
>> you do
>> DECLARE c CURSOR WITH HOLD FOR ...
>> FETCH ALL FROM c;
>> then the second query executes with a portal (and resource owner)
>> created to execute the FETCH command, not directly on the held portal.

> But in that path CurrentResourceOwner gets reset to portal->resowner as
> well (see PortalRunFetch())?

Right, but that's the FETCH's portal, which is a regular "live" portal
that has a ResOwner.

            regards, tom lane


pgsql-general by date:

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