Is there a solution? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

Isak

IIsak Hey can someone help me with this? https://discord.com/channels/5953179901913989...

thomasgauvin

T

thomasgauvin•8/7/24, 2:29 AM

Responded in thread

あああ Is there a solution?

thomasgauvin

T

thomasgauvin•8/7/24, 2:29 AM

Same here

copper

Ccopper found on https://discord.com/channels/595317990191398933/1158330473655840859/115...

AJR

A

AJR•8/10/24, 9:50 PM

Folks use Hyperdrive with pages , see Aha, got it working, for anyone who runs for a recent example

AJR

A

AJR•8/10/24, 9:51 PM

The 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

Mitya

M

Mitya•8/13/24, 2:01 PM

Does 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.

Mitya

MMitya Does Hyperdrive play nicely with Postgres transactions, or would they conflict i...

AJR

A

AJR•8/13/24, 2:03 PM

It 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

AJR

AAJR It works well with them but they do impose some costs. 1. We don't cache parts o...

Mitya

M

Mitya•8/13/24, 7:21 PM

Great, thanks for the info.

✅BattlefieldDuck

✅

✅BattlefieldDuck•8/15/24, 10:09 PM

Suggestion: Support mongodb in hyperdrive

Mitya

M

Mitya•8/16/24, 10:10 AM

This 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

Client

Client

instance on

req

req

, rather than create it for each query? i.e. instead of:

const runQ = async q => {
    const client = new Client(/* options */);
    await client.connect();
    return client.query(q);
}

const runQ = async q => {
    const client = new Client(/* options */);
    await client.connect();
    return client.query(q);
}

do:

const runQ = async (req, q) => {
    if (!req.client) {
        req.client = new Client(/* options */);
        await req.client.connect();
    }
    return req.client.query(q);
}

const runQ = async (req, q) => {
    if (!req.client) {
        req.client = new Client(/* options */);
        await req.client.connect();
    }
    return req.client.query(q);
}

Mitya

MMitya This may be more a general PG question, but asking here in case there's any HD i...

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 12:49 PM

No.

req

req

is new every time and the client will be recycled.

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 12:49 PM

Also it's fine to recreate clients with Hyperdrive, it holds open connections for you.

Isaac McFadyen

IIsaac McFadyen Also it's fine to recreate clients with Hyperdrive, it holds open connections fo...

Hard@Work

H

Hard@Work•8/16/24, 1:18 PM

I think they meant if a single Request runs multiple queries across different handlers

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 1:18 PM

Oh I see

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 1:18 PM

Then 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

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 1:19 PM

If Workers changes something internally on the request you have no guarantee that

req.client

req.client

will still be unused (unlikely it will be but possible?)

Isaac McFadyen

IIsaac McFadyen Then yeah, could work. I'd still be wary of mutating request state though... I'v...

Hard@Work

H

Hard@Work•8/16/24, 1:20 PM

Some frameworks do provide a "state" store somewhere that will be passed around, so I would use that if possible

Hard@Work

HHard@Work Some frameworks do provide a "state" store somewhere that will be passed around,...

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 1:20 PM

Yeah this

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 1:20 PM

Hono calls it context, Fastify calls it state.

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 1:20 PM

There's nothing workers-native though I don't think.

Isaac McFadyen

IIsaac McFadyen There's nothing workers-native though I don't think.

Hard@Work

H

Hard@Work•8/16/24, 1:35 PM

Isn't the "official" one

req.cf

req.cf

?

Hard@Work

H

Hard@Work•8/16/24, 1:36 PM

Like, as in, they don't guarantee that they won't put new stuff on it, but it will be passed around

Hard@Work

HHard@Work Isn't the "official" one `req.cf`?

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 1:36 PM

Yeah but that's even more likely to be overwritten.

Isaac McFadyen

I

Isaac McFadyen•8/16/24, 1:36 PM

I guess if you name your thing something obscure it'll work, but I can imagine a

req.cf.client

req.cf.client

some day for some service or another.

moody 💭

M

moody 💭•8/16/24, 4:46 PM

seem to be experiencing an outage again, with hyperdrive connection latency spikes. is there anyone available who can look into it?

AJR

A

AJR•8/16/24, 4:49 PM

Let me take a look. Same config ID you'd previously sent?

AJR

A

AJR•8/16/24, 5:09 PM

Looks 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.

AJR

AAJR Looks like the ID you'd sent previously is not seeing traffic. Please post or D...

moody 💭

M

moody 💭•8/16/24, 7:11 PM

dmd

Isaac McFadyen

IIsaac McFadyen Oh I see

Mitya

M

Mitya•8/19/24, 11:57 AM

Interesting - I've seen frameworks absolutely encourage storing things on

req

req

between middleware. Otherwise you'd have no option but to laboriously pass around manually a ton of data as function arguments.

Hard@Work

HHard@Work I think they meant if a single Request runs multiple queries across different ha...

Mitya

M

Mitya•8/19/24, 12:01 PM

Exactly.

Mitya

MMitya Interesting - I've seen frameworks absolutely encourage storing things on `req` ...

Isaac McFadyen

I

Isaac McFadyen•8/19/24, 12:15 PM

Absolutely, but there's usually a property dedicated towards it.

Isaac McFadyen

I

Isaac McFadyen•8/19/24, 12:15 PM

Like

ctx

ctx

or similar.

Ping for toast

P

Ping for toast•8/19/24, 9:47 PM

https://www.cloudflarestatus.com/incidents/035gqnkz86zh
was there possibly downtime related to this

Elevated 1xxx Error Rates

Ping for toast

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

AJR

A

AJR•8/19/24, 9:49 PM

No, not for Hyperdrive. Not that I've seen or know of.

AJR

AAJR No, not for Hyperdrive. Not that I've seen or know of.

Ping for toast

P

Ping for toast•8/19/24, 9:50 PM

odd. I know that they have the same ip pool so i was wondering because for about a minute i had connection timeouts

bs_sfalls

B

bs_sfalls•8/19/24, 11:21 PM

Seeing 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.

bs_sfalls

Bbs_sfalls Seeing an interesting problem with workers, may or may not be a result of hyperd...

Matt Silverlock

M

Matt Silverlock•8/20/24, 12:29 AM

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?

Matt Silverlock

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

bs_sfalls

B

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.

bs_sfalls

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

Ping for toast

P

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

I think its possible I'm experiencing this as well

Ping for toast

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

Ping for toast

P

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

up here

Ping for toast

P

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

started getting this error a couple days ago

Ping for toast

P

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

that looks like a bug

Ping for toast

P

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

and i suppose it is

Ping for toast

P

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

but whats interesting is

Ping for toast

P

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

P

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

CONNECT_TIMEOUT?

Ping for toast

P

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

bs_sfalls

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

Ping for toast

P

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

P

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

A

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?

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);
}

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)
}