Skip to content

fix(db): improve Neon connection handling and error reporting - #60

Merged
abeni16 merged 1 commit into
veloxbase:mainfrom
nahom-d54:fix/neon-db-not-able-to-connect
Sep 30, 2026
Merged

abeni16 merged 1 commit into
veloxbase:mainfrom
nahom-d54:fix/neon-db-not-able-to-connect

Conversation

@nahom-d54

Copy link
Copy Markdown
Contributor
  • Increase connection and pool creation timeouts to accommodate managed PostgreSQL providers.
  • Enhance error messages for connection issues to provide more actionable feedback.
  • Ensure client-side parameters are not forwarded to the server for Neon connections.
  • Add tests for Neon-style connection parameters and error classification.
  • And more Importantly fixed neon db not being able to connect

resolves #57

- Increase connection and pool creation timeouts to accommodate managed PostgreSQL providers.
- Enhance error messages for connection issues to provide more actionable feedback.
- Ensure client-side parameters are not forwarded to the server for Neon connections.
- Add tests for Neon-style connection parameters and error classification.
@abeni16
abeni16 merged commit 2ca04f2 into veloxbase:main Sep 30, 2026
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

Successfully merging this pull request may close these issues.

Neon db not able to connect

2 participants