Unwanted connections are established and remains opened consuming additional system resources when selecting a database in `Choose catalog/schema` window
- Dominant language
- Java
- Stars
- 51.8k
- Forks
- 4.4k
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 188
Description
### Description
Every click to the database in the left panel opens a new bunch of connections.
After closing this window, these connections still remains opened taking up some resources.
I would like to keep opened only active connection, not all those that I clicked and didn't finally choose.
Could you please consider closing them after closing this small window?
The number of opened connections in Postgres is limited (after reaching the limit, it gives error on opening a new connection).
I don't want to keep a lot of connections opened if I don't use most of them.
They can also potentially block some operations (drop database, rename database, etc).
If you want to have some sort of caching the connections and keeping them opened to avoid overhead costs for reopeing again, it should not overflow the max limit of connections in postgres blocking the application usage with error `FATAL: sorry, too many clients already`.
https://github.com/user-attachments/assets/2fcdc1d4-1eb3-44b5-8cb5-c89deb2a9b49
```
--query to see all established connections
select query, *
from pg_stat_activity
where pid <> pg_backend_pid()
order by backend_start
;
```
### DBeaver Version
Enterprise Edition 24.3.1-202411300022
### Operating System
Windows 10
### Database and driver
PostgreSQL 16
PostgreSQL JDBC Driver 42.7.4
### Steps to reproduce
_No response_
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.