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
It's easy to reproduce with a stored procedure inserting many rows while nbackup -L is being issued. NBAK owns an EX-lock for the header page and waits for all pages being flushed to disk, but new pages are being marked in parallel and such a long waiting finally becomes a deadlock when the next transaction is going to start (as it also requests an EX-lock for the header page).
Submitted by: @dyemanov
Is related to QA34
It's easy to reproduce with a stored procedure inserting many rows while nbackup -L is being issued. NBAK owns an EX-lock for the header page and waits for all pages being flushed to disk, but new pages are being marked in parallel and such a long waiting finally becomes a deadlock when the next transaction is going to start (as it also requests an EX-lock for the header page).
Commits: f042dc9 fa80ab8
The text was updated successfully, but these errors were encountered: