gold
SELECT T1.DisplayName FROM users AS T1 INNER JOIN badges AS T2 ON T1.Id = T2.UserId WHERE T2.name = 'Autobiographer' ORDER BY T2.Date LIMIT 1
- t2.date
- ascending
sha256:ee5b899354aa38abbfb2efd2e0b9ff079e09e3f44a5d712fdce7903a7cc6ca0b
R-ORD GOLD-ONLY arbitrary-cut
codebase_community · mini_dev_postgresql from https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_postgresql.json
What is the display name of the user who acquired the first Autobiographer badge?
the hint the set supplies: Autobiographer is the name of the badge; acquired the first refers to MIN(Date);
This question was audited without a prediction beside it, so there is nothing to compare the gold with. The probes below read the gold alone.
SELECT T1.DisplayName FROM users AS T1 INNER JOIN badges AS T2 ON T1.Id = T2.UserId WHERE T2.name = 'Autobiographer' ORDER BY T2.Date LIMIT 1
sha256:ee5b899354aa38abbfb2efd2e0b9ff079e09e3f44a5d712fdce7903a7cc6ca0b
from evidence-gold.json, 1 row
| displaynametext |
|---|
| Geoff Dalgas |
A smell is a mechanical reason to read this gold statement again. It is a heuristic: it does not state that the statement is wrong, and a maintainer decides.
this statement orders by a text column holding only numbers, and ordering it as a number gives a different answer, so the gold may be sorting 9.5 above 10
no ORDER BY key resolves to a text column
{
"heuristic": true,
"reason": "no ORDER BY key resolves to a text column",
"keys": [
{
"key": "t2.date",
"column": "badges.date",
"declared_type": "timestamp with time zone",
"not_applicable": "the column is not declared as text"
}
]
}
this statement cuts its result at a LIMIT that does not decide which rows come back, so a different but equally correct statement can return other rows and score zero
from smells.json, 10 rows
| Geoff Dalgas | 2010-07-19T11:39:09+00:00 |
| Jarrod Dixon | 2010-07-19T11:39:09+00:00 |
| Vince | 2010-07-19T11:39:09+00:00 |
| csgillespie | 2010-07-19T11:39:09+00:00 |
| Pierre | 2010-07-19T11:39:09+00:00 |
| wahalulu | 2010-07-19T11:39:09+00:00 |
| Jin | 2010-07-19T11:39:09+00:00 |
| Sharpie | 2010-07-19T11:39:09+00:00 |
| grokus | 2010-07-19T11:39:09+00:00 |
| Noah Snyder | 2010-07-19T11:39:09+00:00 |
{
"heuristic": true,
"cut": 1,
"offset": 0,
"distinct_kept": false,
"unbounded_sql": "SELECT t1.displayname, t2.date AS attestql_ordering_key_0 FROM users t1 JOIN badges t2 ON t1.id = t2.userid WHERE t2.name = 'Autobiographer' ORDER BY t2.date",
"unbounded_rows": 4480,
"projected_columns": [
"displayname"
],
"ordering_key_columns": [
"attestql_ordering_key_0"
],
"ordering_keys": [
{
"key": "t2.date",
"direction": "asc",
"nulls": "default",
"nulls_first_in_effect": false,
"returned_rows_null_in_this_key": 0,
"fires": false
}
],
"tied_at_the_cut": {
"positions": [
0,
1,
2,
3,
4,
5,
6,
7,
8,
9
],
"tied_rows": 12,
"distinct_projected_answers": 12,
"rows": [
[
{
"type": "str",
"value": "Geoff Dalgas"
}
],
[
{
"type": "str",
"value": "Jarrod Dixon"
}
],
[
{
"type": "str",
"value": "Vince"
}
],
[
{
"type": "str",
"value": "csgillespie"
}
],
[
{
"type": "str",
"value": "Pierre"
}
],
[
{
"type": "str",
"value": "wahalulu"
}
],
[
{
"type": "str",
"value": "Jin"
}
],
[
{
"type": "str",
"value": "Sharpie"
}
],
[
{
"type": "str",
"value": "grokus"
}
],
[
{
"type": "str",
"value": "Noah Snyder"
}
]
]
},
"case": "tie-at-the-cut"
}
rerun over the same rows in another physical order this statement gives another answer, so its result depends on how the rows are stored and not only on the data
{
"heuristic": true,
"rule": "R-ORD",
"baseline_result_hash": "sha256:ee5b899354aa38abbfb2efd2e0b9ff079e09e3f44a5d712fdce7903a7cc6ca0b",
"baseline_result": {
"columns": [
{
"name": "displayname",
"declared_type": "text"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Geoff Dalgas"
}
]
],
"result_hash": "sha256:ee5b899354aa38abbfb2efd2e0b9ff079e09e3f44a5d712fdce7903a7cc6ca0b"
},
"planner_statistics": {
"users": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 40325
},
"badges": {
"last_analyze": null,
"last_autoanalyze": "2026-09-08 05:19:12.766008+00",
"n_mod_since_analyze": 0
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"users",
"badges"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"laptimes": 400524,
"legalities": 427907,
"posthistory": 303155,
"trans": 1056320,
"yearmonth": 383282
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:ee5b899354aa38abbfb2efd2e0b9ff079e09e3f44a5d712fdce7903a7cc6ca0b",
"result": {
"columns": [
{
"name": "displayname",
"declared_type": "text"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Geoff Dalgas"
}
]
],
"result_hash": "sha256:ee5b899354aa38abbfb2efd2e0b9ff079e09e3f44a5d712fdce7903a7cc6ca0b"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}
SELECT T1.DisplayName FROM users AS T1 INNER JOIN badges AS T2 ON T1.Id = T2.UserId WHERE T2.name = 'Autobiographer' ORDER BY T2.Date LIMIT 1
result_hash sha256:ee5b899354aa38abbfb2efd2e0b9ff079e09e3f44a5d712fdce7903a7cc6ca0b recomputed from this JSON: match
record_hash sha256:6fedc7d5564cfe97ddb7e53c0aeaa5c613a38f76fd2d4750a3d439a6f3d615d1 recomputed from this JSON: match
from evidence-gold.json, 1 row
| displaynametext |
|---|
| Geoff Dalgas |
re-run this statement read-only against PostgreSQL 16.15 (Debian 16.15-1.pgdg13+2) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit | server=172.17.0.2/32:5432 | database=bird under the session settings and over the data this record's fixture digest names, and compare the two results under R-ORD