R-SET EQUAL duplicate-full-row
superhero · 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 publisher for Hawkman, Karate Kid and Speedy?
the hint the set supplies: publisher refers to publisher_name; Hawkman refers to superhero_name = 'Hawkman'; Karate Kid refers to superhero_name = 'Karate Kid'; Speedy refers to superhero_name = 'Speedy';
NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.
SELECT T2.publisher_name FROM superhero AS T1 INNER JOIN publisher AS T2 ON T1.publisher_id = T2.id WHERE T1.superhero_name IN ('Hawkman', 'Karate Kid', 'Speedy')this statement states no ordering of its own
sha256:566ae52ae5672bc1be5efe845d1c67e1e4937d609806994dbb0fb0a86f4072f9
SELECT publisher.publisher_name
FROM superhero
JOIN publisher ON superhero.publisher_id = publisher.id
WHERE superhero.superhero_name IN ('Hawkman', 'Karate Kid', 'Speedy')this statement states no ordering of its own
sha256:566ae52ae5672bc1be5efe845d1c67e1e4937d609806994dbb0fb0a86f4072f9
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 | publisher_nametext |
|---|---|
| no rows |
from counterexample.json, 0 rows, up to 25 shown per side
| side | publisher_nametext |
|---|---|
| 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, 3 rows
| publisher_nametext |
|---|
| DC Comics |
| DC Comics |
| DC Comics |
from counterexample.json, 3 rows
| publisher_nametext |
|---|
| DC Comics |
| DC Comics |
| DC Comics |
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:566ae52ae5672bc1be5efe845d1c67e1e4937d609806994dbb0fb0a86f4072f9",
"baseline_result": {
"columns": [
{
"name": "publisher_name",
"declared_type": "text"
}
],
"row_count": 3,
"truncated": false,
"rows_shown": 3,
"rows": [
[
{
"type": "str",
"value": "DC Comics"
}
],
[
{
"type": "str",
"value": "DC Comics"
}
],
[
{
"type": "str",
"value": "DC Comics"
}
]
],
"result_hash": "sha256:566ae52ae5672bc1be5efe845d1c67e1e4937d609806994dbb0fb0a86f4072f9"
},
"planner_statistics": {
"superhero": {
"last_analyze": "2026-09-14 12:51:04.622816+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
},
"publisher": {
"last_analyze": "2026-09-14 12:51:04.380226+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"superhero",
"publisher"
],
"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:566ae52ae5672bc1be5efe845d1c67e1e4937d609806994dbb0fb0a86f4072f9",
"result": {
"columns": [
{
"name": "publisher_name",
"declared_type": "text"
}
],
"row_count": 3,
"truncated": false,
"rows_shown": 3,
"rows": [
[
{
"type": "str",
"value": "DC Comics"
}
],
[
{
"type": "str",
"value": "DC Comics"
}
],
[
{
"type": "str",
"value": "DC Comics"
}
]
],
"result_hash": "sha256:566ae52ae5672bc1be5efe845d1c67e1e4937d609806994dbb0fb0a86f4072f9"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}this statement returns the same whole row more than once and never says DISTINCT, so a statement answering the same question once per row disagrees on multiplicity alone
from smells.json, 1 row
| DC Comics |
{
"heuristic": true,
"rows": 3,
"distinct_rows": 1,
"repeated_rows": 1,
"largest_repeat": 3,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
3
]
}SELECT T2.publisher_name FROM superhero AS T1 INNER JOIN publisher AS T2 ON T1.publisher_id = T2.id WHERE T1.superhero_name IN ('Hawkman', 'Karate Kid', 'Speedy')result_hash sha256:566ae52ae5672bc1be5efe845d1c67e1e4937d609806994dbb0fb0a86f4072f9 recomputed from this JSON: match
record_hash sha256:9bd9b2238327212022670dd56745e1a185f79549a3135a9b447e989a1ab91a78 recomputed from this JSON: match
from evidence-gold.json, 3 rows
| publisher_nametext |
|---|
| DC Comics |
| DC Comics |
| DC Comics |
SELECT publisher.publisher_name
FROM superhero
JOIN publisher ON superhero.publisher_id = publisher.id
WHERE superhero.superhero_name IN ('Hawkman', 'Karate Kid', 'Speedy')result_hash sha256:566ae52ae5672bc1be5efe845d1c67e1e4937d609806994dbb0fb0a86f4072f9 recomputed from this JSON: match
record_hash sha256:188a060c9c4ad910942f52578ff835ae06b4905fc250dc569e92c70b2cc5699c recomputed from this JSON: match
from evidence-second.json, 3 rows
| publisher_nametext |
|---|
| DC Comics |
| DC Comics |
| DC Comics |
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