> **Result** > <table> > <tr> > <td width="25%"><img src="assets/ex_result.png"></td> > <td>Represents a constant result set or a 'no-op' node. It evaluates expressions that do not require scanning a table, such as a standalone <code>SELECT 1</code> or a <code>VALUES</code> list. It is often used as a dummy node in more complex structures to bridge gaps in the execution tree.</td> > </tr> > </table> > > ```sql > -- A simple constant result > EXPLAIN (ANALYZE, COSTS, BUFFERS, VERBOSE) > SELECT 1; > ``` > >  > > <!-- literal-explain-plan > Captured EXPLAIN provenance for the adjacent reader-facing visual plan. > Canonical capture metadata lives in scratch/actual_operation_plans.json. > > Result (cost=0.00..0.01 rows=1 width=4) (actual time=0.000..0.001 rows=1 loops=1) > Output: 1 > Planning: > Buffers: shared hit=3 > Planning Time: 0.025 ms > Execution Time: 0.012 ms > --> > > > <!-- > Raw-capture provenance — separate run. > SQL, setup, dataset, settings, and scope: artifacts/chapter4_capture_matrix.json. > Target: PostgreSQL 18.x companion fixture. Cache state: uncontrolled. > Boundary: pg_wait_tracer backend execution root; client states are included when the chart shows them. > Fidelity: exact pg_wait_tracer export. Not the adjacent EXPLAIN run; compare state shape, not durations. > --> > >  > > <table> > <tr> > <td rowspan="2" width="25%"><img src="assets/ex_result.svg"></td> > <td><b>Performance</b></td><td>Near-zero overhead; typically used for <code>VALUES</code> lists, constant <code>SELECT</code> statements, or as a dummy node in more complex structures.</td> > </tr> > <tr><td><b>Cost</b></td><td><code>Constant cost.</code></td></tr> > </table>