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

Use partitioned scoped events/state PostgreSQL tables #3776

Closed
olivergrabinski opened this issue Mar 29, 2023 · 0 comments · Fixed by #3787
Closed

Use partitioned scoped events/state PostgreSQL tables #3776

olivergrabinski opened this issue Mar 29, 2023 · 0 comments · Fixed by #3787

Comments

@olivergrabinski
Copy link
Contributor

Motivation
In order to make project level queries faster, the scoped events/state tables can be partitioned by project.
Changes needed:

  • Update tables schemas to allow partitions
  • When creating a project, a "companion" partition for the project is created for both scoped events and states.

Side-effects:

  • It is possible to export the events/states of a project by exporting its partition.
  • Project deletion boils down to the deletion of its partition.

Acceptance criteria

  1. When a project is created, it has a corresponding partition for its scoped events.
  2. When a project is created, it has a corresponding partition for its scoped states.

API changes
None

Not in scope

  1. When a project is deleted, its partition should also be deleted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant