Hello, do someone has already installed odoo with pgcat ?
the repository is on github postgresml/pgcat
Pgcat is a PostgreSQL pooler and proxy (like pgbouncer) with support for sharding, load balancing, failover and mirroring, with Multi-threaded runtime
The big benefit of PgCat is multi-threaded. If you use pgbouncer at scale, you very likely have run into the problem that pgbouncer is ultimately a single-threaded asynchronous connection based pooler.
It is pretty good at handling a lot of connections, but if you have a lot of activities for individual connections, that's where you'll run into bottlenecks. PgCat don't have this issue.
I have tried but without success, if someone could help me, please. I will be very happy, thanks in advance.
some features
Feature | Status | Comments |
---|---|---|
Transaction pooling | Stable | Identical to PgBouncer with notable improvements for handling bad clients and abandoned transactions. |
Session pooling | Stable | Identical to PgBouncer. |
Multi-threaded runtime | Stable | Using Tokio asynchronous runtime, the pooler takes advantage of multicore machines. |
Load balancing of read queries | Stable | Queries are automatically load balanced between replicas and the primary. |
Failover | Stable | Queries are automatically rerouted around broken replicas, validated by regular health checks. |
Admin database statistics | Stable | Pooler statistics and administration via the pgbouncer and pgcat databases. |
Prometheus statistics | Stable | Statistics are reported via a HTTP endpoint for Prometheus. |
SSL/TLS | Stable | Clients can connect to the pooler using TLS. Pooler can connect to Postgres servers using TLS. |
Client/Server authentication | Stable | Clients can connect using MD5 authentication, supported by libpq and all Postgres client drivers. PgCat can connect to Postgres using MD5 and SCRAM-SHA-256. |
Live configuration reloading | Stable | Identical to PgBouncer; all settings can be reloaded dynamically (except host and port). |
Auth passthrough | Stable | MD5 password authentication can be configured to use an auth_query so no cleartext passwords are needed in the config file. |
Sharding using extended SQL syntax | Experimental | Clients can dynamically configure the pooler to route queries to specific shards. |
Sharding using comments parsing/Regex | Experimental | Clients can include shard information (sharding key, shard ID) in the query comments. |
Automatic sharding | Experimental | PgCat can parse queries, detect sharding keys automatically, and route queries to the correct shard. |
Mirroring | Experimental | Mirror queries between multiple databases in order to test servers with realistic production traffic. |