Partition Daily Tables for Long-Term Performance

User Story

As a developer, I want a data model that will provide longer-term performance for more data and larger data window queries.

This epic encompasses all work to achieve this goal. The work in this epic will be focused primarily on the database engine as well as the data model.
Relevant changes or developer documentation will be required outputs of this work to document how new partitioned tables are to be created as well as how these partitioned tables are to be maintained and deleted.

Impacts

• Data Model
  • Documentation
  • Primary, Foreign Key changes
  • Constraint changes
• Database
  • Upgrade engine to latest RDS production version
  • Structure conversion, data migration
• API (Migrations)
  • Migration changes for new partitions
  • Test migration process changes all partitions of primary table
  • Determine if the tenet schema migration process is viable for creating a new set of customer data tables

Related Stories

• None

External Dependencies

• RHOPS (RDS instance changes)

UX Requirements

• None

UI Requirements

• None

Documentation Requirements

• User-Facing: None
• Developer-Facing: Description of the partitioning as well as the changes to migrations needed to successfully run them

Backend Requirements

• Verify table changes via migrations
• Determine if there is any django support for partitioned tables in PostgreSQL

QE Requirements

• psql and the ability to connect to PostgreSQL databases directly

Release Criteria

• The tickets for this spec should be able to be released in parts without the full epic being completed
• There are no UI requirements for this ticket and this ticket should not affect the UI itself

Has QE approved this epic?

• Awaiting approval