R-SET GOLD-ONLY duplicate-full-row
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
State all the tags used by Mark Meckes in his posts that doesn't have comments.
the hint the set supplies: used by Mark Meckes refers to DisplayName = 'Mark Meckes'; Doen't have comments refers to CommentCount = 0;
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 T3.Tags FROM users AS T1 INNER JOIN postHistory AS T2 ON T1.Id = T2.UserId INNER JOIN posts AS T3 ON T3.Id = T2.PostId WHERE T1.DisplayName = 'Mark Meckes' AND T3.CommentCount = 0this statement states no ordering of its own
sha256:b70d38466401cf5554459703bc706014c89881781745d2ed48fa9175a2d0f8f6
from evidence-gold.json, 5 rows
| tagstext |
|---|
| NULL null |
| <books> str |
| <books> str |
| <books> str |
| <books> str |
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:b70d38466401cf5554459703bc706014c89881781745d2ed48fa9175a2d0f8f6",
"baseline_result": {
"columns": [
{
"name": "tags",
"declared_type": "text"
}
],
"row_count": 5,
"truncated": false,
"rows_shown": 5,
"rows": [
[
{
"type": "null",
"value": null
}
],
[
{
"type": "str",
"value": "<books>"
}
],
[
{
"type": "str",
"value": "<books>"
}
],
[
{
"type": "str",
"value": "<books>"
}
],
[
{
"type": "str",
"value": "<books>"
}
]
],
"result_hash": "sha256:b70d38466401cf5554459703bc706014c89881781745d2ed48fa9175a2d0f8f6"
},
"planner_statistics": {
"posts": {
"last_analyze": "2026-09-14 12:51:04.210618+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
},
"users": {
"last_analyze": "2026-09-14 12:51:05.229441+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
},
"posthistory": {
"last_analyze": "2026-09-14 12:51:04.043991+00",
"last_autoanalyze": null,
"n_mod_since_analyze": 0
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"posts",
"users",
"posthistory"
],
"tables_not_shuffled": [
"posthistory"
],
"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:a68cd7099981910b1867675987e3efee910a62e919f5116dd63fffc2549de609",
"result": {
"columns": [
{
"name": "tags",
"declared_type": "text"
}
],
"row_count": 5,
"truncated": false,
"rows_shown": 5,
"rows": [
[
{
"type": "str",
"value": "<books>"
}
],
[
{
"type": "str",
"value": "<books>"
}
],
[
{
"type": "str",
"value": "<books>"
}
],
[
{
"type": "str",
"value": "<books>"
}
],
[
{
"type": "null",
"value": null
}
]
],
"result_hash": "sha256:a68cd7099981910b1867675987e3efee910a62e919f5116dd63fffc2549de609"
}
},
"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
| <books> |
{
"heuristic": true,
"rows": 5,
"distinct_rows": 2,
"repeated_rows": 1,
"largest_repeat": 4,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
4
]
}SELECT T3.Tags FROM users AS T1 INNER JOIN postHistory AS T2 ON T1.Id = T2.UserId INNER JOIN posts AS T3 ON T3.Id = T2.PostId WHERE T1.DisplayName = 'Mark Meckes' AND T3.CommentCount = 0result_hash sha256:b70d38466401cf5554459703bc706014c89881781745d2ed48fa9175a2d0f8f6 recomputed from this JSON: match
record_hash sha256:5e08bd07451d14659278241ae1a7cd7fb59bc10251d39ead816f23a4c0225fb8 recomputed from this JSON: match
from evidence-gold.json, 5 rows
| tagstext |
|---|
| NULL null |
| <books> str |
| <books> str |
| <books> str |
| <books> str |
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