/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

pingcap/tidb

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T15:49:05.111Z

1mo ago

pingcap/tidb

TiDB is an active, widely adopted open-source distributed SQL database project with strong community traction and ongoing development. It targets cloud-native deployments and emphasizes high availability, horizontal and vertical scaling, strong consistency, HTAP, and MySQL compatibility.

Loading tags...

Stars39,903

Forks6,164

Default branchmaster

Last pushed2026-03-30T15:35:58Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you need its custom test/metrics/tooling stack or its specialized SQL internals. If you want a production TiDB deployment with maximum upstream compatibility and supportability, upstream is the safer choice.

Prefer upstream unless you specifically need a 2019 TiDB snapshot. This fork is far behind and looks unsuitable for production adoption except as a legacy compatibility or debugging baseline.

Prefer this fork only if you want a near-upstream TiDB mirror. If you need new capabilities or the newest fixes, upstream is the better choice.

Prefer this fork only if you need Shopify-specific TiDB behavior, test tooling, or operational controls and are prepared to maintain a large upstream gap. If you want the broadest compatibility, fastest access to bug fixes, and lowest long-term maintenance cost, upstream TiDB is the safer default.

Choose this fork only if you specifically need its custom testing and internal workflow additions and are prepared to own a large, stale divergence from upstream. For general production use, upstream TiDB is the safer default.

Prefer upstream unless you specifically need this fork's testing/tooling customizations and can tolerate major drift. For most adopters, the staleness and divergence outweigh the added workflows.

Prefer this fork only if you need its custom local changes and can absorb long-term merge debt. For most adopters, upstream TiDB is the better choice because this fork is far behind and operationally risky.

Prefer the upstream TiDB unless you specifically need the fork’s custom parser/binlog/metrics/workflow changes and are willing to own a stale, highly divergent codebase.

Prefer upstream TiDB unless you specifically need this fork’s old local experiments or test scaffolding. The fork is materially stale and highly divergent, so adoption is only sensible for users willing to own long-term maintenance and restore missing upstream capabilities.

Prefer this fork only if you need its specific 2019-era customizations and testing workflow. For most adopters, upstream TiDB is the better choice because this fork is stale and substantially behind.

Fork comparison

windtalker/tidb

70/100

active

significant_divergence

Prefer this fork only if you need its custom test/metrics/tooling stack or its specialized SQL internals. If you want a production TiDB deployment with maximum upstream compatibility and supportability, upstream is the safer choice.

Likely purpose

A custom TiDB distribution used to validate planner/parser behavior, stabilize tests, and adapt observability and DDL internals for a specialized environment.

Best for

Teams that need a TiDB variant for internal testing, benchmarking, or compatibility experiments.; Operators who want custom observability and validation workflows more than upstream fidelity.; Engineers debugging planner, parser, or DDL behavior in a specialized deployment.; Users comfortable maintaining a large downstream fork and periodically reconciling with upstream.

Additional features

Expanded test infrastructure and fixtures, including planner case-test data and LLM-oriented test data.
Custom observability and metrics dashboards, including next-generation Grafana JSON and keyspace-aware metrics.
Internal tooling for database validation and replay-style workflows, suggested by the added agent skill directories for failpoint testing, real TiKV runs, integration-test recording, and diff triage.
Broader parser, planner, and DDL rewrites that suggest support for specialized SQL behavior or internal compatibility changes.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.

Missing features

Material upstream progress after the fork point, including recent planner, executor, storage, and test-stability fixes.
Some upstream observability and dashboard assets appear removed or replaced, such as `tidb_worker` and `tidb_with_keyspace_name` dashboards in the diff facts.
Upstream test coverage appears partially dropped or reorganized, including deleted LLM test fixtures.
Because the fork is far behind upstream, it likely lacks many accumulated compatibility, correctness, and maintenance fixes from the upstream TiDB line.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream operational features such as auth, admin, or session handling may be reduced or absent.

Strengths

Very large surface-area customization across parser, planner, DDL, metrics, and tests.
Recent push activity suggests it is still being maintained.
The fork appears tuned for deep validation and observability rather than just a source mirror.

Risks

High merge burden due to extreme divergence from upstream.
Adopting it means inheriting a fork that may lag upstream bug fixes and compatibility work.
Large test and metrics rewrites increase the chance of environment-specific behavior that is hard to upstream or maintain.
The absence of a clear upstream tracking position makes long-term support uncertain.