R-SET GOLD-ONLY 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
Calculate the difference of the total amount spent in all events by the Student_Club in year 2019 and 2020.
the hint the set supplies: The first 4 strings of the event_date values in the event table can represent year; The difference of the total amount spent = SUBTRACT(spent where YEAR(event_date) = 2019, spent where YEAR(event_date) = 2020)
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 SUM(CASE WHEN SUBSTR(T1.event_date, 1, 4) = '2019' THEN T2.spent ELSE 0 END) - SUM(CASE WHEN SUBSTR(T1.event_date, 1, 4) = '2020' THEN T2.spent ELSE 0 END) AS num FROM event AS T1 INNER JOIN budget AS T2 ON T1.event_id = T2.link_to_eventthis statement states no ordering of its own
sha256:6734b548b6e292f82a949162f990dc3457b0a19dbb79bedf2e70d2b5a2ae82a8
from evidence-gold.json, 1 row
| numfloat4 |
|---|
| 2086.05 |
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
| 2086.0498 |
{
"heuristic": true,
"rule": "R-SET",
"baseline_result_hash": "sha256:6734b548b6e292f82a949162f990dc3457b0a19dbb79bedf2e70d2b5a2ae82a8",
"baseline_result": {
"columns": [
{
"name": "num",
"declared_type": "float4"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "dec",
"value": "2086.05"
}
]
],
"result_hash": "sha256:6734b548b6e292f82a949162f990dc3457b0a19dbb79bedf2e70d2b5a2ae82a8"
},
"planner_statistics": {
"event": {
"last_analyze": "2026-09-14 12:50:59.479238+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
},
"budget": {
"last_analyze": "2026-09-14 12:50:58.001042+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"event",
"budget"
],
"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:f9dbbc43e0a5fd935001fea7dbcaf2feda58c4a1ce336678a52647d35d6bf2bf",
"result": {
"columns": [
{
"name": "num",
"declared_type": "float4"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "dec",
"value": "2086.0498"
}
]
],
"result_hash": "sha256:f9dbbc43e0a5fd935001fea7dbcaf2feda58c4a1ce336678a52647d35d6bf2bf"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
},
"float_cells": [
{
"row": 0,
"column": "num",
"declared_type": "float4",
"baseline": "2086.05",
"rerun": "2086.0498"
}
],
"significant_digits": 6
}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
{
"heuristic": true,
"rows": 1,
"distinct_rows": 1,
"repeated_rows": 0,
"largest_repeat": 1,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"not_applicable": "a result of fewer than two rows has nothing to repeat"
}SELECT SUM(CASE WHEN SUBSTR(T1.event_date, 1, 4) = '2019' THEN T2.spent ELSE 0 END) - SUM(CASE WHEN SUBSTR(T1.event_date, 1, 4) = '2020' THEN T2.spent ELSE 0 END) AS num FROM event AS T1 INNER JOIN budget AS T2 ON T1.event_id = T2.link_to_eventresult_hash sha256:6734b548b6e292f82a949162f990dc3457b0a19dbb79bedf2e70d2b5a2ae82a8 recomputed from this JSON: match
record_hash sha256:9cdef6c04306b1a33201cbbb3eb279f6b00f7f50e5dc50e604be8f2ded80b812 recomputed from this JSON: match
from evidence-gold.json, 1 row
| numfloat4 |
|---|
| 2086.05 |
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