Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partition Operational Database for Historical Data Archiving #4049

Open
4 tasks
conbrad opened this issue Oct 29, 2024 · 0 comments
Open
4 tasks

Partition Operational Database for Historical Data Archiving #4049

conbrad opened this issue Oct 29, 2024 · 0 comments
Assignees
Labels
Task Technical task that cannot be written as a user story

Comments

@conbrad
Copy link
Collaborator

conbrad commented Oct 29, 2024

Describe the task
Based on #4031 , we can use pg_slice to generate native partitioning sql.

Acceptance Criteria

  • Large tables are partitioned appropriately (e.g. date range columns that frequently exist in where clauses)
  • weather_station_model_predictions should being the largest would make sense to partition first
  • Partitioning of tables should be captured in migrations
  • An automated job runs to create new future partitions, as well as archive (dump to s3) and delete old partitions

Additional context

@conbrad conbrad added 4Refinement this ticket is ready for refinement with the team Task Technical task that cannot be written as a user story labels Oct 29, 2024
@NicolasLivanos NicolasLivanos removed the 4Refinement this ticket is ready for refinement with the team label Oct 31, 2024
@conbrad conbrad self-assigned this Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Technical task that cannot be written as a user story
Projects
None yet
Development

No branches or pull requests

2 participants