[Bug] Connection pool not released after Postgres query

[xuzeyu91]

Context / Scenario

await memoryDb.GetListAsync(KmsConstantcs.KmsIndex, filters: new List<MemoryFilter>() { new MemoryFilter().ByDocument(fileId) }, limit: int.MaxValue).ToListAsync().ConfigureAwait(false);

I often encounter anomalies such as sorry, too many clients are already ready when querying document slices. I have observed that each query adds a new link

SELECT count(*) FROM pg_stat_activity;

I have found that every query adds new links and they are not dispose. Frequent queries will cause my Postgres connection pool to fill up

What happened?

too many clients are already ready

Importance

I cannot use Kernel Memory

Platform, Language, Versions

I use kernel-memory to connect to Postgres

Relevant log output

too many clients are already ready