Compatibility: preserve root cause on connection timeouts with PG16 parameters
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The issue names no file, function or test. Start by reproducing the problem with a multi-host PostgreSQL DSN that uses target_session_attrs or sslnegotiation, and find where the connection fallback loop catches and re-raises errors. Done would mean the original timeout is chained or preserved in the traceback, which the maintainers would need to agree on first, since the expected behaviour is not yet specified.
由索引模型根据 Issue 内容生成。
描述
Hi everyone,
While working with PostgreSQL 16 multi-host DSNs that utilize newer connection parameters like target_session_attrs or sslnegotiation, we noticed that fallback connection attempts can sometimes obscure the original root cause during network timeouts. This can occasionally make diagnosing connectivity issues in clustered environments a bit trickier than necessary.
Environment
- Python 3.12
- Linux / Ubuntu 22.04
- OCA/rest-framework (current main)
- psycopg / psycopg2 (PostgreSQL 16 connection handling)
Steps to Reproduce
- Configure a multi-host PostgreSQL DSN in Odoo utilizing
target_session_attrs=read-writeorsslnegotiation=direct. - Simulate a network timeout or unreachable primary node where fallback logic is triggered.
- Observe the resulting exception traceback.
Expected Behavior
The underlying root cause and original timeout exception should be preserved or clearly chained in the traceback to facilitate faster debugging.
Actual Behavior
The original network timeout context can sometimes be swallowed during the fallback iteration across connection attempts.
Happy to submit a quick PR for this if the maintainers are open to it!
Reported by Usman Ghias · Senior Systems & Backend Architect · Open for Select Senior Remote & Consulting Roles
- 主要语言
- Python
- 星标
- 385
- 派生
- 393
- 平均合并
- 4 天 22 小时
- 30 天内合并 PR
- 21
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
OCA/rest-framework 的其他 Issue
-
bug stale
难度 1/5 1 小时以内 新手友好度 72/100
OCA/rest-framework#612 · 4 条评论 ·
维护者通常 1 天内回复
-
help wanted no stale work in progress
难度 4/5 3-5 天 新手友好度 35/100
OCA/rest-framework#648 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 12/100
OCA/rest-framework#621 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 25/100
OCA/rest-framework#617 · 2 条评论 ·
维护者通常 1 天内回复
-
Migration to version 19.0可能已有人在做 @Churnika-Chaudhari 于 22 天前认领。 未关闭help wanted no stale work in progress
难度 4/5 3-5 天 新手友好度 25/100
OCA/rest-framework#567 · 3 条评论 ·
维护者通常 1 天内回复
查看 OCA/rest-framework 的全部 Issue
相似的 Issue
-
documentation type/bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 65/100
StevenBlack/hosts#3299 ·
-
`garak --report` overwrites the input report when its name has no ".report"可能已有人在做 @0z5a 今天认领。 未关闭needs-triage
难度 2/5 半天 新手友好度 72/100
维护者通常 2 天内回复
-
trace: Pi's 1-hour cache writes are priced at 1.25x, but billed at 2x可能已有人在做 @Shizoqua 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
microsoft/TokenEconomizer#221 ·
维护者通常 1 天内回复
-
plot_graph crashes when a mesh node has no m2m edge可能已有人在做 @tygvi 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
mllam/neural-lam#883 · 1 条评论 ·
维护者通常 2 天内回复