R-SET NOT_EQUAL
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
User No.23853 gave a comment to a post at 9:08:18 on 2013/7/12, was that post well-finished?
the hint the set supplies: user no. 23853 refers to UserId = '23853'; at 9:08:18 on 2013/7/12 refers to CreationDate = '2013-07-12 09:08:18.0'; not well-finished refers to ClosedDate IS NULL and vice versa
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: A a wrong answer the benchmark credited: another table or projection; a scalar repeated per row of an unrelated table; a list at least twice the answer's length where the question asks for the things, not the rows
both results are empty on this data; the prediction projects (title, closeddate) or a bool, not the well-finished label the question asks for
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 CASE WHEN T2.ClosedDate IS NULL THEN 'NOT well-finished' ELSE 'well-finished' END AS resylt FROM comments AS T1 INNER JOIN posts AS T2 ON T1.PostId = T2.Id WHERE T1.UserId = 23853 AND T1.CreationDate = '2013-07-12 09:08:18.0'this statement states no ordering of its own
sha256:78952fa973a58f7a521b8615137e217e1abd3f6d05e7b1d03eae6fbbfdef25ce
SELECT p.title, p.closeddate
FROM posts p
JOIN comments c ON p.id = c.postid
JOIN users u ON c.userid = u.id
WHERE u.id = 23853
AND c.creationdate = '2013-07-12 09:08:18.0';this statement states no ordering of its own
sha256:a4f15ef1a700b87e8b27c1839eac5bcc08f31cb43feaab001e6a135b82085bdc
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 | resylttext |
|---|---|
| no rows |
from counterexample.json, 0 rows, up to 25 shown per side
| side | titletext | closeddatetimestamptz |
|---|---|---|
| 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
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, 0 rows
| resylttext |
|---|
| no rows |
from counterexample.json, 0 rows
| titletext | closeddatetimestamptz |
|---|---|
| no rows |
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:78952fa973a58f7a521b8615137e217e1abd3f6d05e7b1d03eae6fbbfdef25ce",
"baseline_result": {
"columns": [
{
"name": "resylt",
"declared_type": "text"
}
],
"row_count": 0,
"truncated": false,
"rows_shown": 0,
"rows": [],
"result_hash": "sha256:78952fa973a58f7a521b8615137e217e1abd3f6d05e7b1d03eae6fbbfdef25ce"
},
"planner_statistics": {
"comments": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 174285
},
"posts": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 91966
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"comments",
"posts"
],
"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:78952fa973a58f7a521b8615137e217e1abd3f6d05e7b1d03eae6fbbfdef25ce",
"result": {
"columns": [
{
"name": "resylt",
"declared_type": "text"
}
],
"row_count": 0,
"truncated": false,
"rows_shown": 0,
"rows": [],
"result_hash": "sha256:78952fa973a58f7a521b8615137e217e1abd3f6d05e7b1d03eae6fbbfdef25ce"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT CASE WHEN T2.ClosedDate IS NULL THEN 'NOT well-finished' ELSE 'well-finished' END AS resylt FROM comments AS T1 INNER JOIN posts AS T2 ON T1.PostId = T2.Id WHERE T1.UserId = 23853 AND T1.CreationDate = '2013-07-12 09:08:18.0'result_hash sha256:78952fa973a58f7a521b8615137e217e1abd3f6d05e7b1d03eae6fbbfdef25ce recomputed from this JSON: match
record_hash sha256:0b108f22890b73417ab135c7f14b5743cc5858a3ace59669ccd8a50bbe39ac0d recomputed from this JSON: match
from evidence-gold.json, 0 rows
| resylttext |
|---|
| no rows |
SELECT p.title, p.closeddate
FROM posts p
JOIN comments c ON p.id = c.postid
JOIN users u ON c.userid = u.id
WHERE u.id = 23853
AND c.creationdate = '2013-07-12 09:08:18.0';result_hash sha256:a4f15ef1a700b87e8b27c1839eac5bcc08f31cb43feaab001e6a135b82085bdc recomputed from this JSON: match
record_hash sha256:d1d9b7f1f9fdde63945ea4b712a850e8c8559e6afa5b428eb491963d1a5a1982 recomputed from this JSON: match
from evidence-second.json, 0 rows
| titletext | closeddatetimestamptz |
|---|---|
| no rows |
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