From a quick look at the reasons they provide for choosing `node-postgres`: > With node-postgres, y

Tthomasgauvin Hey folks! We're working on docs to better document how to use Drizzle (Postgres...

I

Nice! Only thing I can see here is that it might be a good idea to set the connection limit on the Postgres connection so it doesn't exceed 6 and deadlock the Worker (as discovered by James)

I

Isaac McFadyenOP•5/1/25, 4:55 PM

// Clean up the connection
ctx.waitUntil(sql.end());

Also, AJR explained why this was a good idea a while back, but might be good to add a line claryfing this in the docs because people might generally assume it's bad practice to close connections on every request.

IIsaac McFadyen From a quick look at the reasons they provide for choosing `node-postgres`: > W...

T

thomasgauvin•5/1/25, 4:57 PM

We actually have had some conversations with the maintainer of Postgres.js. Since the node compat improvements on Workers, node-postgres is just as valid of a choice, and it's actually faster when you need to fetch the types from Postgres so we may change that recommendation https://developers.cloudflare.com/hyperdrive/examples/connect-to-postgres/#postgresjs

Tthomasgauvin We actually have had some conversations with the maintainer of Postgres.js. Sinc...

I

Isaac McFadyenOP•5/1/25, 4:58 PM

Makes sense! I also see that doc has the

max

max

max

max set to 5, so just porting that to the new docs would be good

T

thomasgauvin•5/1/25, 4:59 PM

I'll add a note for Postgres.js vs node-postgres to the drizzle docs, and I'll look into the configurable max connections

Tthomasgauvin Hey folks! We're working on docs to better document how to use Drizzle (Postgres...

M

marsoleg•5/1/25, 5:47 PM

This can be useful in productive environments where developers do not have direct access to the database from their local computers:

name: Deploy App

on:
  push:
    branches: main

permissions:
  contents: read

jobs:
  deploy:
    runs-on: self-hosted
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          fetch-depth: 1

      - name: Install dependencies
        run: npm ci

      - name: Check DB migrations
        run: |
          output=$(npx drizzle-kit generate)
          echo "$output"
          if ! echo "$output" | grep -q "No schema changes, nothing to migrate"; then
            echo; echo "Error: Schema changes detected. Please generate migrations before deploying."
            exit 1
          fi

      - name: Apply DB migrations
        env:
          DATABASE_URL: ${{ secrets.DATABASE_URL }}
        run: npx drizzle-kit migrate

      - name: Deploy application to Cloudflare
        env:
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
        run: npx wrangler deploy

name: Deploy App

on:
  push:
    branches: main

permissions:
  contents: read

jobs:
  deploy:
    runs-on: self-hosted
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          fetch-depth: 1

      - name: Install dependencies
        run: npm ci

      - name: Check DB migrations
        run: |
          output=$(npx drizzle-kit generate)
          echo "$output"
          if ! echo "$output" | grep -q "No schema changes, nothing to migrate"; then
            echo; echo "Error: Schema changes detected. Please generate migrations before deploying."
            exit 1
          fi

      - name: Apply DB migrations
        env:
          DATABASE_URL: ${{ secrets.DATABASE_URL }}
        run: npx drizzle-kit migrate

      - name: Deploy application to Cloudflare
        env:
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
        run: npx wrangler deploy

name: Deploy App

on:
  push:
    branches: main

permissions:
  contents: read

jobs:
  deploy:
    runs-on: self-hosted
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          fetch-depth: 1

      - name: Install dependencies
        run: npm ci

      - name: Check DB migrations
        run: |
          output=$(npx drizzle-kit generate)
          echo "$output"
          if ! echo "$output" | grep -q "No schema changes, nothing to migrate"; then
            echo; echo "Error: Schema changes detected. Please generate migrations before deploying."
            exit 1
          fi

      - name: Apply DB migrations
        env:
          DATABASE_URL: ${{ secrets.DATABASE_URL }}
        run: npx drizzle-kit migrate

      - name: Deploy application to Cloudflare
        env:
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
        run: npx wrangler deploy

name: Deploy App

on:
  push:
    branches: main

permissions:
  contents: read

jobs:
  deploy:
    runs-on: self-hosted
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          fetch-depth: 1

      - name: Install dependencies
        run: npm ci

      - name: Check DB migrations
        run: |
          output=$(npx drizzle-kit generate)
          echo "$output"
          if ! echo "$output" | grep -q "No schema changes, nothing to migrate"; then
            echo; echo "Error: Schema changes detected. Please generate migrations before deploying."
            exit 1
          fi

      - name: Apply DB migrations
        env:
          DATABASE_URL: ${{ secrets.DATABASE_URL }}
        run: npx drizzle-kit migrate

      - name: Deploy application to Cloudflare
        env:
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
        run: npx wrangler deploy

Tthomasgauvin I'll add a note for Postgres.js vs node-postgres to the drizzle docs, and I'll l...

J

James•5/1/25, 10:14 PM

+1 on the max_connections recommendation, this is a mitigation for https://github.com/cloudflare/workerd/issues/3514, at least until https://github.com/porsager/postgres/issues/1023 is resolved. Otherwise the drizzle docs look great and are essentially what we use in production today

AAJR I don't believe anyone is doing that, no. We haven't tested it, though some bri...

D

darkpool•5/2/25, 6:22 PM

Hi AJR I see that hyperdrive now supports GoogleSQL and some distributed SQL DBs. Im assuming Spanner still wont work with hyperdrive since I don't see it on the list? Im also assuming it wont work bc spanner does not provide a traditional connection string with host and port name but just wanted to confirm.

Ddarkpool Hi AJR I see that hyperdrive now supports GoogleSQL and some distributed SQL DBs...

A

AJR•5/2/25, 6:27 PM

I'm afraid that's correct, yes.

AAJR I'm afraid that's correct, yes.

D

darkpool•5/2/25, 6:35 PM

Thank you. Is there a recommended way to connect to google cloud resources in workers? Right now Im just creating and signing JWTs using a service account. I found this article but it’s a few years old so just wondering if there's a better way.

Ddarkpool Thank you. Is there a recommended way to connect to google cloud resources in wo...

A

AJR•5/2/25, 6:55 PM

Do you mean specifically GCP SQL? There's this: https://developers.cloudflare.com/hyperdrive/examples/connect-to-postgres/google-cloud-sql/

edit: I do notice that that still has you allowlisting 0.0.0.0, when now you can instead allowlist just the Cloudflare IP ranges

Cloudflare Docs

Google Cloud SQL

Connect Hyperdrive to a Google Cloud SQL for Postgres database instance.

AAJR Do you mean specifically GCP SQL? There's this: https://developers.cloudflare.c...

D

darkpool•5/2/25, 7:02 PM

I don't think that will work with Spanner since step 2 of the link is asking for a connection string like:

postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name

postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name

postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name

postgres://USERNAME:PASSWORD@HOSTNAME_OR_IP_ADDRESS:PORT/database_name
which spanner does not provide. I was asking more so if there's a recommended way if hyperdrive does not work.

Ddarkpool I don't think that will work with Spanner since step 2 of the link is asking for...

A

AJR•5/2/25, 7:34 PM

Ah, I see. Not that I'm aware of, I'm afraid. You might have better success asking in a more general Workers channel.

AAJR Ah, I see. Not that I'm aware of, I'm afraid. You might have better success a...

D

darkpool•5/2/25, 7:39 PM

Thank you.

W

William•5/4/25, 12:01 PM

Hi, everyone
I have a question with Hyperdrive. On this page: https://developers.cloudflare.com/hyperdrive/platform/limits/

As many hosted databases have limits on the number of unique connections they can manage, Hyperdrive attempts to keep number of concurrent pooled connections to your origin database lower.

How does Hyperdrive know the connection limit of my database? What does keep number of concurrent pooled connections to your origin database lower. means? lower than what?

Cloudflare Docs

Limits

The following limits apply to Hyperdrive configuration, connections, and queries made to your configured origin databases.

WWilliam Hi, everyone I have a question with Hyperdrive. On this page: https://developers...

A

AJR•5/4/25, 1:37 PM

That is a bit of an odd way to phrase it, I suppose.

Hyperdrive is a tx-mode connection pooler. It will agressively reuse connections, only opening a new one if a query arrives needing one and none of the currently open ones are available.

We currently have a soft limit of 60 connections to a pool, though can adjust that on request.

Hope that helps, please feel free to ask if you have any other questions!

AAJR That is a bit of an odd way to phrase it, I suppose. Hyperdrive is a tx-mode co...

W

William•5/4/25, 2:24 PM

Assume that users of my website may come from around the world, including North America, South America, Europe, Africa, and Asia.
This means there could be 5 Hyperdrive connection pools active at the same time:

Pool1: North America
Pool2: South America
Pool3: Europe
Pool4: Africa
Pool5: Asia

I'm using a Postgres database, and let's say the maximum allowed number of connections to my database is 80.

I saw in the documentation that for the Paid Plan, the "Maximum potential origin database connections" is approximately ~100 connections.

So, with these 5 connection pools combined, will the total number of connections to my database be limited to below 80, or below 100?

WWilliam Assume that users of my website may come from around the world, including North ...

A

AJR•5/4/25, 2:28 PM

We refactored our architecture, there'll be only a single pool near wherever your database is hosted, capped to 60.

We prioritize availability over enforcing this limit, so if the system is stressed your traffic may spill to a second pool, which would be 120 total.

Edit: I see the bit I'm missing.

No, Hyperdrive does not currently consider the maximum connection GUC on your origin database.

WWilliam Assume that users of my website may come from around the world, including North ...

A

AJR•5/4/25, 2:29 PM

We go into some detail on this here, if you're curious: https://blog.cloudflare.com/it-it/how-hyperdrive-speeds-up-database-access/#better-faster-smarter-closer

Il blog di Cloudflare

Pools across the sea: how Hyperdrive speeds up access to databases ...

Hyperdrive, Cloudflare's global connection pooler, relies on some key innovations to make your database connections work. We go deep into the details of what that looks like, in celebration of announcing its availability for Free Plan customers.

AAJR We refactored our architecture, there'll be only a single pool near wherever you...

W

William•5/4/25, 2:58 PM

I got it, thanks very much!

S

shay•5/4/25, 6:08 PM

i'm suddenly seeing what i believe to be increased connections from hyperdrive to my postgres server (there are many pg processes each using very little cpu), which is now pegging my server to 100% cpu usage, and that manifests in numerous "PostgresError: Timed out while waiting for an open slot in the pool." as well as CONNECTION_CLOSED errors in my logs. i don't think my traffic has increased proportionally to cause this--i've never noticed sustained CPU usage like this before and my daily requests are about what they've been for the past few weeks. what could be causing this? do i just need to scale up my server?

while writing this i'm noticing a few dips down into the 30-70% range which is more reasonable but the sustained highs are still concerning to me

O

oritwoen•5/5/25, 1:28 PM

Is this features will be available in the future?

https://developers.cloudflare.com/hyperdrive/reference/supported-databases-and-features/#unsupported-mysql-features

Ooritwoen Is this features will be available in the future? https://developers.cloudflare...

A

AJR•5/5/25, 1:29 PM

Some of them might be, depending on user needs. Which ones in particular would you be interested in?

AAJR Some of them might be, depending on user needs. Which ones in particular would ...

O

oritwoen•5/5/25, 1:30 PM

Non utf8 characters ;D

A

AJR•5/5/25, 1:31 PM

Heheh. I'll have to float that by our product folks. CC @thomasgauvin

Candidly I would consider that to not be a high priority right now, given the other things on our plate. I'll see what the team has to say, though.

T

thomasgauvin•5/5/25, 4:28 PM

Hey folks! We're actively talking to teams who are building cross-cloud apps to make sure that we shape Workers VPC (https://blog.cloudflare.com/workers-virtual-private-cloud/) to fit your specific needs. I figured I'd float the opportunity to this channel because I know lots of y'all are using Hyperdrive with Cloudflare tunnels and might be interested in how we're planning on making this more broadly available across Workers. If anyone wants to meet to chat about this, these are my availabilities: https://calendar.app.google/mJma67uLuf4n65Hq6

U

UB•5/5/25, 4:52 PM

I've mentioned it before but it'd still be really nice to have tls support when using local hyperdrive, so we can connect to IE: a planetscale db using local hyperdrive

U

UB•5/5/25, 4:54 PM

Currently this isn't possible because planetscale enforces tls, and doing:

const connection = await mysql.createConnection({
    host: host,
    user: username,
    password: password,
    database: database,
    port: port,
    disableEval: true,
    connectTimeout: 1000,
    ssl: {
        rejectUnauthorized: true,
    }
});

const connection = await mysql.createConnection({
    host: host,
    user: username,
    password: password,
    database: database,
    port: port,
    disableEval: true,
    connectTimeout: 1000,
    ssl: {
        rejectUnauthorized: true,
    }
});

const connection = await mysql.createConnection({
    host: host,
    user: username,
    password: password,
    database: database,
    port: port,
    disableEval: true,
    connectTimeout: 1000,
    ssl: {
        rejectUnauthorized: true,
    }
});

const connection = await mysql.createConnection({
    host: host,
    user: username,
    password: password,
    database: database,
    port: port,
    disableEval: true,
    connectTimeout: 1000,
    ssl: {
        rejectUnauthorized: true,
    }
});

Causes an infinite halt for some unknown reason

T

thomasgauvin•5/5/25, 5:07 PM

Thanks, we're aware of this and have it on our backlog, unfortunately, there are some runtime specific implementations specific to Hyperdrive that make this more complex that regular bindings but we're continuing to make progress on this and will update the discord when it's available

U

UB•5/5/25, 5:19 PM

Do you have a tracking issue on GitHub?

C

CanRau•5/10/25, 3:06 AM

Hi Hyperdrivers

Trying to use Hyperdrive with Planetscale & Kysely I've came across a couple questions and my first try just didn't work, no error, though haven't debugged anything so far, just disabled for the moment, so now to my questions:

Should I use the
```
Optimized Host
```
Optimized Host
```
Optimized Host
```
Optimized Host
:
```
aws.connect.psdb.cloud
```
aws.connect.psdb.cloud
```
aws.connect.psdb.cloud
```
aws.connect.psdb.cloud
or
```
Direct
```
Direct
```
Direct
```
Direct
which in my case is
```
eu-central.connect.psdb.cloud
```
eu-central.connect.psdb.cloud
```
eu-central.connect.psdb.cloud
```
eu-central.connect.psdb.cloud
Creating a Hyperdrive connection does test the connection settings, right? asking because pscale gives me the connection string with
```
?ssl={"rejectUnauthorized":true}
```
?ssl={"rejectUnauthorized":true}
```
?ssl={"rejectUnauthorized":true}
```
?ssl={"rejectUnauthorized":true}
at the end, should I keep it?
The Hyperdrive docs use
```
import { createConnection } from "mysql2/promise";
```
import { createConnection } from "mysql2/promise";
```
import { createConnection } from "mysql2/promise";
```
import { createConnection } from "mysql2/promise";
whereas kysely says
```
import { createPool } from 'mysql2' // do not use 'mysql2/promises'!
```
import { createPool } from 'mysql2' // do not use 'mysql2/promises'!
```
import { createPool } from 'mysql2' // do not use 'mysql2/promises'!
```
import { createPool } from 'mysql2' // do not use 'mysql2/promises'!
(https://www.kysely.dev/docs/getting-started?package-manager=pnpm&dialect=mysql#instantiation
What's the recommended
```
connectionLimit
```
connectionLimit
```
connectionLimit
```
connectionLimit
? Default in kysely docs is 10
think that's it for now also nice weekend to y'all

CCanRau Hi Hyperdrivers 🚗 💨 Trying to use Hyperdrive with Planetscale & Kysely I've ca...

I

Isaac McFadyenOP•5/10/25, 3:28 AM

Probably direct, because Hyperdrive will handle global routing for you and using the
```
Optimized Host
```
Optimized Host
```
Optimized Host
```
Optimized Host
will likely just add a layer of complexity since they'll be trying to also handle global routing.
It does test connection settings, yes.
You probably don't need a pool because Hyperdrive does pooling for you, so the
```
createConnection
```
createConnection
```
createConnection
```
createConnection
is correct. Note that because of the way Hyperdrive works, it's safe and recommended to create a new connection on every request (and terminate the connection after each request using
```
ctx.waitUntil
```
ctx.waitUntil
```
ctx.waitUntil
```
ctx.waitUntil
).
5 connections is the maximum, anything after that can result in deadlocking the Worker (not sure if the
```
createConnection
```
createConnection
```
createConnection
```
createConnection
even has a
```
connectionLimit
```
connectionLimit
```
connectionLimit
```
connectionLimit
param because it's not pooling anyway...)

IIsaac McFadyen 1. Probably direct, because Hyperdrive will handle global routing for you and us...

C

CanRau•5/10/25, 3:38 AM

hmm unfortunately kysely's

MysqlDialect

MysqlDialect

MysqlDialect

MysqlDialect only supports

pool

pool

pool

pool connection it seems

CCanRau hmm unfortunately kysely's `MysqlDialect` only supports `pool` connection it see...

I

Isaac McFadyenOP•5/10/25, 3:41 AM

Hmmm alright, it's probably fine as long as you keep it below 5 connections.

K

knickish•5/12/25, 5:27 PM

Version 5.4.0 of the Cloudflare Terraform Provider has been released. This update includes support for Hyperdrives with the MySQL database type, as well as Custom CA and mTLS support

https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.4.0

.

.gwapes•5/14/25, 4:01 PM

I am using hyperdrive and I just want to clarify something. I'm using hono and then using the variables to set my db. Do I need to use ctx.waitUntil(sql.end()) or is it not 100% neccessary?

app.all("*", async (c, next) => {
    const sql = postgres(c.env.database.connectionString, {
        max: 5,
        fetch_types: false
    });

    const db = drizzle(sql);

    c.set("database", db);

    await next()
})

app.all("*", async (c, next) => {
    const sql = postgres(c.env.database.connectionString, {
        max: 5,
        fetch_types: false
    });

    const db = drizzle(sql);

    c.set("database", db);

    await next()
})

app.all("*", async (c, next) => {
    const sql = postgres(c.env.database.connectionString, {
        max: 5,
        fetch_types: false
    });

    const db = drizzle(sql);

    c.set("database", db);

    await next()
})

app.all("*", async (c, next) => {
    const sql = postgres(c.env.database.connectionString, {
        max: 5,
        fetch_types: false
    });

    const db = drizzle(sql);

    c.set("database", db);

    await next()
})

..gwapes I am using hyperdrive and I just want to clarify something. I'm using hono and t...

A

AJR•5/14/25, 6:07 PM

It is not strictly necessary, though would be preferred when possible.

AAJR It is not strictly necessary, though would be preferred when possible.

.

.gwapes•5/14/25, 6:11 PM

I added a

c.executionCtx.waitUntil(sql.end())

c.executionCtx.waitUntil(sql.end())

c.executionCtx.waitUntil(sql.end())

c.executionCtx.waitUntil(sql.end())

But then got an error that the client was closed or something before the request finished. I can get it again if you would want to see it

How necessary is it to close? What implications does it have if you don't

A

AJR•5/14/25, 6:13 PM

We'll hold the connection open until it times out Idle or the Worker itself disconnects, so it's just a bit of increased resource. Not the end of the world, but at a high enough scale or with particularly long-lived Workers/connections it may pile up enough to start slowing down your requests.

AAJR We'll hold the connection open until it times out Idle or the Worker itself disc...

.

.gwapes•5/14/25, 6:15 PM

Ok that makes sense, I remember reading the docs about that type of thing. Where would I add the c.executionCtx.waitUntil(sql.end()) to prevent the client being closed before the request completes?

..gwapes Ok that makes sense, I remember reading the docs about that type of thing. Where...

A

AJR•5/14/25, 6:16 PM

Just at the end of your fetch handler, as late as possible in the Worker's control flow.

Y

Yashu Mittal•5/24/25, 5:37 PM

I want to confirm if I understand this correctly, before i make a mistake by exposing the db publicly.

I have a db running on third-party cloud provider, along with a

cloudflared

cloudflared

cloudflared

cloudflared container in the same network.
Now, from this docs: https://developers.cloudflare.com/hyperdrive/configuration/connect-to-private-database/#12-connect-your-database-using-a-public-hostname

I need to create a public hostname

<random_name>.<my_domain>.com/

<random_name>.<my_domain>.com/

<random_name>.<my_domain>.com/

<random_name>.<my_domain>.com/
and point it to db

mysq://...

mysq://...

mysq://...

mysq://... with TCP type

Question:

If I link my db to make it accessible publicity via endpoint wouldn't anyone access it?
Do I need to enter the db username and password in type TCP url as well?

When I create a hyperdrive configuration, I can see it does ask for the db name, username and password.
Does that mean, that I do not have to add username, password and db name in the tcp url?

A

AJR•5/26/25, 12:36 AM

We can do it for you on request, please feel free to DM.

Making this self-service is a known feature gap, and we do plan to address it. However we have not prioritized it onto our roadmap for the upcoming few months. We do not yet have a committed timeline for when we will deliver this feature.

K

kindaraffy•5/26/25, 12:55 PM

Does anybody else have issues with their drizzle transaction's being complete cache misses? I know hyperdrive struggles to cache transactions, but my transactions are completely independent queries (I have a root transaction carrying individual, child transactions. It's these child transactions I'm expecting to be cached). I'm using

postgres.js

postgres.js

and

{prepare: true}

{prepare: true}

{prepare: true}

{prepare: true}. Are transactions known not to work with hyperdrive at all?

I wanted to create a reproducible repo, but I wanted to see if anybody else had this problem.

A

AJR•5/26/25, 1:51 PM

We do not cache any queries conducted within a transaction, by design.

That said, Hyperdrive should be perfectly capable of handling transactions, with all the state correctly handled throughout.

Are you having any issues with things besides caching?

A

AJR•5/26/25, 1:56 PM

As an aside, I genuinely wish the Postgres wire protocol had commit/rollback status encoded into its ReadyForQuery messages. It would make caching tx queries so much less risky.

D

Dylan•5/27/25, 2:05 AM

hello everyone,

i'm having this error that I haven't quite know how to solve yet. it's related to using neon with postgres.js and hyperdrive
i'm trying to set up a connection as follows:

import { Context } from 'hono';
import postgres from 'postgres';

const db = (c: Context) => {
  console.log('Connecting to database...');
  console.log(c.env.HYPERDRIVE.connectionString);

  const connectionString = c.env.HYPERDRIVE?.connectionString;

  return postgres(connectionString, {
    fetch_types: false
  });
};

export default db;

import { Context } from 'hono';
import postgres from 'postgres';

const db = (c: Context) => {
  console.log('Connecting to database...');
  console.log(c.env.HYPERDRIVE.connectionString);

  const connectionString = c.env.HYPERDRIVE?.connectionString;

  return postgres(connectionString, {
    fetch_types: false
  });
};

export default db;

import { Context } from 'hono';
import postgres from 'postgres';

const db = (c: Context) => {
  console.log('Connecting to database...');
  console.log(c.env.HYPERDRIVE.connectionString);

  const connectionString = c.env.HYPERDRIVE?.connectionString;

  return postgres(connectionString, {
    fetch_types: false
  });
};

export default db;

import { Context } from 'hono';
import postgres from 'postgres';

const db = (c: Context) => {
  console.log('Connecting to database...');
  console.log(c.env.HYPERDRIVE.connectionString);

  const connectionString = c.env.HYPERDRIVE?.connectionString;

  return postgres(connectionString, {
    fetch_types: false
  });
};

export default db;

but this is the output that I'm getting in the console:

Connecting to database...
postgresql://neondb_owner:*************@91a7****************d1e4c29.hyperdrive.local:5432/neondb?sslmode=disable
✘ [ERROR] PostgresError: connection is insecure (try using `sslmode=require`)

Connecting to database...
postgresql://neondb_owner:*************@91a7****************d1e4c29.hyperdrive.local:5432/neondb?sslmode=disable
✘ [ERROR] PostgresError: connection is insecure (try using `sslmode=require`)

Connecting to database...
postgresql://neondb_owner:*************@91a7****************d1e4c29.hyperdrive.local:5432/neondb?sslmode=disable
✘ [ERROR] PostgresError: connection is insecure (try using `sslmode=require`)

Connecting to database...
postgresql://neondb_owner:*************@91a7****************d1e4c29.hyperdrive.local:5432/neondb?sslmode=disable
✘ [ERROR] PostgresError: connection is insecure (try using `sslmode=require`)

i'm not sure what I'm supposed to do since the url provided by hyperdrive has sslmode=false.
can anyone point me in the right direction?

AAJR Local dev mode (i.e. `wrangler dev`) does not currently support connecting to re...

D

Dylan•5/27/25, 2:36 AM

oooh this explains it, shouldve joined the discord server sooner.

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote works perfectly

From a quick look at the reasons they provide for choosing `node-postgres`: > With node-postgres, y

Similar Threads

Similar Threads

Similar Threads