q1389

R-ORD GOLD-ONLY arbitrary-cut

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

The question

Which event has the lowest cost?

the hint the set supplies: event refers to event_name; lowest cost means MIN(cost)

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.

The statements

gold

SELECT T1.event_name FROM event AS T1 INNER JOIN budget AS T2 ON T1.event_id = T2.link_to_event INNER JOIN expense AS T3 ON T2.budget_id = T3.link_to_budget ORDER BY T3.cost NULLS FIRST LIMIT 1
t3.cost
ascending

sha256:56406324bb087daab39eca2d80eb40a285f0ba16585dc9ae96e7e4c82cf0b7c5

The results

gold, 1 row

from evidence-gold.json, 1 row

event_nametext
November Speaker

The probes

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.

ordering-over-numeric-text not applicable

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

no ORDER BY key resolves to a text column

what it measured
{
  "heuristic": true,
  "reason": "no ORDER BY key resolves to a text column",
  "keys": [
    {
      "key": "t3.cost",
      "column": "expense.cost",
      "declared_type": "real",
      "not_applicable": "the column is not declared as text"
    }
  ]
}

arbitrary-cut fired

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

from smells.json, 3 rows

September Speaker 6
November Speaker 6
October Speaker 6
what it measured
{
  "heuristic": true,
  "cut": 1,
  "offset": 0,
  "distinct_kept": false,
  "unbounded_sql": "SELECT t1.event_name, t3.cost AS attestql_ordering_key_0 FROM event t1 JOIN budget t2 ON t1.event_id = t2.link_to_event JOIN expense t3 ON t2.budget_id = t3.link_to_budget ORDER BY t3.cost NULLS FIRST",
  "unbounded_rows": 32,
  "projected_columns": [
    "event_name"
  ],
  "ordering_key_columns": [
    "attestql_ordering_key_0"
  ],
  "ordering_keys": [
    {
      "key": "t3.cost",
      "direction": "asc",
      "nulls": "first",
      "nulls_first_in_effect": true,
      "returned_rows_null_in_this_key": 0,
      "fires": false
    }
  ],
  "tied_at_the_cut": {
    "positions": [
      0,
      1,
      2
    ],
    "tied_rows": 3,
    "distinct_projected_answers": 3,
    "rows": [
      [
        {
          "type": "str",
          "value": "September Speaker"
        }
      ],
      [
        {
          "type": "str",
          "value": "November Speaker"
        }
      ],
      [
        {
          "type": "str",
          "value": "October Speaker"
        }
      ]
    ]
  },
  "case": "tie-at-the-cut"
}

not-a-function-of-the-data quiet

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

what it measured
{
  "heuristic": true,
  "rule": "R-ORD",
  "baseline_result_hash": "sha256:56406324bb087daab39eca2d80eb40a285f0ba16585dc9ae96e7e4c82cf0b7c5",
  "baseline_result": {
    "columns": [
      {
        "name": "event_name",
        "declared_type": "text"
      }
    ],
    "row_count": 1,
    "truncated": false,
    "rows_shown": 1,
    "rows": [
      [
        {
          "type": "str",
          "value": "November Speaker"
        }
      ]
    ],
    "result_hash": "sha256:56406324bb087daab39eca2d80eb40a285f0ba16585dc9ae96e7e4c82cf0b7c5"
  },
  "planner_statistics": {
    "expense": {
      "last_analyze": null,
      "last_autoanalyze": null,
      "n_mod_since_analyze": 32
    },
    "event": {
      "last_analyze": null,
      "last_autoanalyze": null,
      "n_mod_since_analyze": 42
    },
    "budget": {
      "last_analyze": null,
      "last_autoanalyze": null,
      "n_mod_since_analyze": 52
    }
  },
  "shuffle": {
    "seed": "1",
    "row_limit": 300000,
    "tables": [
      "expense",
      "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": "equal",
    "differs": false,
    "result_hash": "sha256:56406324bb087daab39eca2d80eb40a285f0ba16585dc9ae96e7e4c82cf0b7c5",
    "result": {
      "columns": [
        {
          "name": "event_name",
          "declared_type": "text"
        }
      ],
      "row_count": 1,
      "truncated": false,
      "rows_shown": 1,
      "rows": [
        [
          {
            "type": "str",
            "value": "November Speaker"
          }
        ]
      ],
      "result_hash": "sha256:56406324bb087daab39eca2d80eb40a285f0ba16585dc9ae96e7e4c82cf0b7c5"
    }
  },
  "plan_variant": {
    "run": false,
    "reason": "the plan variant was not asked for"
  }
}

The evidence records

gold: evidence-gold.json

SELECT T1.event_name FROM event AS T1 INNER JOIN budget AS T2 ON T1.event_id = T2.link_to_event INNER JOIN expense AS T3 ON T2.budget_id = T3.link_to_budget ORDER BY T3.cost NULLS FIRST LIMIT 1
statement read from
data/questions/mini_dev_postgresql.json
digest
sha256:d2731292f20b8d8569cd956dd747ffe1df13cd625076263e38ae9ebcef50b1ab
origin
https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_postgresql.json, 2024-06-19

result_hash sha256:56406324bb087daab39eca2d80eb40a285f0ba16585dc9ae96e7e4c82cf0b7c5 recomputed from this JSON: match

record_hash sha256:e4867b646f254cf7a8a78334e2c593f9fdf0dd7f853eda6c16188814e4ed63c4 recomputed from this JSON: match

the result this record holds, 1 row

from evidence-gold.json, 1 row

event_nametext
November Speaker
what ran, and where
run
audit-adbef1a5-9f41-4a8f-ac55-8c3d8df71394
executed at
2026-09-08T05:19:05.240729+00:00
data as of
2026-09-08T05:18:53.188261+00:00
backend at checkout
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
backend that answered
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
database role
auditor
replay rule
R-ORD
question set version
sha256:d2731292f20b8d8569cd956dd747ffe1df13cd625076263e38ae9ebcef50b1ab
validator
audit:libpg_query-parse
checks run
parses_as_exactly_one_statement, the_one_statement_is_a_select, no_placeholder_without_a_bound_parameter
statement timeout
30000 ms
rows
1 row
the session it ran under
engine
postgresql
time_zone
Etc/UTC
date_style
ISO, MDY
interval_style
postgres
extra_float_digits
1
database_collation
en_US.utf8
work_mem
4096
hash_mem_multiplier
2

recorded beside them

statement_timeout
0
search_path
"$user", public
server_version
16.15 (Debian 16.15-1.pgdg13+2)
server_version_num
160015
transaction_read_only
on
max_parallel_workers_per_gather
2
server_encoding
UTF8
datlocprovider
c
daticulocale
datcollversion
2.41
the rendering and the data
version
attestql/audit/2
numeric_scale
6
timestamp_format
%Y-%m-%dT%H:%M:%S.%fZ
timezone
UTC
null_rendering
NULL
encoding
utf-8
schema digest
sha256:5a015b4f8f5195c6c1534672114e29b20459d8eb295df670fac83eb79f922b60
source file sha256
sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.budget
52
rows in public.event
42
rows in public.expense
32

Running these again

gold

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-ORD

This question's run

run
audit-adbef1a5-9f41-4a8f-ac55-8c3d8df71394
server
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
question set
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
replay rule
R-ORD

the run this question belongs to

The JSON this page was rendered from