You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sending link privately. When that happens again I'll try to take the
dump early.
> PS Stack shows that EXECUTE STATEMENT is used, probably with autonomous
> transactions - it could block itself if used not correctly (for example:
> update record and then update it again in autonomus tx with "wait"
> option)
Any suggestion how to implement test for this ticket ?
The text was updated successfully, but these errors were encountered:
summary: Engine could hang up if auto-sweep is starting while database is shuttign down => Engine could hang up if auto-sweep is starting while database is shutting down
Sending link privately. When that happens again I'll try to take the
dump early.
> PS Stack shows that EXECUTE STATEMENT is used, probably with autonomous
> transactions - it could block itself if used not correctly (for example:
> update record and then update it again in autonomus tx with "wait"
> option)
Any suggestion how to implement test for this ticket ?
Submitted by: @hvlad
The issue was reported by Jiří Činčura at fb-devel (26 Sep 2016, " Stuck transaction in 2.5.6") :
https://sourceforge.net/p/firebird/mailman/message/35391555/
Commits: 0c520b8 51cb2c9 d4e6436
====== Test Details ======
Quote from https://sourceforge.net/p/firebird/mailman/message/35391555/
Sending link privately. When that happens again I'll try to take the
dump early.
> PS Stack shows that EXECUTE STATEMENT is used, probably with autonomous
> transactions - it could block itself if used not correctly (for example:
> update record and then update it again in autonomus tx with "wait"
> option)
Any suggestion how to implement test for this ticket ?
The text was updated successfully, but these errors were encountered: