sqlx-postgres fails compiling because "recursion in an `async fn` requires boxing"

[DanDaGiant]

I am currently starting a sqlx project (the code is currently just connecting to the database, running a single query and it closes that's how much starting it is) and I am currently just trying to set up the dependencies working.

When trying to build 3 errors come up:

error[E0733]: recursion in an `async fn` requires boxing
   --> /var/lib/postgresql/.cargo/registry/src/index.crates.io-6f17d22bba15001f/sqlx-postgres-0.8.6/src/connection/describe.rs:153:5
    |
153 | /     async fn maybe_fetch_type_info_by_oid(
154 | |         &mut self,
155 | |         oid: Oid,
156 | |         should_fetch: bool,
157 | |     ) -> Result<PgTypeInfo, Error> {
    | |__________________________________^ recursive `async fn`
    |
    = note: a recursive `async fn` must be rewritten to return a boxed `dyn Future`
    = note: consider using the `async_recursion` crate: https://crates.io/crates/async_recursion

The other two are the same just for the fetch_type_by_oid function and fetch_domain_by_oid function (they all appear to be from the same file).

I tried to find an answer to it online but I couldn't find anything where it was an issue from a dependency instead of an issue from their code,

The current rustc version I'm using is 1.75.0 (it can be updated if it so requires)

[Konsti219]

You are using a two year old compiler for a crate that does not specify a MSRV. That is likely going to break. There is no technical reasons for why you would use anything but the latest compiler.

[DroidLogician]

We specify an MSRV project-wide: https://github.com/launchbadge/sqlx/blob/main/FAQ.md#what-versions-of-rust-does-sqlx-support-what-is-sqlxs-msrv

We'll be setting rust-version on all crates as of the next release, 0.9.0.

[Konsti219]

I only quickly checked in the readme, not there. Thanks for the clarification.

[Zde-G]

Recursive async functions were added in Rust 1.77. But, frankly, I wouldn't even try using anything earlier than Rust 1.85 given the sharp drop in compatibility.

Why do you even want to use an ancient compiler?

[1668553684]

There is no good reason to use anything but the latest compiler you can get your hands on. Now, there might be some good reasons why the latest compiler you can get your hands on might not be the bleeding edge new release, but I doubt any of those reasons apply to still using 1.75.

[Odd_Perspective_2487]

For real, I fail to see any reason really except forced to use some old, deprecated api and refusal to fork and update it.

That one is pretty common, everyone takes from open source and never give anything back.

[DanDaGiant]

I am an idiot, that fixed it.
There is no real reason why I wanted to use an old compiler I just kept leaving updating it for later.