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
..
client.yaml	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
cockroach.yaml	add github action for integration tests	2023-04-25 18:11:04 +03:00
docker-compose.yaml	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
postgres.yaml	chore(test): set connection lifetimes for postgresql (#8586)	2024-09-11 07:45:02 +00:00
steps.yaml	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
system-user-key.pem	feat: push telemetry (#6027)	2023-07-06 08:38:13 +02:00
zitadel.yaml	perf(cache): pgx pool connector (#8703)	2024-10-04 13:15:41 +00:00