Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

it takes lot of refresh attempts to connect to DB #2

Open
nikhil2406 opened this issue Mar 23, 2024 · 1 comment
Open

it takes lot of refresh attempts to connect to DB #2

nikhil2406 opened this issue Mar 23, 2024 · 1 comment

Comments

@nikhil2406
Copy link

nikhil2406 commented Mar 23, 2024

i have postgres DB in AWS. I use this client to connect to it in VScode. I need to click refresh multiple times before it can establish a connection to my AWS DB. Then the connection breaks after some inactivity, I need to then do the same refresh button click again. Is there a way to increase time it waits for connection establishment to succeed? Is there a keep alive so that it doesnt break the connection often.

update:
Here is the log i see on output. Today it connected relatively quickly. But some days i need to keep clicking refresh.
2024-03-24 11:39:53 Execute fail : SELECT datname "Database" FROM pg_database WHERE datistemplate = false order by datname ASC;
2024-03-24 11:39:53 Error: read ETIMEDOUT
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
2024-03-24 11:39:53 Execute fail : SELECT datname "Database" FROM pg_database WHERE datistemplate = false order by datname ASC;
2024-03-24 11:39:53 Error: read ETIMEDOUT
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
2024-03-24 11:39:53 Execute fail : SELECT datname "Database" FROM pg_database WHERE datistemplate = false order by datname ASC;
2024-03-24 11:39:53 Error: read ETIMEDOUT
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
2024-03-24 11:39:53 Execute fail : SELECT datname "Database" FROM pg_database WHERE datistemplate = false order by datname ASC;
2024-03-24 11:39:53 Error: read ETIMEDOUT
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
2024-03-24 11:39:54 Creating PostgreSQL connection for 1697345580019/postgres_tree
2024-03-24 11:40:15 Execute fail : SELECT nspname "schema" from pg_catalog.pg_namespace order by nspname ASC;
2024-03-24 11:40:15 Error: read ETIMEDOUT
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
2024-03-24 11:40:15 Execute fail : SELECT nspname "schema" from pg_catalog.pg_namespace order by nspname ASC;
2024-03-24 11:40:15 Error: read ETIMEDOUT
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
2024-03-24 11:40:15 Error: read ETIMEDOUT
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
2024-03-24 11:40:15 Error: read ETIMEDOUT
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
2024-03-24 11:40:16 Creating PostgreSQL connection for 1697345580019/maindb_tree

@cweijan
Copy link
Contributor

cweijan commented Mar 24, 2024

Hi, you can modify the connection timeout. The default time is 5 seconds. Is your connection to the AWS database very slow?
image

Regarding keep alive, I will try to support it in the next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants