Re: [BUGS] BUG #14808: V10-beta4, backend abort - Mailing list pgsql-bugs

From Robert Haas
Subject Re: [BUGS] BUG #14808: V10-beta4, backend abort
Date
Msg-id CA+TgmoZO2JJzG0QFYHzgAY6E2hQwwbicYdxWGng0aFfg3RBuRQ@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] BUG #14808: V10-beta4, backend abort  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] BUG #14808: V10-beta4, backend abort
List pgsql-bugs
On Sat, Sep 9, 2017 at 1:08 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> My first instinct is to get rid of DestroyTransitionCaptureState
> altogether, on the grounds that the TransitionCaptureState will
> go away at transaction cleanup and we can't really get rid of it
> any sooner than that.

End of transaction, or end of query?  I'm not sure what happens when
triggers are deferred, but I think there are a lot of cases when we
want to throw away the tuplestore immediately, not hold on to it for
the rest of the transaction.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Michael Meskes
Date:
Subject: Re: [BUGS] BUG #14801: ECPG core dump
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #14808: V10-beta4, backend abort