launchbadge/sqlx

Pool should spawn a task when connecting in `acquire()`

Open

#3,513 建立於 2024年9月20日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Rust (13,916 star) (1,307 fork)batch import
E-mediumenhancementgood first issuepool

描述

This way, if the acquire() call is cancelled or times out, the connection can still go through.

The connection task should have its own separate timeout, possibly surfaced as PoolOptions::connect_timeout().

This will likely fix:

貢獻者指南

技術棧
rust
領域
backenddatabase
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Rustasync programmingsqlx pool internals
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Examine the current `acquire()` method in sqlx's pool module, likely in `/sqlx core/src/pool/`. Understand how connections are spawned and consider spawning a separate task with its own timeout. Reference linked issues #3315, #3132, #2848 for additional context and expected behavior.