You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ PostgreSQL pooler (like PgBouncer) with sharding, load balancing and failover su
19
19
| Sharding |:white_check_mark:| Transactions are sharded using `SET SHARD TO` and `SET SHARDING KEY TO` syntax extensions; see examples below. |
20
20
| Failover |:white_check_mark:| Replicas are tested with a health check. If a health check fails, remaining replicas are attempted; see below for algorithm description and examples. |
21
21
| Statistics reporting |:white_check_mark:| Statistics available in the admin database (`pgcat` and `pgbouncer`) with `SHOW STATS`, `SHOW POOLS` and others. |
22
-
| Live configuration reloading |:construction_worker:| Reload supported settings with a `SIGHUP` to the process, e.g. `kill -s SIGHUP $(pgrep pgcat)` or `RELOAD` query issued to the admin database. |
22
+
| Live configuration reloading |:white_check_mark:| Reload supported settings with a `SIGHUP` to the process, e.g. `kill -s SIGHUP $(pgrep pgcat)` or `RELOAD` query issued to the admin database. |
23
23
| Client authentication |:x::wrench:| On the roadmap; currently all clients are allowed to connect and one user is used to connect to Postgres. |
0 commit comments