Re: backend crash with FATAL: BeginInternalSubTransaction: unexpected state END - Mailing list pgsql-bugs

From Tom Lane
Subject Re: backend crash with FATAL: BeginInternalSubTransaction: unexpected state END
Date
Msg-id 3896.1180537482@sss.pgh.pa.us
Whole thread Raw
In response to backend crash with FATAL: BeginInternalSubTransaction: unexpected state END  (Frank van Vugt <ftm.van.vugt@foxi.nl>)
Responses Re: backend crash with FATAL: BeginInternalSubTransaction: unexpected state END  (Frank van Vugt <ftm.van.vugt@foxi.nl>)
List pgsql-bugs
Frank van Vugt <ftm.van.vugt@foxi.nl> writes:
> FATAL:  BeginInternalSubTransaction: unexpected state END

Hmm, do you get the impression that user-written constraint triggers
aren't very well tested ;-) ?

It looks to me like BeginInternalSubTransaction simply needs to allow
TBLOCK_END (and TBLOCK_PREPARE too) as acceptable initial states,
because these could be seen by a function executed during COMMIT or
PREPARE TRANSACTION-time processing of deferred triggers.  I think that
the other states it rejects are OK, because we don't try to execute any
user-written code while transiting through those TBLOCK states.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Frank van Vugt
Date:
Subject: backend crash with FATAL: BeginInternalSubTransaction: unexpected state END
Next
From: Frank van Vugt
Date:
Subject: Re: backend crash with FATAL: BeginInternalSubTransaction: unexpected state END