mirror of https://github.com/citusdata/citus.git
629ecc3dee
Considering the adaptive connection management
improvements that we plan to roll soon, it makes it
very helpful to know the number of active client
backends.
We are doing this addition to simplify yhe adaptive connection
management for single node Citus. In single node Citus, both the
client backends and Citus parallel queries would compete to get
slots on Postgres' `max_connections` on the same Citus database.
With adaptive connection management, we have the counters for
Citus parallel queries. That helps us to adaptively decide
on the remote executions pool size (e.g., throttle connections
if necessary).
However, we do not have any counters for the total number of
client backends on the database. For single node Citus, we
should consider all the client backends, not only the remote
connections that Citus does.
Of course Postgres internally knows how many client
backends are active. However, to get that number Postgres
iterates over all the backends. For examaple, see [pg_stat_get_db_numbackends](
|
||
|---|---|---|
| .. | ||
| backend_counter.c | ||
| colocation_utils.c | ||
| create_shards.c | ||
| deparse_function_query.c | ||
| deparse_shard_query.c | ||
| distributed_deadlock_detection.c | ||
| distributed_intermediate_results.c | ||
| distribution_metadata.c | ||
| fake_am.c | ||
| fake_fdw.c | ||
| file_utils.c | ||
| foreign_key_relationship_query.c | ||
| intermediate_results.c | ||
| metadata_sync.c | ||
| partitioning_utils.c | ||
| progress_utils.c | ||
| prune_shard_list.c | ||
| relation_access_tracking.c | ||
| run_from_same_connection.c | ||
| sequential_execution.c | ||
| shared_connection_counters.c | ||
| xact_stats.c | ||