Severe performance issue in Npgsql 10 when PGSSLROOTCERT is set to system store
维护者通常 6 天内回复
还没有人认领这个 Issue。
- #6418 来自 @某人 —— 已关闭，未合并
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 20/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- csharp, postgresql
- 领域
- databases, performance
调研方向
Start by reading commit 73202604c3d66d4b55c81d3d532bf0e78cc5c2ee and the linked pull request #6418 to understand the certificate-chain validation change and work already underway. Compare the system-store case with custom certificate files; done means avoiding the reported connection-timeout performance problem while preserving the expected validation for custom files.
由索引模型根据 Issue 内容生成。
描述
After updating from Npgsql 8 to 10, we experienced frequent database connection timeouts, and traced them to commit 73202604c3d66d4b55c81d3d532bf0e78cc5c2ee, which adds an additional certificate chain validation in case the PGSSLROOTCERT environment variable is set.
While this additional validation is expected if PGSSLROOTCERT is set to a custom file, it becomes a significant performance problem if PGSSLROOTCERT is in fact set to the system certificate store, which was the case in the environment I was operating in -- probably because in contrast to Npgsql, libpq requires PGSSLROOTCERT for certificate validation. The reason for the large performance difference is that the actual system store includes a cache, whereas the custom certificates are loaded from disk every time.
As I expect other users to run into the same problem, it would be useful if Npgsql could detect this problem and either silently use the system store or at least warn the user and instruct them to unset PGSSLROOTCERT specifically for the Npgsql-based application. I will create a PR, but unfortunately I could not find a way to ask .NET for the system store location it actually used.
- 主要语言
- C#
- 星标
- 3.7k
- 派生
- 890
- 平均合并
- 4 天 11 小时
- 30 天内合并 PR
- 19
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
npgsql/npgsql 的其他 Issue
-
Writing a decimal as numeric allocates a short[9] per value可能已有人在做 @tamasprincz97-dot 于 13 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 89/100
维护者通常 6 天内回复
-
Reading a large interval as TimeSpan returns a wrong value instead of throwing可能已有人在做 @Mr444-dev 于 7 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 6 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 6 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 6 天内回复
-
ReadReplicationSlot returns the slot name as passed, not the one the server read可能已有人在做 @Brar 于 8 天前认领。 未关闭replication
npgsql/npgsql#6735 · 已指派 1 人 ·
维护者通常 6 天内回复
相似的 Issue
-
Issue-Bug Needs-Triage
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
JiaFeiMiao-K-Cat/DiscImageStudio#281 ·
维护者通常 1 天内回复
-
area/access-management Frontend onboarding candidate :handshake:
难度 2/5 1-3 小时 新手友好度 65/100
Altinn/altinn-auth#4941 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
aws/aws-sdk-net#4586 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复