Do coding agents recommend Postgres Full-Text Search?
Postgres Full-Text Search is the most chosen search engine, taking 17% of 459 judged search sessions. Measured with Claude Code, Codex and Cursor.
Postgres Full-Text Search is the most chosen search engine, taking 17% of 459 judged search sessions. It was also raised as a candidate in 42 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in search inside a realistic codebase. Not what a chat assistant says about Postgres Full-Text Search. What an agent actually installed.
The numbers
| Category | Search |
| Sessions in the category | 459 |
| Sessions where Postgres Full-Text Search was chosen | 79 |
| Install share | 17% |
| Rank in category | 1 of 16 |
| Codebases it won in | 8 |
| Raised as a candidate, not chosen | 42 |
| Chosen when considered | 65% |
| Site | postgresql.org |
By agent
The three agents land within 9 points of each other on Postgres Full-Text Search, which is closer than most products in this experiment manage.
| Agent | Sessions | Chose Postgres Full-Text Search | Share |
|---|---|---|---|
| Claude Code | 152 | 34 | 22% |
| Codex | 155 | 26 | 17% |
| Cursor | 152 | 19 | 13% |
By who was asking
Postgres Full-Text Search does much better with one kind of buyer than another. It won 35% of sessions asked as vibe coder and 9% of those asked as enterprise team.
| Who is asking | Sessions | Chose Postgres Full-Text Search | Share |
|---|---|---|---|
| Vibe coder | 65 | 23 | 35% |
| Junior developer | 193 | 19 | 10% |
| Senior engineer | 106 | 28 | 26% |
| Enterprise team | 95 | 9 | 9% |
What Postgres Full-Text Search was up against
The full ranking in search, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Built in-house (no product adopted) | 106 | 23% |
| 2 | Postgres Full-Text Search (this page) | 79 | 17% |
| 3 | OpenSearch | 59 | 13% |
| 4 | Typesense | 42 | 9% |
| 5 | Meilisearch | 40 | 9% |
| 6 | Oracle Indexed Search | 23 | 5% |
| 7 | Algolia | 23 | 5% |
| 8 | Elasticsearch | 22 | 5% |
What this means
Leading a category is a position to defend rather than a result to celebrate. In our data, leaders lose ground in exactly two situations: when the person asking is an enterprise buyer with procurement constraints, and when a competitor's documentation is easier for an agent to integrate correctly.
The defence is unglamorous. Keep the quickstart running. Keep the version current on the page. Keep the names aligned. Stay in the templates.
Where these numbers come from
The 459 sessions in search are part of a published set of 5,292, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every search run can be replayed on the board.
If you work on Postgres Full-Text Search: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Postgres Full-Text Search?
Yes. Postgres Full-Text Search was chosen in 79 of the 459 judged sessions in search, a 17% install share, ranking first in its category.
Does Claude Code recommend Postgres Full-Text Search?
In 34 of the 152 sessions in search run with Claude Code, which is 22%.
Do different coding agents treat Postgres Full-Text Search differently?
Not much. The three agents chose it at similar rates, between 13% and 22% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 51 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Postgres Full-Text Search considered but not chosen?
It was raised as a candidate in 42 sessions without being chosen, and chosen in 79. That is a 65% conversion from considered to chosen.
Where this comes from
Armature ran 5,292 judged sessions with Claude Code, Codex and Cursor inside 51 realistic codebases, and published every run. The numbers on this page come from that work.