Closed Bug 794645 Opened 12 years ago Closed 7 years ago

Separate views from mat views in the docs

Categories

(Socorro :: General, task)

Product:
Socorro
Component:
General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: selenamarie, Unassigned, Mentored)

Details

Separate views from mat views in the docs
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [mentor=selena@mozilla.com]
Mentor: sdeckelmann
Whiteboard: [mentor=selena@mozilla.com]
Can I get a more detailed description for this, so that I can farm it out to the community?
Flags: needinfo?(sdeckelmann)
We would like to document the differences between "materialized views" - in our case, actual tables that are written to, and the "views" which are Postgres VIEWs which query underlying tables on-demand.  Currently these are documented as though they are the same, leading to performance issues when the wrong tables are used. 

To find this information, a person could look into socorro/external/postgresql/raw_sql/views to find the VIEW information and socorro/external/postgresql/models.py to locate "materialized views" - which are primarily tables that serve report data to the middleware. The targeted tables are mentioned in this diagram: http://socorro.readthedocs.org/en/latest/databaseschema.html#materialized-view-reporting

Ideally someone would consult with the #breakpad channel as they embarked on this.
Flags: needinfo?(sdeckelmann)
per 1361394, we intend to delete or rewrite
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.