sqlx-pool

PgPool sharing across Axum and Leptos uses State and provide_context to distribute the connection pool. You configure PgPoolOptions at startup and leverage FromRef for sub-state extraction, ensuring safe database access within server functions.

You can configure PgPoolOptions including max and min connections, acquire timeouts, idle timeouts, connection lifetime timeouts, and test_before_acquire. These settings control the lifecycle and capacity of your shared PgPool.

FromRef allows your Leptos server functions to extract the PgPool from Axum's application state. By implementing FromRef, you create sub-states that safely derive the shared pool, preventing direct coupling and ensuring Send-safety across components.

Handling Send-safety rules requires ensuring the shared PgPool works correctly across long-running tasks and async contexts. The Skill provides lifecycle guidance to maintain Send-safety, preventing runtime errors when sharing pool state across Axum handlers and Leptos components.

Yes, you can use the same PgPool for both Axum handlers and Leptos server functions. The setup automates pool construction and lifecycle-aware sharing patterns, allowing both frameworks to safely access the shared database pool without boilerplate.