| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Time series databases | Data platform | 2% | 9 of 66 | 58% | 12 | criticized challenger | |
| NoSQL databases | Data platform | 2% | 6 of 73 | 0% | 11 | accepted challenger | ▼−2Since September 2026: 4% → 2%, −2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Managed relational databases | Data platform | 0% | 53 of 82 | 33% | 3 | under 10 labels · led by Amazon RDS at 45% | ▼−2Since September 2026: 2% → 0%, −2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Data warehouses | Data platform | 0% | 12 of 26 | 0% | 2 | under 10 labels · led by Snowflake at 49% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| ETL and ELT | Data platform | 0% | 51 of 75 | 0% | 1 | under 10 labels · led by Fivetran at 40% | newNew since September 2026: not ranked then, 0% now. |
| Streaming platforms | Data platform | 0% | 94 of 98 | 100% | 1 | under 10 labels · led by Confluent Cloud at 39% | newNew since September 2026: not ranked then, 0% now. |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 1 | 1 | 1 | 3 |
| GPT-5.4 mini | 1 | 3 | 0 | 0 | 4 |
| Gemini 3.5 Flash | 1 | 1 | 0 | 1 | 3 |
| Perplexity Sonar | 0 | 0 | 0 | 2 | 2 |
| Grok 4.20 | 0 | 0 | 0 | 2 | 2 |
| Mistral Small | 0 | 0 | 0 | 1 | 1 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 0 | 1 |
| Llama 4 Maverick | 0 | 1 | 0 | 0 | 1 |
| Qwen 3.7 Flash | 1 | 1 | 0 | 1 | 3 |
| Kimi K2 | 0 | 1 | 1 | 0 | 2 |
| GLM 4.7 FlashX | 0 | 2 | 1 | 0 | 3 |
| MiniMax M2.5 | 0 | 1 | 1 | 0 | 2 |
| GPT-6 Luna | 0 | 1 | 0 | 0 | 1 |
| Muse Glimmer 30B | 0 | 0 | 1 | 1 | 2 |
Verbatim evidence the judge attached to positive labels.
“Start with PostgreSQL + TimescaleDB if your scale is modest. It minimizes new tooling and hiring complexity.” GPT-5.4 mini · Time series DBs · budget prompt · first choice
“Before choosing any NoSQL database, ask yourself: "Why can't I use PostgreSQL?"” Gemini 3.5 Flash · NoSQL · negative prompt · first choice
“If your data is highly normalized and relational ... stick to Postgres.” Qwen 3.7 Flash · NoSQL · scale prompt · first choice
“modern trends suggest looking at PostgreSQL (specifically with JSONB) as the ultimate hybrid solution” Qwen 3.7 Flash · NoSQL · direct prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“they are not optimized for large volumes... making them poor choices for serious time series workloads” Mistral Small · Time series DBs · negative prompt · hard negative
“Databases Posing as Event Streams ... databases are not optimized for this pattern” Gemini 3.5 Flash · Streaming · negative prompt · hard negative
“PostgreSQL, MySQL, and SQL Server are fine for *small-scale* time-series workloads, but ... they become a poor fit as ingest volume, retention, and query complexity grow.” Perplexity Sonar · Time series DBs · negative prompt · soft negative
“General-purpose databases like PostgreSQL or MySQL can handle time-series workloads at small scale, but performance degrades” Claude Haiku 4.5 · Time series DBs · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 82 of the 106 answers that named PostgreSQL and are not a share of its labels.
234 of the 234 domain citations in answers naming PostgreSQL came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| News or press | 959 | undated | |||
| Conference or event | 31 | 1 | 2026-08-07 | ||
| Comparison | 12 | 0 | 2025-11-13 | ||
| Glossary or explainer | 8 | 7 | 2026-09-24 | ||
| Report or ebook | 5 | undated | |||
| Podcast or video | 3 | 0 | 2024-07-22 |
As the event pages on postgresql.org state them, read September 28, 2026.
Every page postgresql.org exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read September 29, 2026.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What PostgreSQL's own pages state, read September 28, 2026: postgresql.org, postgresql.org/support/security, postgresql.org/download/products/1. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when PostgreSQL's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as PostgreSQL, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for PostgreSQL by email, built from the raw record of the edition. It shows: