Upgrade script for 5.23 can fail if config_backend exists and logging is enabled
https://civicrm.stackexchange.com/questions/35302/stuck-upgrading-to-5-24-1-on-joomla
The upgrade script for https://github.com/civicrm/civicrm-core/pull/15842/files#diff-2cbb1d9cc3ea352d50c109fc5ec3efb1R87 uses the dropColumn utility function https://github.com/civicrm/civicrm-core/blob/5.24.1/CRM/Upgrade/Incremental/Base.php#L236 but that function doesn't take log tables into account, so you can still have the column referenced in the trigger at the point where it then goes to update the version in civicrm_domain, which happens before the final Logging fixSchemaDifferences where it rebuilds. Note this is only a problem because config_backend is in the same civicrm_domain table. Otherwise the rebuild at the end handles it.