Re: Fwd: Core dump with nested CREATE TEMP TABLE

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fwd: Core dump with nested CREATE TEMP TABLE
Date: 2015-09-04 01:14:32
Message-ID: CAB7nPqRyEmtjehrpZFY4ZdkT-ud0G4r1AFg+cWwsnZvfuhHHYg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 4, 2015 at 9:57 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>wrote:

> On reflection I think that the tracking of activeSubid in my patch is
> probably overkill if we're attacking it this way. We can just have
> AtSubAbort_Portals fail any ACTIVE portal regardless of subxact level,
> which is pretty analogous to what AtAbort_Portals has done for a long
> time.
>

Tracking the activated subxact looked neat from my side, that's more
consistent with what is done when the portal is marked as ready,
particularly with the new routine introduced.

> Let me work on this and see if I can get to a simpler patch.
>

Oh, OK. Thanks!
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2015-09-04 01:15:07 Re: Reduce ProcArrayLock contention
Previous Message Amit Langote 2015-09-04 01:10:51 Re: BRIN INDEX value