Skip to content

[RelDB2] Concurrency-related stuff #3319

@luisa-beerboom

Description

@luisa-beerboom

There seem to be some uncertainties in regards to locking and concurrency. Not necessarily blockers, but uncomfortable things nonetheless. Here's a list of topics:

  • See this comment [relDB] Investigate safety of TreeSortMixin #3305 (comment) and the one above.
  • test_create_sequential_number.py test_create_sequential_numbers_race_condition problem will need to be investigated (Impulse from @hjanott was to search for dead locks in postgres)
  • db_connection_handling.py in create_os_conn_pool, try enabling prepared statements again, according to @hjanott they were disabled due to problems with concurrency.
  • system/test_write.py: the two_write_requests_with_locked_fields test deals with locks and is currently skipped. It should be fixed or deleted. It is quite possible that the concept behind the test is obsolete.
  • action/test_action_command_format.py: Implement locked fields or delete commented out code. Apparently 95% chance that the test is obsolete.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementGeneral enhancement which is neither bug nor featureneeds investigationThe cause for a bug is not clear enough, so it has to be investigated for some time

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions