dev-mcps/postgres-mcp/test
Lucio Lelii 23a9060112 Say why a PostgreSQL connection never reached the server
A connection that failed before PostgreSQL answered was reported as "connection failed (Error)", which
said nothing: a timeout from a firewall dropping the port looked like any other fault. It now says
which it was - the host does not resolve, the connection was refused, timed out, was closed before an
answer, or the TLS handshake failed - in words that point at where to look, still without the
address or the credentials. The internal mode's own connection, as the catalog's user, says the same.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-05 10:06:52 +02:00
..
connection-failure.test.js Say why a PostgreSQL connection never reached the server 2026-10-05 10:06:52 +02:00
connection-registry.test.js External sessions connect where the node says, not where the model says 2026-10-05 09:54:33 +02:00
execution-database.test.js Add postgres-mcp: SQL for a model, in a database of its own for each execution 2026-10-02 20:04:52 +02:00
host-guard.test.js External sessions connect where the node says, not where the model says 2026-10-05 09:54:33 +02:00
integration.test.js External sessions connect where the node says, not where the model says 2026-10-05 09:54:33 +02:00
streamable-http.test.js Add postgres-mcp: SQL for a model, in a database of its own for each execution 2026-10-02 20:04:52 +02:00
tool-definitions.test.js External sessions connect where the node says, not where the model says 2026-10-05 09:54:33 +02:00