workers-help
pages-help
general-help
durable-objects
workers-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
⚡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows-beta
Just wondering if anyone is experiencing
Pgjs perf investigation
{ "prepare": true }
I get 100% cache misses on a simple SELECT like const [user]: [User?] = await sql`SELECT * FROM users WHERE id = ${userId}
;. If I set { “prepare”: false }
then latency improves,...There is any list that I can use to
I am not sure if this fix should happen
remix vite:build
to succeed in CI.
I think this should be fixed in Cloudflare (it should detect that it is running in the CI and not fail with the "when running locally" message)...Aha, got it working, for anyone who runs
compatibility_flags = [ "nodejs_compat" ]
in wrangler.toml
and then normal functions directory just works™. It took me a while to figure it out because most of the community resources, gh issues etc are slightly outdated and took me a while to understand that node_compat = true
is a build time thing not supported by pages and likely won't be (as it is legacy) and compatibility_flags
is...Why does query latency fluctuate so much
I use postgres.js (latest version 3.4.4
CONNECTION_CLOSED
Disabling the hyperdrive cache didn't help and I can't find any open issue on that topic in the postgres.js repo. Am I the only one?Appointments
@thomasgauvin I am using AWS lambda
1. Depends on your use case. There's
Hyperdrive Untrusted IP Address Space
While waiting for Cloudflare Tunnel
What's the recommended way to build a
Error: When developing locally, you should use a local Postgres connection string to emulate Hyperdrive functionality. Please setup Postgres locally and set the value of the 'WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_HYPERDRIVE' variable or "HYPERDRIVE"'s "localConnectionString" to the Postgres connection string.
Error: When developing locally, you should use a local Postgres connection string to emulate Hyperdrive functionality. Please setup Postgres locally and set the value of the 'WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_HYPERDRIVE' variable or "HYPERDRIVE"'s "localConnectionString" to the Postgres connection string.
Postgres.js with default settings doesn'
prepare: false
when setting up your connection with postgres.js to help ameliorate some of the performance penalty....Hi @AutumnCicada! What database are you
Hyperdrive bindings exist in the Pages
hyperdrive_bindings
. You won't be able to use the pg
driver, but you can use the Postgres.js driver which only requires the compat flag nodejs_compat
(not old node_compat
) and it works 🙂Postgres-js Distributed Performance
prepare: false
- ? (that's going to slow things down!)
- Don't define timeouts or lifetimes.
- Have you tried the pg
driver? We've noticed issues with Postgres.js and working with the maintainer to figure out why...Heroku Postgres SSL Errors