zitadel/internal/eventstore/repository
Silvan 4dc86c2415
fix(eventstore): order by sequence if filter by aggregate id (#8019)
# Which Problems Are Solved

Queriying events by an aggregate id can produce high loads on the
database if the aggregate id contains many events (count > 1000000).

# How the Problems Are Solved

Instead of using the postion and in_tx_order columns we use the sequence
column which guarantees correct ordering in a single aggregate and uses
more optimised indexes.

# Additional Context

Closes https://github.com/zitadel/DevOps/issues/50

Co-authored-by: Livio Spring <livio.a@gmail.com>
2024-05-28 06:49:30 +00:00
..
mock fix: add action v2 execution to features (#7597) 2024-04-09 20:21:21 +03:00
sql fix(eventstore): order by sequence if filter by aggregate id (#8019) 2024-05-28 06:49:30 +00:00
asset.go feat: add assets to eventstore and event (#1674) 2021-04-27 12:58:18 +02:00
event.go feat(eventstore): increase parallel write capabilities (#5940) 2023-10-19 12:19:10 +02:00
search_query_test.go feat(eventstore): increase parallel write capabilities (#5940) 2023-10-19 12:19:10 +02:00
search_query.go chore: use pgx v5 (#7577) 2024-03-27 15:48:22 +02:00