Which Cloudflare product(s) does this pertain to? Other What versions are you using? 4.4.0 [Wrangler], 16.8 [PostgreSQL] What operating system and version are you using? Windows 10 21H2 (Wrangler) ...
Currrently we support the default curves on pg 14-17. So, ssl_ecdh_curve=prime256v1ssl_ecdh_curve=prime256v1 is supported. Assuming that's the one you mean, yes it works.
My project uses Drizzle + Hyperdrive + Neon. The last week start to appears this message: "Timed out while waiting for a message from the origin database". I think is a Hyperdrive message. Are there any place to see hyperdrive logs?
Hyperdrive is configured with the pool's connection string of Neon, is it right?
I've trierd Drizzle client with and without a PgNeon Pool --> in both cases, some time I get the error (is not deterministic) Any ideas?
Hello. Confirmed, that's a Hyperdrive error message. It is thrown when a query is sent to the origin database, but no response is received for 60 seconds.
This timeout was added about a month ago. If you are seeing it regularly, I can adjust it upwards for you in our next release. I will note that 60s is a fairly long time, so I would recommend confirming that everything is performing as expected from your origin DB before requesting this. Happy to do it, though, just let me know and please provide the Hyperdrive IDs for which you would like this increase.
If their cold starts delay responses past the 60 second mark, that could cause this, yes. I haven't personally witnessed that, but it's certainly possible in theory.
The only thing the Pool struct will do is to allow multiple parallel queries within a given Worker request. If that's something that's helpful for your use case, then I'd say go for it. Depends entirely on your situation.
The only caveat I'd add is that you want to limit it to 5 max, as it'll fail if you pass the 6 egress connection limit within a Worker request. It may deadlock, as observed by some other users in this channel.
Can you share your code or repo? Does it happen without hyperdrive (I would asssume yes)? This looks more like a code-specific issue so might make more sense in #workers-help