From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, 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: | 2016-01-28 03:40:13 |
Message-ID: | 20160128034013.GA3888107@tornado.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jan 03, 2016 at 12:35:56AM -0500, Noah Misch wrote:
> On Sat, Jan 02, 2016 at 07:22:13PM -0500, Tom Lane wrote:
> > Noah Misch <noah(at)leadboat(dot)com> writes:
> > > I am inclined to add an Assert(portal->status != PORTAL_ACTIVE) to emphasize
> > > that this is backup only. MarkPortalActive() callers remain responsible for
> > > updating the status to something else before relinquishing control.
> >
> > No, I do not think that would be an improvement. There is no contract
> > saying that this must be done earlier, IMO.
>
> Indeed, nobody wrote a contract. The assertion would record what has been the
> sole standing practice for eleven years (since commit a393fbf9). It would
> prompt discussion if a proposed patch would depart from that practice, and
> that is a good thing. Also, every addition of dead code should label that
> code to aid future readers.
Here's the patch I have in mind. AtAbort_Portals() has an older
MarkPortalFailed() call, and the story is somewhat different there per its new
comment. That call is plausible to reach with no bug involved, but
MarkPortalFailed() would then be the wrong thing.
nm
Attachment | Content-Type | Size |
---|---|---|
AtSubAbort_Portals-ACTIVE-v1.patch | text/plain | 3.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2016-01-28 03:46:16 | Re: RFC: replace pg_stat_activity.waiting with something more descriptive |
Previous Message | Igal @ Lucee.org | 2016-01-28 03:26:16 | Re: Implementing a new Scripting Language |