On seemingly every single page access MediaWiki 1.29 and 1.29.1 issue UPDATE followed by INSERT on module_deps with the exact same data in both statements. The INSERT statement is wrapped in a transaction and fails with
Sep 29 22:49:31 db postgres[90132]: [11-3] azurlane_wiki STATEMENT: INSERT /* Wikimedia\Rdbms\Database::upsert */ INTO "module_deps" (md_module,md_skin,md_deps) VALUES [skipping the entire statement here] Sep 29 22:49:32 db postgres[90135]: [9-1] ERROR: duplicate key value violates unique constraint "md_module_skin" Sep 29 22:49:32 db postgres[90135]: [9-2] DETAIL: Key (md_module, md_skin)=(mediawiki.action.view.postEdit, vector|en-gb) already exists.
Judging by DBQuery debug logs, MediaWiki 1.28 (and 1.26 as well? unsure at the moment, but no errors are logged for these) only issues an UPDATE statement for the same table without INSERT following (provided the data is already in the table).
This floods the PostgreSQL server log files with unnecessary messages. Is there a reason this behaviour was introduced in 1.29?