Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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.
Comments
Comment #2
alexpottComment #3
dawehnerLooks reasonable for me.
Comment #4
catchsqlite isn't happy. Sending for re-test.
Comment #5
alexpottSeems fine now and I can't see how the simpletest https test is related to this so back to rtbc.
Comment #6
alexpottI 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
Comment #7
catchPostponing on #2487269: Postgres insert queries that fail in a transaction break the entire transaction.
Comment #8
alexpott#2487269: Postgres insert queries that fail in a transaction break the entire transaction got committed so back to rtbc as per #3
Comment #10
catchCommitted/pushed to 8.1.x, thanks!