To reduce read-only time by a very large margin, starting with the MediaWiki 1.31 upgrade as many database updates as possible must be applied before actually upgrading MediaWiki. The only exceptions are database updates that are not compatible in the old MediaWiki version (i.e. a database update for MediaWiki 1.31 would break MediaWiki 1.30).

With the possibility of false positives, the following database updates seem to be new in MediaWiki 1.31:

• ...have img_description_id field in image table.
• ...slots table already exists.
• ...have slot_origin field in slots table.
• ...content table already exists.
• ...slot_roles table already exists.
• ...content_models table already exists.
• ...actor table already exists.
• ...rev_text_id in table revision already modified by patch patch-rev_text_id-default.sql.
• ...table site_stats already modified by patch patch-site_stats-modify.sql.
• ...index rc_namespace_title_timestamp already set on recentchanges table.
• ...user_stats table does not contain stats_year_id field.
• ...user_profile table does not contain up_last_seen field.
• ...wb_ips_site_page key doesn't exist.
• ...have math_png field in mathoid table.
• ...cargo_tables_template_id key doesn't exist.
• ...ep_articles_course_id key doesn't exist.
• ...table pagetriage_tags already modified by patch /srv/mediawiki/w/extensions/PageTriage/sql/PageTriageTagsPatch.sql.
• ...Update 'Wikibase\Repo\Maintenance\PopulateTermFullEntityId' already logged as completed.

Any MediaWiki sysadmin can determine if action is necessary, but the updates should be done by Operations using pt-osc.