fix(setup): reenable index creation (#9868)

# Which Problems Are Solved

We saw high CPU usage if many events were created on the database. This
was caused by the new actions which query for all event types and
aggregate types.

# How the Problems Are Solved

- the handler of action execution does not filter for aggregate and
event types.
- the index for `instance_id` and `position` is reenabled.

# Additional Changes

none

# Additional Context

none
This commit is contained in:
Silvan
2025-05-08 17:13:57 +02:00
committed by GitHub
parent 867e9cb15a
commit 60ce32ca4f
4 changed files with 19 additions and 2 deletions

View File

@@ -23,5 +23,5 @@ func (mig *InstancePositionIndex) Execute(ctx context.Context, _ eventstore.Even
}
func (mig *InstancePositionIndex) String() string {
return "54_instance_position_index_remove"
return "54_instance_position_index_again"
}

View File

@@ -1 +1 @@
DROP INDEX IF EXISTS eventstore.es_instance_position;
CREATE INDEX CONCURRENTLY IF NOT EXISTS es_instance_position ON eventstore.events2 (instance_id, position);