R-SET GOLD-ONLY duplicate-full-row
student_club · mini_dev_pg-00000-of-00001 from https://huggingface.co/datasets/birdsql/bird_mini_dev/resolve/f65faf4ae3b638c1fa6df1d3370c8d92c8366301/data/mini_dev_pg-00000-of-00001.json (commit f65faf4a, downloaded 2026-09-14)
Among the events attended by more than 10 members of the Student_Club, how many of them are meetings?
the hint the set supplies: meetings events refers to type = 'Meeting'; attended by more than 10 members refers to COUNT(event_id) > 10
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 COUNT(DISTINCT T1.event_id) FROM event AS T1 INNER JOIN attendance AS T2 ON T1.event_id = T2.link_to_event WHERE T1.type = 'Meeting' GROUP BY T1.event_id HAVING COUNT(T2.link_to_event) > 10this statement states no ordering of its own
sha256:78ce3502e5b0666d54d01bc15fb296a847f9f899ef820ca4b2a52c6df2a61f40
from evidence-gold.json, 4 rows
| countint8 |
|---|
| 1 |
| 1 |
| 1 |
| 1 |
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:78ce3502e5b0666d54d01bc15fb296a847f9f899ef820ca4b2a52c6df2a61f40",
"baseline_result": {
"columns": [
{
"name": "count",
"declared_type": "int8"
}
],
"row_count": 4,
"truncated": false,
"rows_shown": 4,
"rows": [
[
{
"type": "int",
"value": 1
}
],
[
{
"type": "int",
"value": 1
}
],
[
{
"type": "int",
"value": 1
}
],
[
{
"type": "int",
"value": 1
}
]
],
"result_hash": "sha256:78ce3502e5b0666d54d01bc15fb296a847f9f899ef820ca4b2a52c6df2a61f40"
},
"planner_statistics": {
"event": {
"last_analyze": "2026-09-14 12:50:59.479238+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
},
"attendance": {
"last_analyze": "2026-09-14 12:50:57.969365+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"event",
"attendance"
],
"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:78ce3502e5b0666d54d01bc15fb296a847f9f899ef820ca4b2a52c6df2a61f40",
"result": {
"columns": [
{
"name": "count",
"declared_type": "int8"
}
],
"row_count": 4,
"truncated": false,
"rows_shown": 4,
"rows": [
[
{
"type": "int",
"value": 1
}
],
[
{
"type": "int",
"value": 1
}
],
[
{
"type": "int",
"value": 1
}
],
[
{
"type": "int",
"value": 1
}
]
],
"result_hash": "sha256:78ce3502e5b0666d54d01bc15fb296a847f9f899ef820ca4b2a52c6df2a61f40"
}
},
"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
| 1 |
{
"heuristic": true,
"rows": 4,
"distinct_rows": 1,
"repeated_rows": 1,
"largest_repeat": 4,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
4
]
}SELECT COUNT(DISTINCT T1.event_id) FROM event AS T1 INNER JOIN attendance AS T2 ON T1.event_id = T2.link_to_event WHERE T1.type = 'Meeting' GROUP BY T1.event_id HAVING COUNT(T2.link_to_event) > 10result_hash sha256:78ce3502e5b0666d54d01bc15fb296a847f9f899ef820ca4b2a52c6df2a61f40 recomputed from this JSON: match
record_hash sha256:a4c99a59e020df64ed5a4728f6020d801e5b13363bd3fe6992439547a9407c5d recomputed from this JSON: match
from evidence-gold.json, 4 rows
| countint8 |
|---|
| 1 |
| 1 |
| 1 |
| 1 |
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