Skip to content

Commit d865d9f

Browse files
committed
readme
1 parent d3310a6 commit d865d9f

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

README.md

+13-13
Original file line numberDiff line numberDiff line change
@@ -9,19 +9,19 @@ PostgreSQL pooler (like PgBouncer) with sharding, load balancing and failover su
99
**Beta**: looking for beta testers, see [#35](https://github.com/levkk/pgcat/issues/35).
1010

1111
## Features
12-
| **Feature** | **Status** | **Comments** |
13-
|--------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
14-
| Transaction pooling | :white_check_mark: | Identical to PgBouncer. |
15-
| Session pooling | :white_check_mark: | Identical to PgBouncer. |
16-
| `COPY` support | :white_check_mark: | Both `COPY TO` and `COPY FROM` are supported. |
17-
| Query cancellation | :white_check_mark: | Supported both in transaction and session pooling modes. |
18-
| Load balancing of read queries | :white_check_mark: | Using round-robin between replicas. Primary is included when `primary_reads_enabled` is enabled (default). |
19-
| Sharding | :white_check_mark: | Transactions are sharded using `SET SHARD TO` and `SET SHARDING KEY TO` syntax extensions; see examples below. |
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-
| Statistics | :white_check_mark: | Statistics available in the admin database (`pgcat` and `pgbouncer`) with `SHOW STATS`, `SHOW POOLS` and others. |
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-
| Client authentication | :x: :wrench: | On the roadmap; currently all clients are allowed to connect and one user is used to connect to Postgres. |
24-
| Admin database | :white_check_mark: | The admin database, similar to PgBouncer's, allows to query for statistics and reload the configuration. |
12+
| **Feature** | **Status** | **Comments** |
13+
|--------------------------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
14+
| Transaction pooling | :white_check_mark: | Identical to PgBouncer. |
15+
| Session pooling | :white_check_mark: | Identical to PgBouncer. |
16+
| `COPY` support | :white_check_mark: | Both `COPY TO` and `COPY FROM` are supported. |
17+
| Query cancellation | :white_check_mark: | Supported both in transaction and session pooling modes. |
18+
| Load balancing of read queries | :white_check_mark: | Using round-robin between replicas. Primary is included when `primary_reads_enabled` is enabled (default). |
19+
| Sharding | :white_check_mark: | Transactions are sharded using `SET SHARD TO` and `SET SHARDING KEY TO` syntax extensions; see examples below. |
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+
| Statistics | :white_check_mark: | Statistics available in the admin database (`pgcat` and `pgbouncer`) with `SHOW STATS`, `SHOW POOLS` and others. |
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+
| Client authentication | :white_check_mark: :wrench: | MD5 password authentication is supported, SCRAM is on the roadmap; one user is used to connect to Postgres with both SCRAM and MD5 supported. |
24+
| Admin database | :white_check_mark: | The admin database, similar to PgBouncer's, allows to query for statistics and reload the configuration. |
2525

2626
## Deployment
2727

0 commit comments

Comments
 (0)