[Feature] graphman should automatically run ANALYZE after creating indexes

未关闭
#5,185 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
postgres, rust
领域
cli, databases

调研方向

首先追踪 graphman 的索引创建流程以及它如何执行 PostgreSQL 操作。确定索引创建后应在何处运行 ANALYZE，包括多个索引针对同一张表时的行为；完成的标准是，在不干扰索引创建的情况下始终收集最新统计信息。

由索引模型根据 Issue 内容生成。

描述

enhancement indexer experience ops Stale
Description

When creating multicolumn indexes, a subsequent ANALYZE is needed so that Postgres collects the necessary statistics and makes the freshly created index available for the query planner. Therefore, it's a good idea to teach graphman to automatically run ANALYZE after such index creations.

What's more, it also seems to be a good idea to always run ANALYZE after any index creation - after all, we create indexes to address performance issues, and fresh statistics (obtained by ANALYZE) also often help with such problems. This will make the implementation easier as a side effect, I believe.

An optional sub-feature might be the ability to turn it off when creating multiple indexes one after another on the same table. We have to consider here that index creation usually takes several minutes, whereas a typical ANALYZE finishes somewhere between 4 and 15 seconds.

Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out
  • Tick this box if you plan on implementing this feature yourself.
  • I have searched the issue tracker to make sure this issue is not a duplicate.
主要语言
Rust
星标
3.2k
派生
1.1k
平均合并
4 天 1 小时
30 天内合并 PR
1

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

graphprotocol/graph-node 的其他 Issue

查看 graphprotocol/graph-node 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。