Closed Bug 1361394 Opened 5 years ago Closed 3 years ago
[tracker] Simplify and clean up postgresql schema
Our current database schema is huge and has a lot of obsolete data. The deprecation rampage removed the need for many tables, stored procedures and matviews. We want to audit our database to figure out exactly which elements we actually use at the moment, remove the rest, and then see if it's possible to simplify it even further.
Documentation about the current plan of action: https://docs.google.com/document/d/1Vfxx3R3MO9D9x2hTHnXTzmEU-OyVLdc3HDqH6OExo9E/edit?pli=1#heading=h.n824gaooepd4 Documentation about existing tables in our database: https://docs.google.com/spreadsheets/d/1Oke1PN2jkLlKPMmDY64xPTnHDMbQU-DM7rSIhOGN7Xg/edit#gid=0
Update on this project--we still want to do the following things: 1. Drop ADI and all the related things from Socorro. This covers some stored procedures, a bunch of tables, and some crontabber jobs. 2. Write a new product/version/build info acquiring system that's based on Buildhub and retire ftpscraper. This will let us remove a swatch of stored procedures and tables. 3. Move whatever's left from alembic/sqlalchemy land to Django land. At that point, the webapp owns the database and we can use Django's tools to manage it. This will let us drop a ton of code. We'll be in a much better spot going forward.
Summary: [tracker] Simplify postgresql database schema → [tracker] Simplify and clean up postgresql schema
We should still rewrite crontabber, but otherwise this is done. Marking as FIXED.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.