Page MenuHomePhabricator

Drop ss_admins from postgres
Closed, ResolvedPublic

Description

In MediaWiki 1.21 the ss_admins field was removed as part of a schema change. Both the standard layout was updated and schema changes for existing installs, except for Postgres.

The new installation schema for Postgres still has the field, and existing installations didn't get a patch either.

rMWbd602d20833f: Drop unused database field ss_admins (https://gerrit.wikimedia.org/r/24675).

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.
StatusSubtypeAssignedTask
InvalidNone
ResolvedPleaseStand

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 3:07 AM
bzimport set Reference to bz62103.
bzimport added a subscriber: Unknown Object (MLST).
Jdforrester-WMF subscribed.

Migrating from the old tracking task to a tag for PostgreSQL-related tasks.

I just ran into this field being still present in postgres/tables.sql when working on T56888. This field is removed since 1.21 and afaics we don't use it anywhere any more. Is there any reason that not only this field has not been dropped already but we keep creating it for new databases which are set up with postgres? Is it still used for anything? If this is only about that we need to remove that one line from postgres/tables.sql and give a short patch to drop that field, I'd be going to send in a patch for this.

Krinkle updated the task description. (Show Details)
Krinkle edited subscribers, added: Umherirrender; removed: wikibugs-l-list.
Krinkle renamed this task from drop ss_admins from postgres to Drop ss_admins from postgres.May 7 2017, 9:28 PM
Krinkle updated the task description. (Show Details)
Krinkle subscribed.

@EddieGP Nope, no reason. Looks like it was just forgotten. We can apply the same to Postgres. I'd recommend doing it as its own change separate from T56888 so that the timeline and updater path is a similar as possible between different backends.

@EddieGP Nope, no reason. Looks like it was just forgotten. We can apply the same to Postgres.

Okay, wanted to be sure about this.

I'd recommend doing it as its own change separate from T56888 so that the timeline and updater path is a similar as possible between different backends.

Sure, I didn't plan to put more unrelated stuff into the T56888 patch ;-) Going to do this once I'm done on T56888 - haven't tested for oracle and not finished mssql patch yet (MS has a strange implementation of default values).

Not doing mw core work any more, at least in the short-term future.

Change 444606 had a related patch set uploaded (by PleaseStand; owner: PleaseStand):
[mediawiki/core@master] PostgreSQL: Drop three unused columns

https://gerrit.wikimedia.org/r/444606

Change 444606 merged by jenkins-bot:
[mediawiki/core@master] PostgreSQL: Drop three unused columns

https://gerrit.wikimedia.org/r/444606

Change 479740 had a related patch set uploaded (by Anomie; owner: PleaseStand):
[mediawiki/core@REL1_32] PostgreSQL: Drop three unused columns

https://gerrit.wikimedia.org/r/479740

Change 479740 merged by jenkins-bot:
[mediawiki/core@REL1_32] PostgreSQL: Drop three unused columns

https://gerrit.wikimedia.org/r/479740

As far as I can tell, all patches are merged. Can this be closed now?

Reedy assigned this task to PleaseStand.
Reedy removed a project: Patch-For-Review.