zitadel/internal/database
Tim Möhlmann 25dc7bfe72
perf(cache): pgx pool connector (#8703)
# Which Problems Are Solved

Cache implementation using a PGX connection pool.

# How the Problems Are Solved

Defines a new schema `cache` in the zitadel database.
A table for string keys and a table for objects is defined.
For postgreSQL, tables are unlogged and partitioned by cache name for
performance.

Cockroach does not have unlogged tables and partitioning is an
enterprise feature that uses alternative syntax combined with sharding.
Regular tables are used here.

# Additional Changes

- `postgres.Config` can return a pxg pool. See following discussion

# Additional Context

- Part of https://github.com/zitadel/zitadel/issues/8648
- Closes https://github.com/zitadel/zitadel/issues/8647

---------

Co-authored-by: Silvan <silvan.reusser@gmail.com>
2024-10-04 13:15:41 +00:00
..
cockroach perf(cache): pgx pool connector (#8703) 2024-10-04 13:15:41 +00:00
dialect perf(cache): pgx pool connector (#8703) 2024-10-04 13:15:41 +00:00
migrate feat(cli): init cli (#3186) 2022-02-09 15:01:19 +01:00
mock chore: use pgx v5 (#7577) 2024-03-27 15:48:22 +02:00
postgres perf(cache): pgx pool connector (#8703) 2024-10-04 13:15:41 +00:00
database_test.go refactor: rename package errors to zerrors (#7039) 2023-12-08 15:30:55 +01:00
database.go perf(cache): pgx pool connector (#8703) 2024-10-04 13:15:41 +00:00
type_test.go chore: use pgx v5 (#7577) 2024-03-27 15:48:22 +02:00
type.go chore: use pgx v5 (#7577) 2024-03-27 15:48:22 +02:00