I'm running into an issue connecting to
I'm running into an issue connecting to a Postgres database hosted in Google Cloud SQL using the
@neondatabase/serverless driver. It looks like it's timing out but the same connection details work when I use the pg CLI tooling. Any advice?6 Replies
ambitious-aqua•16mo ago
@elmd that driver is designed specifically for use with Neon. We have a HTTP and WebSocket proxy in front of our Postgres instances. Your database on GCP doesn't have those components so it won't work with our driver.
xenial-black•16mo ago
Is that a recent change? Theres a few articles (and Drizzle's own documentation) suggests using this driver for general general edge environments https://orm.drizzle.team/learn/tutorials/drizzle-with-vercel-edge-functions#edge-compatible-driver
Drizzle ORM - Drizzle with Vercel Edge Functions
Drizzle ORM is a lightweight and performant TypeScript ORM with developer experience in mind.
ambitious-aqua•16mo ago
That wording does seem a tad misleading. Let me look into getting it addressed.
Nothing has changed, I think it's just those docs are a bit misleading.
xenial-black•16mo ago
Gotcha, I've seen a few people mention in github comments as well that they're using this driver for their non-neon databases so not sure how that's working haha!
ambitious-aqua•16mo ago
Huh! Can you share some links? I would assume that they've deployed the ws-proxy or http-proxy, e.g https://github.com/neondatabase/neon/issues/4989
GitHub
Epic: local dev setup for serverless proxy · Issue #4989 · neondata...
Motivation With more adoption of serverless driver we got more requests for local and CI setups for proxy. DoD We have local setup that is: fast to spin up and has small footprint works without int...
ambitious-aqua•16mo ago
GitHub
fix: apply corrections to edge docs for vercel/neon by evanshortiss...
This corrects the statement that Neon's serverless driver is compatible with any Postgres provider. The serverless driver is only compatible with environments where Neon's HTTP/WebSocket pr...