Does Hyperdrive supports Xata with direct postgres connection? Supabase works fine for me but xata d
Does Hyperdrive supports Xata with direct postgres connection? Supabase works fine for me but xata do not work. Show /inactive on dashboard.
AInteresting! I hadn't heard of Xata. We've tested across many providers, but that one may be doing something different enough that there's an issue. I'll ask around the team, and take a look when I have some spare cycles if none of them are familiar with it.
MDoes the Xata database have Postgres enabled? “Inactive” means we haven’t seen any recent queries - when you say “doesn’t work” do you mean you can’t query it from your Worker?
DThe hyperdrive stabilished but a simple query run forever with no return. Using pgcli or psql I can connect and run the same query.
DUsing postgres.js direct I can connect but with Hyperdrive, no way.
MMind sharing your account ID and the ID of your Hyperdrive configuration? (both are safe to make public)
We’ll take a look. Wonder if something strange with Xata’s new Postgres connection support.
We’ll take a look. Wonder if something strange with Xata’s new Postgres connection support.
ICockroachDB requires installing a client CA certificate, yet Cloudflare Hyperdrive doesn't support uploading your own certificates. How is anyone able to connect to CockroachDB with Hyperdrive? (getting the error
PostgresError: server requires encryption)AI'll let someone who knows more about Cockroach chime in if they know a way to accomplish this.
However we are planning to add support for custom CA verification. It's a complex feature so it won't be very soon, but it's on our roadmap (and near the top of it).
However we are planning to add support for custom CA verification. It's a complex feature so it won't be very soon, but it's on our roadmap (and near the top of it).
あHow to use google alloydb with hyperdrive? I can't specify 0.0.0.0/0 as the public IP.
https://blog.cloudflare.com/it-it/hyperdrive-making-regional-databases-feel-distributed
https://blog.cloudflare.com/it-it/hyperdrive-making-regional-databases-feel-distributed
The Cloudflare Blog
Hyperdrive makes accessing your existing databases from Cloudflare Workers, wherever they are running, hyper fast.
DFor sure. I'll share right now
I
あIs there a solution?
TResponded in thread
TSame here
AAThe recent postgres.js work did a lot to unblock this, as the nodejs_compat flag works with postgres.js, and also with pages, which was I think one of the last blockers there
MDoes Hyperdrive play nicely with Postgres transactions, or would they conflict in any way? I know Hyperdrive handles pooling, hence the question, whereas PG transactions depend on using a pool client, not on-the-fly, one-off queries.
AIt works well with them but they do impose some costs.
- We don't cache parts of transactions, so you'll always be serving from origin
- The client holds the connection until the transaction completes or rolls back, which limits the amount of scaling available
MGreat, thanks for the info.
✅Suggestion: Support mongodb in hyperdrive
MThis may be more a general PG question, but asking here in case there's any HD implications/angle on it: is it advisable to cache the
do:
Clientreq, rather than create it for each query? i.e. instead of:do:
INo.
req is new every time and the client will be recycled.IAlso it's fine to recreate clients with Hyperdrive, it holds open connections for you.
HI think they meant if a single Request runs multiple queries across different handlers
IOh I see
IThen yeah, could work. I'd still be wary of mutating request state though... I've always been told not to do that by various frameworks
IIf Workers changes something internally on the request you have no guarantee that
req.client will still be unused (unlikely it will be but possible?)HSome frameworks do provide a "state" store somewhere that will be passed around, so I would use that if possible
IYeah this
IHono calls it context, Fastify calls it state.
IThere's nothing workers-native though I don't think.
HIsn't the "official" one
req.cf?HLike, as in, they don't guarantee that they won't put new stuff on it, but it will be passed around
IYeah but that's even more likely to be overwritten.
II guess if you name your thing something obscure it'll work, but I can imagine a
req.cf.client some day for some service or another.
Mseem to be experiencing an outage again, with hyperdrive connection latency spikes. is there anyone available who can look into it?
ALet me take a look. Same config ID you'd previously sent?
ALooks like the ID you'd sent previously is not seeing traffic. Please post or DM the one you're seeing issues with. I'm not seeing latency spikes globally, but individual configs certainly could be. Happy to take a look.
MInteresting - I've seen frameworks absolutely encourage storing things on
req between middleware. Otherwise you'd have no option but to laboriously pass around manually a ton of data as function arguments.MExactly.
IAbsolutely, but there's usually a property dedicated towards it.
ILike
ctx or similar.
P
ANo, not for Hyperdrive. Not that I've seen or know of.
Podd. I know that they have the same ip pool so i was wondering because for about a minute i had connection timeouts
BSeeing an interesting problem with workers, may or may not be a result of hyperdrive. I have an API implemented in workers with typescript and I'm running React in Pages. Some of my components load 2 different requests simultaneously. Sometimes, works fine, a lot of times, one of the requests receives a connection timeout from the DB. If I disable hyperdrive, the problem goes away. If I stagger the request by a second or two then there is no problem. Is it possible hyperdrive or workers cannot locate a connection in such quick succession? Should I serialize the requests?
Interestingly, I also see the problem locally with wrangler dev. Again, stagger the requests, no issue.
Interestingly, I also see the problem locally with wrangler dev. Again, stagger the requests, no issue.
