You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After starting Timeplus Proton with 5432 port exposed from docker or using bare metal installation, I failed to connect the 5432 Postgres port
psql -h 127.0.0.1 -p 5432
psql: error: connection to server at "127.0.0.1", port 5432 failed: SSL SYSCALL error: EOF detected
connection to server at "127.0.0.1", port 5432 failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The port 5432 is certainly opening for pgsql. Otherwise if I set a different port, the error message is different
psql -h 127.0.0.1 -p 5431
psql: error: connection to server at "127.0.0.1", port 5431 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?
Impact
Some users want to use AWS QuickSight to build dashboard for Timeplus. It supports Postgres/MySQL/ClickHouse, but not Timeplus. Considering the long process of adding Timeplus data source to AWS product, we should allow users to use Postgres or MySQL port. This worked before but is broken for a while.
The text was updated successfully, but these errors were encountered:
Describe what's wrong
After starting Timeplus Proton with 5432 port exposed from docker or using bare metal installation, I failed to connect the 5432 Postgres port
The port 5432 is certainly opening for pgsql. Otherwise if I set a different port, the error message is different
Impact
Some users want to use AWS QuickSight to build dashboard for Timeplus. It supports Postgres/MySQL/ClickHouse, but not Timeplus. Considering the long process of adding Timeplus data source to AWS product, we should allow users to use Postgres or MySQL port. This worked before but is broken for a while.
The text was updated successfully, but these errors were encountered: