Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[postgres] Avoid deadlocks in transactional editing #3001

Closed
wants to merge 2 commits into from
Closed

[postgres] Avoid deadlocks in transactional editing #3001

wants to merge 2 commits into from

Commits on Apr 14, 2016

  1. [postgres] Test for deadlocks with transactions

    @m-kuhn
    m-kuhn committed Apr 14, 2016
    Configuration menu
    Copy the full SHA
    8edbd85 View commit details
    Browse the repository at this point in the history

  2. [postgres] Avoid deadlocks in transactional editing 

    Can currently be triggered by using the field calculator to update a selection.
While an iterator is active and the connection is locked, an update statement
waits unsuccessfully for the same (locked) connection.

This commit only locks the connection while an iterator is actually fetching
data and not for its entire lifetime.
    @m-kuhn
    m-kuhn committed Apr 14, 2016
    Configuration menu
    Copy the full SHA
    419fd9e View commit details
    Browse the repository at this point in the history