R-SET NOT_EQUAL
student_club · 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 amount of the funds that the Vice President received?
the hint the set supplies: 'Vice President' is a position of Student Club; funds received refers to amount.
NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.
read by hand, 2026-09-04: C the tool's rule, not the question's: the same number as int8 against numeric or float8 against numeric
int8 against numeric (SUM), one row, value 50
a maintainer's reading of this question, out of classification.json, copied from plans/reports/prediction-mode-260904-real-predictions/classification.json. It is not a verdict and nothing above it was computed from it.
The two statements name their result columns differently. A projection is compared by position and declared type, so these names did not decide the verdict. They are part of the canonical rendering each result is hashed under, so the two result hashes differ with them.
SELECT T2.amount FROM member AS T1 INNER JOIN income AS T2 ON T1.member_id = T2.link_to_member WHERE T1.position = 'Vice President'this statement states no ordering of its own
sha256:0df8a1d044a1157cd83e4547d3fbb8c84aef8ce39843e4398cfc5ea97f42370b
SELECT SUM(income.amount) AS funds_received
FROM income
JOIN member ON income.link_to_member = member.member_id
WHERE member.position = 'Vice President'this statement states no ordering of its own
sha256:47c45b64d492e74ba696e66e7f3335e9ada04d6a0a2408f419d8d9894447b2f4
The marked tokens are where the two texts differ. Two statements that differ everywhere can return the same rows, and two that differ in one token can return other rows; the verdict above is read off the results.
from counterexample.json, 1 row, up to 25 shown per side
| side | amountint8 |
|---|---|
| gold | 50 |
from counterexample.json, 1 row, up to 25 shown per side
| side | funds_receivednumeric |
|---|---|
| second | 50 |
set(second_rows) == set(gold_rows), float4/float8 cells as Python float as psycopg2 returns them, numeric as Decimal
https://github.com/bird-bench/mini_dev/blob/main/evaluation/evaluation_ex.py
result_eq: equal row counts and equal column counts, each row unordered as a quick rejection, then the two equal as a list when the gold text holds ORDER BY and as a multiset otherwise, under some permutation of the columns; DISTINCT is not stripped and re-executed, and the cells are PostgreSQL's as psycopg2 returns them
ruiqi-zhong/test-suite-sql-eval, exec_eval.py, result_eq, at commit 48cb78ec: https://github.com/ruiqi-zhong/test-suite-sql-eval/blob/48cb78ecf7f610620206283846c76751b18a1326/exec_eval.py
The class states what makes these two results unequal under this rule, read off the two results and nothing else. It does not state which of the two statements is wrong.
from counterexample.json, 1 row
| amountint8 |
|---|
| 50 |
from counterexample.json, 1 row
| funds_receivednumeric |
|---|
| 50 |
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
the statement states no top level ORDER BY
{
"heuristic": true,
"reason": "the statement states no top level ORDER BY"
}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
the statement states no LIMIT
{
"heuristic": true,
"reason": "the statement states no LIMIT"
}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-SET",
"baseline_result_hash": "sha256:0df8a1d044a1157cd83e4547d3fbb8c84aef8ce39843e4398cfc5ea97f42370b",
"baseline_result": {
"columns": [
{
"name": "amount",
"declared_type": "int8"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "int",
"value": 50
}
]
],
"result_hash": "sha256:0df8a1d044a1157cd83e4547d3fbb8c84aef8ce39843e4398cfc5ea97f42370b"
},
"planner_statistics": {
"member": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 33
},
"income": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 36
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"member",
"income"
],
"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:0df8a1d044a1157cd83e4547d3fbb8c84aef8ce39843e4398cfc5ea97f42370b",
"result": {
"columns": [
{
"name": "amount",
"declared_type": "int8"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "int",
"value": 50
}
]
],
"result_hash": "sha256:0df8a1d044a1157cd83e4547d3fbb8c84aef8ce39843e4398cfc5ea97f42370b"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT T2.amount FROM member AS T1 INNER JOIN income AS T2 ON T1.member_id = T2.link_to_member WHERE T1.position = 'Vice President'result_hash sha256:0df8a1d044a1157cd83e4547d3fbb8c84aef8ce39843e4398cfc5ea97f42370b recomputed from this JSON: match
record_hash sha256:0c154a14fccc93761006a17beeb969f701fb02db3e47f2b4893dc6f1222fffaa recomputed from this JSON: match
from evidence-gold.json, 1 row
| amountint8 |
|---|
| 50 |
SELECT SUM(income.amount) AS funds_received
FROM income
JOIN member ON income.link_to_member = member.member_id
WHERE member.position = 'Vice President'result_hash sha256:47c45b64d492e74ba696e66e7f3335e9ada04d6a0a2408f419d8d9894447b2f4 recomputed from this JSON: match
record_hash sha256:54d31cc155540e95f0cb8ae4a843ac31c8a1704def0642ae25264ce535e4e215 recomputed from this JSON: match
from evidence-second.json, 1 row
| funds_receivednumeric |
|---|
| 50 |
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-SET
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-SET