Is wasm32-unknown-unknown currently a supported target for tokio-postgres?

[Jaltaire]

I see a couple other Issues reference wasm32-unknown-unknown support:

• feat: add support for wasm #1040
• Getrandom 0.3.1 #1206

though I'm not seeing how this would work due to current mio/tokio limitations...? Indeed, trying to compile with cargo build --target wasm32-unknown-unknown yields a host of mio-related errors.

Mostly sanity checking here, as I would love to use tokio-postgres within an edge computing runtime if there is something I'm missing.

[sfackler]

You need to build it without the tokio integration and hook it up to some other API providing async TCP.

https://github.com/sfackler/rust-postgres/blob/master/.github/workflows/ci.yml#L75

[Jaltaire]

Got it. As future reference for anyone who is looking, here's how this would be set up for Cloudflare Workers, for example:

• https://developers.cloudflare.com/workers/languages/rust/crates/#tokio-postgres
• https://github.com/cloudflare/workers-rs/blob/main/examples/tokio-postgres/src/lib.rs

I'm exploring setting this up with Supabase Edge Functions, but this remains a work in progress.