I'm using node-postgres 8.13.1
I'm using node-postgres 8.13.1
AAre you explicitly using CLOSE statements?
AI 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
AWell that's not good. That worked fine before.
SThis is occurring for me as well
A3.87.0 also seems to be broken for me.. maybe it's something on my system, but I'm still doubting this
SI got the same error both on 3.87 and 3.88 locally as well
AOk, this is going to take some time to unpack. I'll let the team know.
ASorry for the inconvenience, all
AI'm not using CLOSE statement on my query
A3.86.0 also broken for me
A3.84.1 works for me.. 3.85.0 doesn't work at all, cause it breaks with service bindings
A3.83.0 is the last version before we made the only tweak I'm aware of to local dev
AAh, 3.84.1 works locally? Does it cooperate with local dev against a remote connection string?
BI 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
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
An example repository showcasing how to implement a Cloudflare worker + DurableObjects binding + Hyperdrive (Postgres) integration - shadrach-tayo/cloudflare-worker-example
HHey @AJR I'm facing the same issue.
ALet me pass that along to the team. Thanks for letting me know.
ATeam 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.
THi 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
https://www.cloudflarestatus.com/incidents/r6ltkr1t0vkr
TThis 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.
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.
HHey 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 ?
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 ?
JIs there any way to use hyperdrive without SSL?
JI 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
FHey team, I'm seeing an elevated amount of
Error: Connection terminated unexpectedlywaitUntilIt'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.
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.
AMany users point Hyperdrive at Supabase with good success, if you do end up going with them.
AYes. 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.
ANot 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.
IAlso 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:
IHTTP works fine for DB queries but yeah a connection-oriented protocol is going to be better unless you have a reason to use HTTP
II'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
ISo you pay for the TCP (+ maybe TLS) handshake every time for HTTP too
T@PatrickJ worth also trying out Hyperdrive + Supabase's Postgres db as well, some customers have done so with good success. You would need to use Hyperdrive as your pooler instead of Supabase's pooler, but that would ensure you have an edge-aware pooler with caching included
TYep, let us know how it goes.
A- Do you have a paid workers plan?
- Try to use psql or similar to connect to with the connection string you're providing to the dashboard. Does it work as expected?
AHey all. New release just rolled out with a pretty huge performance improvement for cache hit latencies. This one took a lot of work, so I wanted to show it off.
Today also marks my 1-year on the team, and I happened to snag a screencap of our demo page in my first week or two. So, in classical fashion: how it started vs how it's going.
Today also marks my 1-year on the team, and I happened to snag a screencap of our demo page in my first week or two. So, in classical fashion: how it started vs how it's going.
W@Hyperdrive Massive performance improvements made to Hyperdrive! See above
C
A:fingerprint:
RI tried Hyperdrive also, but it has some bugs with connectors. Overall not facing any performance issues. But if someone has question about code-related issues. I am here to answer.
AWould you care to elaborate on what bugs you're seeing?
RThank you I elaborated about issues here: Deployment Issues on Cloudflare Pages with SvelteKit 5
But I am helping here also another people from Discord community, if they have any difficulties. Feel free to give me any questions.
But I am helping here also another people from Discord community, if they have any difficulties. Feel free to give me any questions.
Fi would love to being able to connect to a remote db from local
Fis there any eta about when that's gonna be supported?
ANo hard ETA, I'm afraid. We took a shot at adding it recently and ran into some pretty serious unexpected behavior, so we are gonna have to come back to that when we have some real time to dedicate to it. It is still something we are hoping to add, but it is (apparently) more complicated than it sounds.
RI am here for assistance, because other community members reach me out to help with it. Unfortunately I am block now, but helping them as much as I can.
RDo you have any connectors in your App? I am doing it using Drizzle
Fyeah, i'm using drizzle as well so i think i will need to fallback to an env var when developing locally
