Why sometimes i got this error message: "Database error: PostgresError: Protocol Error: Unable to

Why sometimes i got this error
message:

"Database error: PostgresError: Protocol Error: Unable to close prepared statement: hesvlatshn72",

(I use hyperdrive -> Supabase and CF worker backend)

Aalex (he/him)Is it possible to use `localConnectionString` with a remote connectionString, we...

AJR•11/20/24, 3:18 PM

It's meant to be possible, yes, as of a couple weeks ago. I'm getting those timeouts too. I'll open a ticket to take a look when we can. Thanks!

AAgung Vivekananda Why sometimes i got this error message: "Database error: PostgresError: Proto...

AJR•11/20/24, 3:19 PM

Which driver and/or ORM are you using?

thomasgauvin•11/20/24, 3:19 PM

@alex (he/him) what version of Wrangler are you using? it works on the latest 3.88.0

AJR•11/20/24, 3:20 PM

I hit it with Neon just now on 3.88.0

thomasgauvin•11/20/24, 3:20 PM

And @alex (he/him) do you have IP allowlisting for each developers' IP address? Might be responsible for timeout

alex (he/him)•11/20/24, 3:22 PM

@thomasgauvin I'm using latest 3.88.0, and I have allowed connection from

0.0.0.0/0

0.0.0.0/0

, so I really don't think it's the cause here

alex (he/him)•11/20/24, 3:23 PM

It also happens for RDS & Neon, so two different provider.. If there is anything else I can provide, logs? Or you want me to run any command, let me know. I can provide those.

thomasgauvin•11/20/24, 3:24 PM

And presumably, developers can sign in from local machine to the pg database directly in Node or via PgAdmin?

alex (he/him)•11/20/24, 3:24 PM

Yes that's correct! However using the "original" connectionString, I have not tried to use the hyperdrive specific one postgresql://XXX:XXX@ffca328615404666884948d7d21ccf36.hyperdrive.local:5432/database?sslmode=preferpostgresql://XXX:XXX@ffca328615404666884948d7d21ccf36.hyperdrive.local:5432/database?sslmode=prefer

AJR•11/20/24, 3:25 PM

The Hyperdrive one won't work outside a Worker, that's an internally-generated identifier

AJR•11/20/24, 3:26 PM

If you deploy a random test worker with your configs it behaves as expected?

AJR•11/20/24, 3:26 PM

Any particular SSL/TLS configuration you've set up on your origin DBs? I assume not, just checking

alex (he/him)•11/20/24, 3:26 PM

Production works as expected. It really is about

localConnectionString

localConnectionString

combined with a db not running on localhost.

alex (he/him)•11/20/24, 3:27 PM

No particular SSL/TLS.. I would need to confirm if

localConnectionString

localConnectionString

works with a db on localhost

alex (he/him)•11/20/24, 3:28 PM

{"DB":{"connectionString":"postgresql://repguide_owner:XXX@ffca328615404666884948d7d21ccf36.hyperdrive.local:5432/repguide?sslmode=prefer","port":5432,"host":"ffca328615404666884948d7d21ccf36.hyperdrive.local","password":"XXX","user":"repguide_owner","database":"repguide"}}
✘ [ERROR] Uncaught (in promise) Error: write CONNECT_TIMEOUT ffca328615404666884948d7d21ccf36.hyperdrive.local:5432

      at connectTimedOut
  (file:///Users/alexanderniebuhr/Developer/Projects/frickegroup/workers/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:259:20)
      at done
  (file:///Users/alexanderniebuhr/Developer/Projects/frickegroup/workers/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:1035:8)

{"DB":{"connectionString":"postgresql://repguide_owner:XXX@ffca328615404666884948d7d21ccf36.hyperdrive.local:5432/repguide?sslmode=prefer","port":5432,"host":"ffca328615404666884948d7d21ccf36.hyperdrive.local","password":"XXX","user":"repguide_owner","database":"repguide"}}
✘ [ERROR] Uncaught (in promise) Error: write CONNECT_TIMEOUT ffca328615404666884948d7d21ccf36.hyperdrive.local:5432

      at connectTimedOut
  (file:///Users/alexanderniebuhr/Developer/Projects/frickegroup/workers/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:259:20)
      at done
  (file:///Users/alexanderniebuhr/Developer/Projects/frickegroup/workers/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:1035:8)

AJR•11/20/24, 3:28 PM

Yep. Ok, I'll circle up with Thomas to dig into this when we have some spare cycles. Making this work with remotes is a new feature, and it's worked for us in our testing, but it seems there's some configuration still to be done on our side.

AJR•11/20/24, 3:29 PM

Thanks for letting us know

alex (he/him)•11/20/24, 3:29 PM

What did you use in your testing? I'm using RDS & Neon, so two different providers which are quite common.

AAJR Which driver and/or ORM are you using?

Agung VivekanandaOP•11/20/24, 3:30 PM

I'm using node-postgres 8.13.1

AAgung Vivekananda I'm using node-postgres 8.13.1

AJR•11/20/24, 3:31 PM

Are you explicitly using CLOSE statements?

alex (he/him)•11/20/24, 3:34 PM

I would need to confirm if localConnectionString works with a db on localhost

@AJR @thomasgauvin I actually get timeouts too for a db running on localhost

let me go back one version of wrangler

Aalex (he/him)> I would need to confirm if localConnectionString works with a db on localhost ...

AJR•11/20/24, 3:35 PM

Well that's not good. That worked fine before.

Aalex (he/him)> I would need to confirm if localConnectionString works with a db on localhost ...

Slylencer•11/20/24, 3:35 PM

This is occurring for me as well

alex (he/him)•11/20/24, 3:36 PM

3.87.0 also seems to be broken for me.. maybe it's something on my system, but I'm still doubting this

Slylencer•11/20/24, 3:37 PM

I got the same error both on 3.87 and 3.88 locally as well

AJR•11/20/24, 3:40 PM

Ok, this is going to take some time to unpack. I'll let the team know.

AJR•11/20/24, 3:40 PM

Sorry for the inconvenience, all

AAJR Are you explicitly using CLOSE statements?

Agung VivekanandaOP•11/20/24, 3:40 PM

I'm not using CLOSE statement on my query

alex (he/him)•11/20/24, 3:40 PM

3.86.0 also broken for me

alex (he/him)•11/20/24, 3:42 PM

3.84.1 works for me.. 3.85.0 doesn't work at all, cause it breaks with service bindings

Aalex (he/him)3.86.0 also broken for me

AJR•11/20/24, 3:42 PM

3.83.0 is the last version before we made the only tweak I'm aware of to local dev

AJR•11/20/24, 3:42 PM

Ah, 3.84.1 works locally? Does it cooperate with local dev against a remote connection string?

Big Tay•11/23/24, 12:07 AM

I put together a very simple example repo showing a Worker + Durable object + Hyperdrive (Postgres) integration
https://github.com/shadrach-tayo/cloudflare-worker-example

I just recently migrated our Automerge CRDT sync server architecture to use Partykit + Cloudflare workers Durable Object + Hyperdrive (Postgres) with tunnel deployed in our kubernetes cluster.

Happy hacking weekend guys

GitHub

GitHub - shadrach-tayo/cloudflare-worker-example: An example reposi...

An example repository showcasing how to implement a Cloudflare worker + DurableObjects binding + Hyperdrive (Postgres) integration - shadrach-tayo/cloudflare-worker-example

Jjared I'm not able to create new Hyperdrive configs or update the existing ones via th...

Huxwell | Reown•11/26/24, 9:18 AM

Hey @AJR I'm facing the same issue.

AJR•11/26/24, 12:13 PM

Let me pass that along to the team. Thanks for letting me know.

HHuxwell | Reown Hey @AJR I'm facing the same issue.

AJR•11/26/24, 12:55 PM

Team checked and things seem to be working right now. We'll have someone reach out to you for details to try to reproduce, if you don't mind.

thomasgauvin•12/3/24, 3:36 AM

Hi folks. If you're encountering issues when trying to develop locally with Wrangler, please downgrade to 3.85.0. This is a known issue and a fix will be released soon.

https://www.cloudflarestatus.com/incidents/r6ltkr1t0vkr

Hyperdrive local development results in connection errors

Tthomasgauvin Hi folks. If you're encountering issues when trying to develop locally with Wran...

thomasgauvin•12/4/24, 12:33 AM

This fix has been released in Wrangler version 3.92.0. Please make sure to upgrade if you run into errors with connectivity.

This new version brings back support for localConnectionString for local development with Hyperdrive, with support for databases that do not require SSL.

Support for remote databases (which typically require SSL connectivity) and databases that require SSL more broadly is something we'll continue to work to bring to the Hyperdrive CLI.

Huxwell | Reown•12/4/24, 9:47 AM

Hey team, what's the best way of getting more context about these errors ?
Is there an API endpoint I can use to retrieve the error status and messages ?
Do I have to manually log the error on my worker ?

Capture_decran_2024-12-04_a_16.45.52.png

johtso•12/9/24, 11:33 AM

Is there any way to use hyperdrive without SSL?

johtso•12/9/24, 11:34 AM

I tried to enable SSL on my postgres database and for some reason it caused our infrastructure of janky old windows POS machines to fall over

flyingshoes•12/9/24, 3:30 PM

Hey team, I'm seeing an elevated amount of Error: Connection terminated unexpectedlyError: Connection terminated unexpectedly in our setup (hyperdrive enabled). We did ship some changes recently that increased some calls within a

waitUntil

waitUntil

function. Could that code be the reason why we are seeing more of these errors?

Original message was deleted

AJR•12/10/24, 2:55 PM

It's going to depend mostly on where you host your database and where your users are. Plus whether you cache or not. In general, Hyperdrive itself will add very minimal overhead, single-digit milliseconds generally. Latency for us is about network travel more than anything else.

Except for cache hits, those are stupid fast (and going to get way way faster :soonsoontm: ).

All that said, I think many folks see less than 80ms latencies, so I'd encourage you try it out for yourself.

AJR•12/10/24, 3:12 PM

Many users point Hyperdrive at Supabase with good success, if you do end up going with them.

Original message was deleted

AJR•12/10/24, 3:42 PM

Yes. The supabase-js client works well in a serverless environment like Workers, but can't take advantage of CF internals the way Hyperdrive can. So often folks find that postgres.js over Hyperdrive to Supabase ends up being a good fit for them.

AJR•12/10/24, 3:45 PM

Not that it makes a bunch of difference for your use case, but Hyperdrive is actually all Unix Sockets and RPC under the hood, at least until the queries egress back off our network. Much less overhead than HTTP, yeah.

Original message was deleted

Isaac McFadyen•12/10/24, 11:09 PM

Also the issue with Atlas wasn't HTTP but the fact that MongoDB Atlas actually ran on AWS Lambda, and their cold-start handling was suboptimal so you'd constantly get Lambda cold-starts :NotLikeThis:

Isaac McFadyen•12/10/24, 11:09 PM

HTTP works fine for DB queries but yeah a connection-oriented protocol is going to be better unless you have a reason to use HTTP

Isaac McFadyen•12/10/24, 11:10 PM

I'd also add that normally HTTP/1.1 and HTTP/2 has TCP Keep Alive which doesn't really exist in Workers because a Worker might be triggered on a different machine at any time and they can't really keep a connection alive the way you could from e.g. a Docker container

{"DB":{"connectionString":"postgresql://repguide_owner:XXX@ffca328615404666884948d7d21ccf36.hyperdrive.local:5432/repguide?sslmode=prefer","port":5432,"host":"ffca328615404666884948d7d21ccf36.hyperdrive.local","password":"XXX","user":"repguide_owner","database":"repguide"}} ✘ [ERROR] Uncaught (in promise) Error: write CONNECT_TIMEOUT ffca328615404666884948d7d21ccf36.hyperdrive.local:5432 at connectTimedOut (file:///Users/alexanderniebuhr/Developer/Projects/frickegroup/workers/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:259:20) at done (file:///Users/alexanderniebuhr/Developer/Projects/frickegroup/workers/node_modules/.pnpm/postgres@3.4.5/node_modules/postgres/cf/src/connection.js:1035:8)

Why sometimes i got this error message: "Database error: PostgresError: Protocol Error: Unable to

Similar Threads

Similar Threads

Similar Threads