You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Queries using the current state logic here are already a bit slow, and will only get slower as the number of records grows. This is because the filemanager never deletes records, even though records transition from current to historical data.
This can be improved by partitioning the records by historical and current state, which should improve the speed of queries on the current state. In order to do this a new column should be added that can be used to split the data.
Tasks:
Add new is_current_state column and adjust the API to use it.
Partition the records on the new column.
This will involve some complexity because the table needs to be recreated. Also, in postgres, globally unique constraints can't apply across partitions which will affect the event de-duplication logic.
The text was updated successfully, but these errors were encountered:
Queries using the current state logic here are already a bit slow, and will only get slower as the number of records grows. This is because the filemanager never deletes records, even though records transition from current to historical data.
This can be improved by partitioning the records by historical and current state, which should improve the speed of queries on the current state. In order to do this a new column should be added that can be used to split the data.
Tasks:
is_current_state
column and adjust the API to use it.The text was updated successfully, but these errors were encountered: