In system_schema() we create a semaphore table. We should change Drupal\Core\Lock\DatabaseLockBackend to only create a table if necessary - this means that alternate lock implementations can safely remove the semaphore table and know that if the site swaps back to the DatabaseLockBackend the table will be created.

Also making this change encapsulates the storage to the backend which is good for general sanity.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

alexpott created an issue. See original summary.

alexpott’s picture

dawehner’s picture

Status: Needs review » Reviewed & tested by the community

Looks reasonable for me.

catch’s picture

Status: Reviewed & tested by the community » Needs review

sqlite isn't happy. Sending for re-test.

alexpott’s picture

Status: Needs review » Reviewed & tested by the community

Seems fine now and I can't see how the simpletest https test is related to this so back to rtbc.

alexpott’s picture

I think before we commit anymore of these we need to have a think about #2664466-12: url_alias table is only used by a core service but it depends on system install if this fails in the middle of a postgres transaction we've got a problem

catch’s picture

alexpott’s picture

Status: Postponed » Reviewed & tested by the community

  • catch committed 9de3594 on 8.1.x
    Issue #2664302 by alexpott: Semaphore table is only used by a core...
catch’s picture

Status: Reviewed & tested by the community » Fixed

Committed/pushed to 8.1.x, thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.