Hi, Currently the error handling of normal backends only does a LWLockReleaseAll() once CurrentTransactionState->state != TRANS_DEFAULT because it's called in AbortTransaction(). There's pretty damn few places that fiddle with lwlocks outside of a transaction command, but I still do wonder whether it'd wouldn't be a tad more robust to unconditionally do a LWLockReleaseAll(), just like other error handlers are doing? In comparison to the cost of a longjmp and the rest of error handling that ought to be nearly free.
Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
