postgres/postgres
GitHub release · Unknown version
Latest collection: unavailable. No verified release declaration is available. This does not mean the project has no releases or platform support.
Is postgres/postgres the successor of mysql/mysql-server?
postgres/postgres subject · successor candidate successor of? mysql/mysql-server object · predecessor
postgres-mysql · status observed
Data verified at: 2026-09-11T16:51:48Z (UTC)
Conclusion status
No confirmed conclusion exists for this pair. The evidence below is presented for transparency; a relationship conclusion requires a human review that has not happened, or a previous decision no longer matches the current evidence.
No directional succession or fork claim was found; the current evidence does not establish the researched relationship.
Seed context: Negative research question: same domain (RDBMS), no lineage claim is expected.
Observed repository facts
As of the last verified collection. These are facts about the snapshots, not activity verdicts — a low number is not a claim that a project is inactive.
| Endpoint | Repo | Stars | Last push | Fork | Archived |
|---|---|---|---|---|---|
| postgres/postgres | postgres/postgres | 22071 | 2026-09-11T16:00:49Z | no | no |
| mysql/mysql-server | mysql/mysql-server | 12423 | 2026-09-11T13:29:44Z | no | no |
Versions & deployment facts
Official release and package declarations, compared independently of the relationship verdict. These are not installation tests or a migration guarantee. Missing declarations mean unknown.
mysql/mysql-server
GitHub release · Unknown version
Latest collection: unavailable. No verified release declaration is available. This does not mean the project has no releases or platform support.
Timeline
“Event time” is an upstream timestamp when the source provides one; “first observed” is when this project saw it. They are deliberately separate columns.
| Event | Event time | First observed | Source |
|---|---|---|---|
| mysql/mysql-server metadata first observed | — | 2026-09-11T16:49:19Z | link |
| recent commit activity of mysql/mysql-server observed (5 commits in sampled window) | 2026-09-01T22:12:06Z | 2026-09-11T16:49:22Z | link |
| postgres/postgres metadata first observed | — | 2026-09-11T16:51:48Z | link |
| recent commit activity of postgres/postgres observed (5 commits in sampled window) | 2026-09-11T15:43:11Z | 2026-09-11T16:51:50Z | link |
| automatic evaluation -> insufficient_data | — | 2026-09-11T16:53:25Z | — |
| automatic evaluation -> insufficient_data | — | 2026-09-11T16:58:19Z | — |
| automatic evaluation -> insufficient_data | — | 2026-09-12T02:55:35Z | — |
| automatic evaluation -> insufficient_data | — | 2026-09-12T02:57:05Z | — |
| automatic evaluation -> insufficient_data | — | 2026-09-12T02:59:28Z | — |
Decision and dispute history
Review decisions are recorded privately with reasons that stay internal; this public history shows what happened and when, not why.
| Kind | When (UTC) |
|---|---|
| automatic evaluation → insufficient_data | 2026-09-11T16:53:25Z |
| automatic evaluation → insufficient_data | 2026-09-11T16:58:19Z |
| automatic evaluation → insufficient_data | 2026-09-12T02:55:35Z |
| automatic evaluation → insufficient_data | 2026-09-12T02:57:05Z |
| automatic evaluation → insufficient_data | 2026-09-12T02:59:28Z |
To question this report, use the feedback form,
select “data error”, and include pair ID postgres-mysql.
Feedback is reviewed privately and does not change a report automatically.
Snapshot taken at 2026-09-16T13:11:39.533Z (UTC).