If so then likely, but if you're using some sort of global/persistent connection then probably not.
If so then likely, but if you're using some sort of global/persistent connection then probably not.
DThis is what I'm thinking of doing, putting the session in the global scope..
Dnot sure if it's a good idea
II've heard mixed things. I think it's probably fine for a new client per request since Hyperdrive is very fast to connect.
IConfirmed by an engineer here: https://canary.discord.com/channels/595317990191398933/1150557986239021106/1322396253832609835
Dso it's not reopening connections on the backend?
IIt re-opens connections to Hyperdrive, but Hyperdrive is a Durable Object running near your Worker so that's quite fast. Hyperdrive itself holds open connections even if you call
sql.end()sweet, thanks!
AAll correct, yep. Not actually a DO, though. It runs as a separate service on our servers.
DIn my Worker client, am I restricted to 6 max connections per instance?
IYes. All of the Postgres drivers (with the exception of like Neon WebSockets or certain non-Hyperdrive) connect via TCP which is subject to the 6 connection limit.
DOoo that’s good to know! So I should limit postgres.js to like 5 connections to be safe? (To avoid deadlocking unrelated http requests.)
II'd tentatively say yes unless hyperdrive has an exception applied within the runtime but I presume they do not. @AJR could confirm.
AHyperdrive does not have any exceptions in that way, same 6 connection limit applies here. If you're concerned you might want to set that limit on your postgres.js connection, yes.
DDo PostgreSQL channels work with hyperdrive?
DThis stuff.
ANo, I'm afraid not. It's something I've poked at a little, but it's not likely to get added any time soon, unfortunately.
We document a bit of this here, if it's helpful: https://developers.cloudflare.com/hyperdrive/configuration/how-hyperdrive-works/#unsupported-postgresql-features
We document a bit of this here, if it's helpful: https://developers.cloudflare.com/hyperdrive/configuration/how-hyperdrive-works/#unsupported-postgresql-features
Cloudflare Docs
Connecting to traditional centralized databases from Cloudflare's global network which consists of over 300 data center locations 
presents a few challenges as queries can originate from any of these locations.
presents a few challenges as queries can originate from any of these locations.
Dah thank you, I was walking while trying to find that page 
Does .execute and .cancel work with Hyperdrive? It's working locally, so not sure if that's a good sign or not. https://github.com/porsager/postgres?tab=readme-ov-file#execute
Does .execute and .cancel work with Hyperdrive? It's working locally, so not sure if that's a good sign or not. https://github.com/porsager/postgres?tab=readme-ov-file#execute
A.execute()Execute.cancel()If I do a .cancel(), will an error be thown?
DAYes, it should error out.
AWell, it depends on how each individual driver implements it. Reading through the docs for postgres.js it (also) considers cancellations to be best-effort, so it may swallow the errors we throw.
DDuring local dev, is Hyperdrive supposed to do connection pooling?
HI forget, isn’t Hyperdrive completely disabled in local?
HI thought it just passed in the URL directly
DIt gives a string like
4870f521c22c2295fdfaceef9b4aeca5.hyperdrive.localIs there a way to see if a connection to Hyperdrive is working without binding it to a Worker?
AWe validate connections at create time. If the credentials/hostname provided don't connect successfully you'll get an error and it'll fail to create.
DCan I validate a connection after it's created?
AWe re run it on updates. You could increase your cache ttl by 1 second or something.
Alternatively, you can bind the same Hyperdrive to multiple workers. Spin up a hello world worker and test it out that way with some small queries?
Alternatively, you can bind the same Hyperdrive to multiple workers. Spin up a hello world worker and test it out that way with some small queries?
DOh nice, so if an update works, that means for sure that the connection is good?
AYep, that's correct. The point is to avoid having folks change a password or hostname or something and have a typo that they don't notice til their alerts blow up, but it can be used for this too
AYou can confirm this on the DB side by looking at logins, if you have that monitoring set up.
AHey everyone. I'm looking for some beta testers. We have a fairly large change going out soon, that will pretty dramatically improve performance for Hyperdrives with wide geographic distributions of their users.
If you're interested, please respond in the thread I'm about to create indicating your interest, and which Hyperdrive IDs you'd like me to enroll in this beta test. I expect that we'll get this rolling early next week.
If you're interested, please respond in the thread I'm about to create indicating your interest, and which Hyperdrive IDs you'd like me to enroll in this beta test. I expect that we'll get this rolling early next week.
W@Hyperdrive 
if you want access to beta, see above!
if you want access to beta, see above!
OI see that this is beta access to active hyperdrive instances. I am eagerly awaiting the possibility of connecting mysql. I have a very large service made on Nuxt 3 with Headless for WordPress and deploys on Cloudflare and hyperdrive would probably reduce costs and improve the performance of the site.
AWe hear you.
P
Ck
IThere is a beta going on at the moment but I believe it was opt-in meaning if you haven't given your account IDs you shouldn't be in the beta 
IOne of the Hyperdrive engineers could tell you more whenever they see this, probably. Can you grab your account ID and hyperdrive ID (It's safe to share publicly)?
ANo, the beta code has been sitting out for weeks and is gated, it's not that.
Let me check our monitoring when I can get back to my desk. No outages or anything like that but I can see if we're seeing wider variation in the region right now.
Let me check our monitoring when I can get back to my desk. No outages or anything like that but I can see if we're seeing wider variation in the region right now.
IAha I was going to ping you but saw you were offline, thanks 
Mcan anyone please take a look at https://github.com/ARC-Solutions/IntelliQ-V2/tree/main/apps/dashboard whenever they have time? ive been trying to solve my issue for a week now and ive went down the route of:
Tried Deployment on CF Pages: didnt know I can get the context inside my api routes
Tried Deployment on CF Workers: my env vars weren't working
Went Back to CF Pages Again: found out about bindings, getting the context for the Hyperdrive Environment VAR, but now i've been trying to connect somehow through postgres.js but that doesn't work even though i have the nodejs_compat flag
my techstack is:
Supabase
NextJS 14
Node
Drizzle
CF Pages
Tried Deployment on CF Pages: didnt know I can get the context inside my api routes
Tried Deployment on CF Workers: my env vars weren't working
Went Back to CF Pages Again: found out about bindings, getting the context for the Hyperdrive Environment VAR, but now i've been trying to connect somehow through postgres.js but that doesn't work even though i have the nodejs_compat flag
my techstack is:
Supabase
NextJS 14
Node
Drizzle
CF Pages
GitHub
Contribute to ARC-Solutions/IntelliQ-V2 development by creating an account on GitHub.
ATaking a look now. No wider impacts, checking on traffic isolated to your region
AWe are registering very large variations in your traffic over this time period. It ranges from about 3k client connections per hour at the low end, with a steady state of about 25k client connections per hour. At the time shown, we register an approximately 10x increase in traffic for you, spiking up to about 400k client connections per hour. The connection exhaustion and performance variation you're seeing seems to be a result of this, and the connection exhaustion seems to be expected.
We have some interventions that are available for helping this, please discuss with @thomasgauvin about what we can do for you here.
We have some interventions that are available for helping this, please discuss with @thomasgauvin about what we can do for you here.
AYes it does mean that, though somewhat indirectly. I'm limited in how much I can discuss that architecture at the moment, looking forward to a rather longer blog post about it when I can. Please message me and we'll get you sorted out during next week's release.
In the mean time you can create another hyperdrive, split your load across it, and DM me the ID so I can pin it for you tonight
In the mean time you can create another hyperdrive, split your load across it, and DM me the ID so I can pin it for you tonight
MThis caught my eye. What would a global persistent connection between distinct worker requests look like, @Isaac | AS213339? I thought everything shut down, including a DB connection, when a Worker had sent its response. My app connects fresh for each request - in truth I didn't know there was another way.