postgresql.sessions

Total sessions established

Dimensions:None

Technical Annotations (23)

Configuration Parameters (4)

max_connections

defines maximum simultaneous connections allowed

work_memrecommended: 64MB

start conservative, increase only if needed for specific workloads

track_activity_query_sizerecommended: 1024

default; requires server restart to change; increase if queries truncated

hikaricp.cache_prepared_statementsrecommended: consider enabling

HikariCP does not support caching prepared statements, may contribute to bind phase overhead

Error Signatures (2)

LWLock:lock_managerlog pattern

LWLock:LockManagerlog pattern

CLI Commands (2)

pgbench -c 100 -j 10 -n -f transaction.sql -T 900diagnostic

SELECT query, calls, total_exec_time, mean_exec_time, rows FROM pg_stat_statements ORDER BY total_exec_time DESC LIMIT 20;

diagnostic

Technical References (15)

CloudWatch Database Insightscomponentaverage active sessionsconceptpgbenchcomponentcheck_postgrescomponentmax_connectionscomponentwork_memcomponentsort operationsconcepthash tablesconceptpg_stat_activitycomponentpg_stat_activity.querycomponentplanidcomponentqueryidcomponentHikariCPcomponentAurora PostgrescomponentBIND phaseconcept

Related Insights (5)

Lock manager contention reduces throughput by up to 34 percent under high concurrencywarning

▸

Connection count approaching max_connections causes connection failurescritical

▸

Excessive work_mem allocation can exhaust system memory under concurrent loadcritical

▸

Query text truncation prevents full query visibility in monitoringinfo

▸

Brief CPU spike in active sessions during bind phase prevents query plan generationwarning

▸