[solatic]

Cloudflare Workers doesn't offer a Postgres option. At most, there's Hyperdrive to connect to Postgres hosted elsewhere, and even then Hyperdrive is essentially a connection pooler, with all the additional restrictions that places on you.

It's also unlikely that Cloudflare will offer a true Postgres option; their whole ethos is that anything you deploy is deployed globally, whereas relational databases enforce having a single server as a definition of truth. But I'd love to be proven wrong here.

[TobyTheDog123]

You're right - I should have clarified that I'm talking about new projects - as in "Why would someone choose Postgres over one of these distributed SQLite providers for a new project?"

(I'm sure those use-cases exist, but I'm not sure if they exist inside the use-cases Supabase supports)

[solatic]

Just to take an example from my current project - Postgres has ltree for hierarchical data: https://www.postgresql.org/docs/current/ltree.html , which has no SQLite equivalent.

Postgres is simply a much more feature-ful option. Going with database-per-tenant with e.g. Cloudflare D1 (besides the fact that D1 is still in beta, technically, but that's important when we're talking about databases) is a specific architectural decision that has its own tradeoffs (like making analytics much more difficult).