R-SET EQUAL float-aggregate-order
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
List out the full name and total cost that member id "rec4BLdZHS2Blfp4v" incurred?
the hint the set supplies: full name refers to first_name, last name
NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.
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 T1.first_name, T1.last_name, SUM(T2.cost) FROM member AS T1 INNER JOIN expense AS T2 ON T1.member_id = T2.link_to_member WHERE T1.member_id = 'rec4BLdZHS2Blfp4v' GROUP BY T1.first_name, T1.last_namethis statement states no ordering of its own
sha256:6376fecdfe2de0191c430a98db1db23ae8c94b2235a7101989955c2d73465c47
SELECT member.first_name, member.last_name, SUM(expense.cost) as total_cost
FROM member
JOIN expense ON member.member_id = expense.link_to_member
WHERE member.member_id = 'rec4BLdZHS2Blfp4v'
GROUP BY member.first_name, member.last_namethis statement states no ordering of its own
sha256:8322454004dc9af9071894202909c9703edfef9fc204159efe8bbd447fc59f0f
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, 0 rows, up to 25 shown per side
| side | first_nametext | last_nametext | sumfloat4 |
|---|---|---|---|
| no rows |
from counterexample.json, 0 rows, up to 25 shown per side
| side | first_nametext | last_nametext | total_costfloat4 |
|---|---|---|---|
| no rows |
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
from counterexample.json, 1 row
| first_nametext | last_nametext | sumfloat4 |
|---|---|---|
| Sacha | Harrison | 866.25006 |
from counterexample.json, 1 row
| first_nametext | last_nametext | total_costfloat4 |
|---|---|---|
| Sacha | Harrison | 866.25006 |
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"
}this statement aggregates floating point numbers, so its last digits depend on the order the rows were summed in; the values agree to six significant digits
from smells.json, 1 row
| Sacha | Harrison | 866.25 |
{
"heuristic": true,
"rule": "R-SET",
"baseline_result_hash": "sha256:6376fecdfe2de0191c430a98db1db23ae8c94b2235a7101989955c2d73465c47",
"baseline_result": {
"columns": [
{
"name": "first_name",
"declared_type": "text"
},
{
"name": "last_name",
"declared_type": "text"
},
{
"name": "sum",
"declared_type": "float4"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Sacha"
},
{
"type": "str",
"value": "Harrison"
},
{
"type": "dec",
"value": "866.25006"
}
]
],
"result_hash": "sha256:6376fecdfe2de0191c430a98db1db23ae8c94b2235a7101989955c2d73465c47"
},
"planner_statistics": {
"member": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 33
},
"expense": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 32
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"member",
"expense"
],
"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": "not_equal",
"differs": true,
"result_hash": "sha256:88fbf702d4829bf6bf75c9caf11ecbb563d6884b0a94a2597fa7458dec47ecca",
"result": {
"columns": [
{
"name": "first_name",
"declared_type": "text"
},
{
"name": "last_name",
"declared_type": "text"
},
{
"name": "sum",
"declared_type": "float4"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Sacha"
},
{
"type": "str",
"value": "Harrison"
},
{
"type": "dec",
"value": "866.25"
}
]
],
"result_hash": "sha256:88fbf702d4829bf6bf75c9caf11ecbb563d6884b0a94a2597fa7458dec47ecca"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
},
"float_cells": [
{
"row": 0,
"column": "sum",
"declared_type": "float4",
"baseline": "866.25006",
"rerun": "866.25"
}
],
"significant_digits": 6
}SELECT T1.first_name, T1.last_name, SUM(T2.cost) FROM member AS T1 INNER JOIN expense AS T2 ON T1.member_id = T2.link_to_member WHERE T1.member_id = 'rec4BLdZHS2Blfp4v' GROUP BY T1.first_name, T1.last_nameresult_hash sha256:6376fecdfe2de0191c430a98db1db23ae8c94b2235a7101989955c2d73465c47 recomputed from this JSON: match
record_hash sha256:ae06d43d07ea08a91b2a554fd616861eb13728d371dfbac9c35dd97779189b14 recomputed from this JSON: match
from evidence-gold.json, 1 row
| first_nametext | last_nametext | sumfloat4 |
|---|---|---|
| Sacha | Harrison | 866.25006 |
SELECT member.first_name, member.last_name, SUM(expense.cost) as total_cost
FROM member
JOIN expense ON member.member_id = expense.link_to_member
WHERE member.member_id = 'rec4BLdZHS2Blfp4v'
GROUP BY member.first_name, member.last_nameresult_hash sha256:8322454004dc9af9071894202909c9703edfef9fc204159efe8bbd447fc59f0f recomputed from this JSON: match
record_hash sha256:b4ae141b80fe172127c8214c5b709428c24c9aee2f54041223fcfc4e1c267349 recomputed from this JSON: match
from evidence-second.json, 1 row
| first_nametext | last_nametext | total_costfloat4 |
|---|---|---|
| Sacha | Harrison | 866.25006 |
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