If you’re seeing it in dev - where Hyperdrive’s connection logic isn’t in place - it might be someth

If you’re seeing it in dev - where Hyperdrive’s connection logic isn’t in place - it might be something else. Are you doing something odd with your driver/client code?

MMatt Silverlock If you’re seeing it in dev - where Hyperdrive’s connection logic isn’t in place ...

bs_sfalls•8/20/24, 5:22 PM

Nothing unique and no problems normally. The only issue is if I send off 2 simultaneous connections from react at roughly the same time. I see it in wrangler and I see it in workers production. Using Hono and Kysley. I'll dig a bit more, as of right now, just staggering the requests.

Bbs_sfalls Nothing unique and no problems normally. The only issue is if I send off 2 simu...

Ping for toast•8/20/24, 9:07 PM

I think its possible I'm experiencing this as well

PPing for toast odd. I know that they have the same ip pool so i was wondering because for about...

Ping for toast•8/20/24, 9:08 PM

up here

Ping for toast•8/20/24, 9:08 PM

started getting this error a couple days ago

Ping for toast•8/20/24, 9:09 PM

that looks like a bug

Ping for toast•8/20/24, 9:09 PM

and i suppose it is

Ping for toast•8/20/24, 9:09 PM

but whats interesting is

Ping for toast•8/20/24, 9:11 PM

function n(i) {
  e50.apply(null, i), r = null;
}
function un() {
  Et($r.connection("CONNECT_TIMEOUT", e50, D)), D.destroy();
}
function Et(H) {
  ae && (ae.destroy(H), ae = null), ye && ft(ye, H), z && (ft(z, H), z = null);
}
function ft(H, ue) {
  Object.defineProperties(ue, { stack: { value: ue.stack + H.origin.replace(/.*\n/, `
`), enumerable: e50.debug }, query: { value: H.string, enumerable: e50.debug }, parameters: { value: H.parameters, enumerable: e50.debug }, args: { value: H.args, enumerable: e50.debug }, types: { value: H.statement && H.statement.types, enumerable: e50.debug } }), H.reject(ue);
}

function n(i) {
  e50.apply(null, i), r = null;
}
function un() {
  Et($r.connection("CONNECT_TIMEOUT", e50, D)), D.destroy();
}
function Et(H) {
  ae && (ae.destroy(H), ae = null), ye && ft(ye, H), z && (ft(z, H), z = null);
}
function ft(H, ue) {
  Object.defineProperties(ue, { stack: { value: ue.stack + H.origin.replace(/.*\n/, `
`), enumerable: e50.debug }, query: { value: H.string, enumerable: e50.debug }, parameters: { value: H.parameters, enumerable: e50.debug }, args: { value: H.args, enumerable: e50.debug }, types: { value: H.statement && H.statement.types, enumerable: e50.debug } }), H.reject(ue);
}

Ping for toast•8/20/24, 9:11 PM

CONNECT_TIMEOUT?

Ping for toast•8/20/24, 9:16 PM

function connectTimedOut() {
  errored(Errors.connection('CONNECT_TIMEOUT', options, socket))
  socket.destroy()
}
function errored(err) {
  stream && (stream.destroy(err), stream = null)
  query && queryError(query, err)
  initial && (queryError(initial, err), initial = null)
}
function queryError(query, err) {
  Object.defineProperties(err, {
    stack: { value: err.stack + query.origin.replace(/.*\n/, '\n'), enumerable: options.debug },
    query: { value: query.string, enumerable: options.debug },
    parameters: { value: query.parameters, enumerable: options.debug },
    args: { value: query.args, enumerable: options.debug },
    types: { value: query.statement && query.statement.types, enumerable: options.debug }
  })
  query.reject(err)
}

function connectTimedOut() {
  errored(Errors.connection('CONNECT_TIMEOUT', options, socket))
  socket.destroy()
}
function errored(err) {
  stream && (stream.destroy(err), stream = null)
  query && queryError(query, err)
  initial && (queryError(initial, err), initial = null)
}
function queryError(query, err) {
  Object.defineProperties(err, {
    stack: { value: err.stack + query.origin.replace(/.*\n/, '\n'), enumerable: options.debug },
    query: { value: query.string, enumerable: options.debug },
    parameters: { value: query.parameters, enumerable: options.debug },
    args: { value: query.args, enumerable: options.debug },
    types: { value: query.statement && query.statement.types, enumerable: options.debug }
  })
  query.reject(err)
}

its a bug in postgres.js, caused by CONNECTION_TIMEOUTs

Bbs_sfalls Nothing unique and no problems normally. The only issue is if I send off 2 simu...

Ping for toast•8/20/24, 9:38 PM

Furthermore, I can corroborate that the issue is solved when hyperdrive is disabled

Ping for toast•8/20/24, 9:39 PM

I can tell that hyperdrive was properly disabled because requests now take about 200ms longer

AJR•8/20/24, 10:04 PM

How interesting. Can you share a code snippet that induces this behavior? How often/reliably does it reproduce for you?

AJR•8/20/24, 10:06 PM

Aside, you should be seeing better caching behavior now, btw, @Ping for toast . How's it looking on your side?

AAJR How interesting. Can you share a code snippet that induces this behavior? How ...

Ping for toast•8/20/24, 10:11 PM

By a code snippet, do you mean you're asking for a minimum reproducible example? My configuration is very much like bs_sfalls

I use solid-start and hyperdrive, and my backend is elysia with hyperdrive.
The backend is hosted on a separate worker.
In SSR, two requests are fired simultaneously — one to retrieve data about the current user, and one to fetch the data presented on the page, using service bindings
This can obviously be triggered by doing a page reload.
Until said page reload happens, requests work fine
After n seconds (where n is unknown; greater than 30s and less than 5 minutes?), presumably after hyperdrive disconnects // the worker cools down, it begins working again

It seems to reproduce perfectly.

Ping for toast•8/20/24, 10:11 PM

Caching is a lot better — 50% or so

Ping for toast•8/20/24, 10:12 PM

I also literally just switched db hosts as I thought this would be a good opportunity, so I will test it again to see if it reproduces

AJR•8/20/24, 10:16 PM

Interesting. We do have some rate limiting in place but it wouldn't be triggered by a single pair of simultaneous requests, and even if it was it would only lock out for a couple hundred ms.

I'm going to have to dig at this a bit. I'll put together a ticket for it

You said this only started within the last week or so?

@bs_sfalls same timeframe for you, just the last week or so?

AAJR Interesting. We do have some rate limiting in place but it wouldn't be trigger...

Ping for toast•8/20/24, 10:16 PM

yup, you can actually see the first time i noticed it

PPing for toast https://www.cloudflarestatus.com/incidents/035gqnkz86zh was there possibly downt...

Ping for toast•8/20/24, 10:16 PM

right here :)

Ping for toast•8/20/24, 10:16 PM

it could have been up to a week tho

Ping for toast•8/20/24, 10:23 PM

Reproduced

Ping for toast•8/20/24, 10:24 PM

The reason that it looks like the html has loaded is because of streaming

Aalexrobinson Not to mention that we have docs about the setup process here. Have you been fol...

Igor•8/21/24, 8:55 PM

Yes followed the instructions, using the exact same code as the examples in the documentation. Getting the error 'PostgresError: server requires encryption' when postgres in the Cloudflare worker attempts to set up a connection.

    const client = new Client({
      connectionString: env.HYPERDRIVE.connectionString,
    });

    try {
      // Connect to our database
      await client.connect();

    const client = new Client({
      connectionString: env.HYPERDRIVE.connectionString,
    });

    try {
      // Connect to our database
      await client.connect();

PPing for toast The reason that it *looks* like the html has loaded is because of streaming

Ping for toast•8/22/24, 3:22 PM

Any updates on this? If not, would you mind pinging me when there's updates

, it would be very appreciated

PPing for toast Any updates on this? If not, would you mind pinging me when there's updates ❤️ ,...

AJR•8/22/24, 5:01 PM

Will ping you when we have anything to share on this one. You'd better have toast.

AAJR Will ping you when we have anything to share on this one. You'd better have toa...

Ping for toast•8/22/24, 5:02 PM

always

BumblebeeSquare•8/23/24, 5:53 AM

hi gusy does worker support node-postgres's pg.Pool ? when i building with svelte Cloudflare adapter, i got fs,dns,...etc not supported error

BBumblebeeSquare hi gusy does worker support node-postgres's pg.Pool ? when i building with svelt...

Isaac McFadyen•8/23/24, 12:55 PM

Make sure you have nodejs_compat enabled in your wrangler.toml.

Isaac McFadyen•8/23/24, 12:56 PM

compatibility_flags = ["nodejs_compat"]

compatibility_flags = ["nodejs_compat"]

AJR•8/23/24, 1:02 PM

Morning all! Yep, that scenario is why we sunk some time into getting postgres-js supported, and now recommend it.

BumblebeeSquare•8/23/24, 4:27 PM

oh ok, maybe it is good idea to put a warning on this page https://developers.cloudflare.com/workers/tutorials/postgres/

Cloudflare Docs

Connect to a PostgreSQL database with Cloudflare Workers | Cloudfla...

In this tutorial, you will learn how to create a Cloudflare Workers application and connect it to a PostgreSQL database using TCP Sockets. The Workers application you create in this tutorial will interact with a product database inside of PostgreSQL.

AJR•8/23/24, 4:54 PM

I'll take a look through and add that. Appreciate the suggestion

tester123•8/28/24, 5:37 PM

has anyone used hyperdrive with neondb? What is the latency that you guys are getting?

Isak•8/28/24, 8:12 PM

Neon databases are hosted in a single region so you need to use smart placement in the same region to get acceptable latency.

Ttester123 has anyone used hyperdrive with neondb? What is the latency that you guys are ge...

Emilio•8/28/24, 8:24 PM

I personally use a neon database for testing, and get sub 100 millisecond latency on hot connections without caching -- but your results will vary based on where your requests are coming from and where you neon database is located

EEmilio I personally use a neon database for testing, and get sub 100 millisecond latenc...

tester123•8/29/24, 5:13 AM

I created one in Frankfurt and I'm based in Malta, so I was getting 200-300ms for a single query (not cached I think), using the hyperdrive with postgres.js. Btw, I haven't managed making hyperdrive work with the serverless neondb driver (via drizzle orm), but only with postgres.js. Maybe the serverless driver of neondb is not supported in cloudflare?

tester123•8/29/24, 5:15 AM

also, which driver do you recommend using with hyperdrive? Are you using postgres.js yourself as well, instead of the serverless driver of neon?

Ttester123 I created one in Frankfurt and I'm based in Malta, so I was getting 200-300ms fo...

Matt SilverlockOP•8/29/24, 12:38 PM

The serverless Neon driver is supported… it’s just slower than Hyperdrive: https://blog.cloudflare.com/hyperdrive-making-regional-databases-feel-distributed/

The Cloudflare Blog

Hyperdrive: making databases feel like they’re global

Hyperdrive makes accessing your existing databases from Cloudflare Workers, wherever they are running, hyper fast.

Ttester123 also, which driver do you recommend using with hyperdrive? Are you using postgre...

Matt SilverlockOP•8/29/24, 12:38 PM

All of our docs recommend Postgres.js and our teams internally use it.

Matt SilverlockOP•8/29/24, 12:39 PM

https://developers.cloudflare.com/hyperdrive/configuration/connect-to-postgres/

Cloudflare Docs

Connect to PostgreSQL | Hyperdrive

Hyperdrive supports PostgreSQL and PostgreSQL-compatible databases, popular drivers and Object Relational Mapper (ORM) libraries that use those drivers.

MMatt Silverlock The serverless Neon driver is supported… it’s just slower than Hyperdrive: https...

tester123•8/29/24, 4:27 PM

Thanks for your kind reply. I was referring that I did not manage to use the serverless Neon driver together with Hyperdrive (not separately!). I don't think hyperdrive can work together with the serverless driver without changing it to postgres.js. More info here:
https://orm.drizzle.team/docs/get-started-postgresql#neon-postgres

Drizzle ORM - PostgreSQL

Drizzle ORM is a lightweight and performant TypeScript ORM with developer experience in mind.

Ttester123 Thanks for your kind reply. I was referring that I did not manage to use the ser...

Matt SilverlockOP•8/29/24, 4:41 PM

The Neon serverless driver uses WebSockets — because most serverless providers don't have something like Hyperdrive — so they aren't compatible and can't be.

WebSocket-per-request is still slower than using Hyperdrive's connection pooling (by a fair bit, as the blog lays out)

MMatt Silverlock The Neon serverless driver uses WebSockets — because most serverless providers d...

tester123•8/29/24, 5:41 PM

Thank you very much for your detailed reply, this clears a lot of the confusion I had

May I ask about any future plans for Hyperdrive? It's a really amazing product!
Thank you once again! I'll proceed with using postgres.js.

Lila Rest•8/31/24, 10:09 AM

Hello there! Has anyone managed to make a NextJS app hosted on Cloudflare Pages to fetch its Postgres database through Hyperdrive?

MMatt Silverlock https://developers.cloudflare.com/hyperdrive/configuration/connect-to-postgres/

anirudh•9/2/24, 2:30 PM

There was an issue with prepared statements and extra round trips to the DB with postgres.js. Has that been resolved?

anirudh•9/2/24, 2:30 PM

We saw a reduction in latency by using the node-pg driver

Aanirudh There was an issue with prepared statements and extra round trips to the DB with...

Matt SilverlockOP•9/2/24, 3:12 PM

Quite some time ago - we discussed that here too. https://developers.cloudflare.com/hyperdrive/platform/changelog/#2024-05-22

Cloudflare Docs

Changelog | Hyperdrive

anirudh•9/2/24, 3:16 PM

Oh. Let me check again. I remember trying it after sometime in June/July and still having the issue.

lifeiscontent•9/5/24, 6:39 PM

for hyperdrive, could I connect to it via a pages app or would I have to use worker sites?

function connectTimedOut() { errored(Errors.connection('CONNECT_TIMEOUT', options, socket)) socket.destroy() } function errored(err) { stream && (stream.destroy(err), stream = null) query && queryError(query, err) initial && (queryError(initial, err), initial = null) } function queryError(query, err) { Object.defineProperties(err, { stack: { value: err.stack + query.origin.replace(/.*\n/, '\n'), enumerable: options.debug }, query: { value: query.string, enumerable: options.debug }, parameters: { value: query.parameters, enumerable: options.debug }, args: { value: query.args, enumerable: options.debug }, types: { value: query.statement && query.statement.types, enumerable: options.debug } }) query.reject(err) }

If you’re seeing it in dev - where Hyperdrive’s connection logic isn’t in place - it might be someth

Similar Threads