neonctl 2.22.2 → 2.23.0

package/psql/command/cmd_pipeline.js

@@ -0,0 +1,1141 @@
+/**
+ * psql pipeline / extended-query backslash commands (WP-21).
+ *
+ * Implements the subset of upstream psql's "pipeline mode" backslash commands
+ * that drive the extended protocol directly. These are typically used together
+ * with the existing `\g` flow: a `\bind` (or `\parse`) command stashes
+ * parameter / statement state on the {@link BackslashContext}'s settings via
+ * a Symbol-keyed slot; when the mainloop then sees a `;` (or a `\g`), it can
+ * notice the stashed state and route the query through
+ * `Connection.query(sql, params)` instead of `execSimple`.
+ *
+ * Because the mainloop integration is owned by other WPs (and was deliberately
+ * left untouched here), this module exposes both the command specs AND a
+ * small helper, {@link getPipelineState}, that the mainloop will use to
+ * consult the stashed state. The commands operate on the buffered query the
+ * same way `\g` does — they execute or queue the buffer and reset it.
+ *
+ * Commands shipped:
+ *
+ *   \bind [VALUE ...]        stash params for next ; / \g
+ *   \bind_named NAME [V ...] stash params + named prepared statement
+ *   \parse NAME              prepare current query buffer as NAME
+ *   \close_prepared NAME     Close('S', NAME)
+ *   \startpipeline           begin a pipeline session (settings.sendMode)
+ *   \endpipeline             end the pipeline session, drain results
+ *   \syncpipeline            send Sync mid-pipeline
+ *   \sendpipeline            submit the current buffered query w/o waiting
+ *   \flushrequest            send Flush
+ *   \flush                   alias for \flushrequest
+ *   \getresults [N]          drain pending pipeline results
+ *   \gdesc                   describe-without-execute the buffered query
+ *
+ * The set is registered in bulk via {@link registerPipelineCommands}.
+ */
+import { writeErr } from './shared.js';
+import { alignedPrinter } from '../print/aligned.js';
+import { clearPipelineGateErrors } from './cmd_io.js';
+// ---------------------------------------------------------------------------
+// Settings stash. We can't add new fields to PsqlSettings (frozen WP-00) so
+// we attach Symbol-keyed state.
+// ---------------------------------------------------------------------------
+const BIND_STATE_KEY = Symbol.for('neonctl.psql.bindState');
+const PIPELINE_KEY = Symbol.for('neonctl.psql.pipeline');
+const PREPARED_BY_NAME_KEY = Symbol.for('neonctl.psql.preparedByName');
+const stashOf = (settings) => settings;
+/** Read (and clear) the pending bind params, if any. */
+export const consumeBindState = (settings) => {
+    const s = stashOf(settings);
+    const cur = s[BIND_STATE_KEY] ?? null;
+    s[BIND_STATE_KEY] = undefined;
+    return cur;
+};
+/**
+ * Peek at the bind stash without consuming. Used by `\g` to decide
+ * whether to skip the "empty buffer, no prior query" no-op guard:
+ * when a `\bind_named NAME` is pending, the prepared statement carries
+ * the SQL server-side so no buffer text is needed.
+ */
+export const stagedNamedBindPresent = (settings) => {
+    const cur = stashOf(settings)[BIND_STATE_KEY];
+    return !!cur && cur.byName;
+};
+/** Stash a PreparedStatement for later `\bind_named NAME \g` lookup. */
+export const stashPrepared = (settings, name, ps) => {
+    const s = stashOf(settings);
+    let map = s[PREPARED_BY_NAME_KEY];
+    if (!map) {
+        map = new Map();
+        s[PREPARED_BY_NAME_KEY] = map;
+    }
+    map.set(name, ps);
+};
+/** Look up a previously-stashed PreparedStatement by name. */
+export const lookupPrepared = (settings, name) => {
+    const map = stashOf(settings)[PREPARED_BY_NAME_KEY];
+    return map?.get(name) ?? null;
+};
+/** Drop a stashed PreparedStatement (after `\close_prepared`). */
+export const dropPrepared = (settings, name) => {
+    const map = stashOf(settings)[PREPARED_BY_NAME_KEY];
+    if (map)
+        map.delete(name);
+};
+/** Peek at the current pipeline session (or null). */
+export const getPipelineState = (settings) => stashOf(settings)[PIPELINE_KEY] ?? null;
+// ---------------------------------------------------------------------------
+// PIPELINE_* counter book-keeping.
+//
+// Upstream psql 18 exposes three pipeline counters as `:VAR`-interpolatable
+// session variables (initialized to "0" in `settings.ts` at startup):
+//
+//   PIPELINE_COMMAND_COUNT  number of P/B/E batches queued since last Sync
+//   PIPELINE_SYNC_COUNT     number of Syncs issued in the current pipeline
+//   PIPELINE_RESULT_COUNT   results queued server-side but not yet fetched
+//
+// The counter rules (verified empirically against vanilla psql 18.4):
+//
+//   \startpipeline    — all three reset to "0".
+//   \parse            — COMMAND_COUNT++.
+//   \sendpipeline     — COMMAND_COUNT++.
+//   ;-query in pipeline mode — COMMAND_COUNT++ (each implicit-`;` send).
+//   \syncpipeline     — SYNC_COUNT++, RESULT_COUNT += COMMAND_COUNT,
+//                       COMMAND_COUNT = 0.
+//   \flushrequest /
+//   \flush            — RESULT_COUNT += COMMAND_COUNT, COMMAND_COUNT = 0.
+//   \getresults [N]   — RESULT_COUNT -= actually-drained; if RESULT_COUNT
+//                       hits 0, SYNC_COUNT also resets to 0 (full-drain
+//                       returns the pipeline to a clean slate).
+//   \endpipeline      — all three reset to "0".
+//
+// For `;`-queries the increment fires from a wrapper installed around the
+// stashed `Pipeline.execute` in `cmdStartPipeline.run` — mainloop's
+// `dispatchSendQuery` calls `ps.session.parse/bind/execute` directly, and
+// the wrapper picks that up without mainloop having to know about the var
+// store.
+// ---------------------------------------------------------------------------
+const readCounter = (settings, name) => {
+    const raw = settings.vars.get(name);
+    if (raw === undefined)
+        return 0;
+    const n = parseInt(raw, 10);
+    return Number.isFinite(n) && n >= 0 ? n : 0;
+};
+const setCounter = (settings, name, value) => {
+    settings.vars.set(name, String(Math.max(0, value)));
+};
+const bumpCounter = (settings, name, delta) => {
+    setCounter(settings, name, readCounter(settings, name) + delta);
+};
+const resetPipelineCounters = (settings) => {
+    setCounter(settings, 'PIPELINE_COMMAND_COUNT', 0);
+    setCounter(settings, 'PIPELINE_SYNC_COUNT', 0);
+    setCounter(settings, 'PIPELINE_RESULT_COUNT', 0);
+};
+/**
+ * Wrap `Pipeline.execute` so each enqueued Execute message bumps
+ * `PIPELINE_COMMAND_COUNT`. The wrapping covers both call sites:
+ *
+ *  - `cmdSendPipeline` (this file) — `\sendpipeline`.
+ *  - `dispatchSendQuery` (mainloop) — implicit `;`-queries while pipeline
+ *    is active. Mainloop calls `ps.session.execute('', 0)` so the wrapper
+ *    fires automatically without mainloop knowing about the var store.
+ *
+ * The wrapper preserves the original function's `this` binding via `apply`.
+ */
+const wrapSessionForCounters = (session, settings) => {
+    const origExecute = session.execute.bind(session);
+    session.execute = (name, maxRows) => {
+        bumpCounter(settings, 'PIPELINE_COMMAND_COUNT', 1);
+        return origExecute(name, maxRows);
+    };
+    return session;
+};
+// ---------------------------------------------------------------------------
+// Helpers
+// ---------------------------------------------------------------------------
+const errResult = (ctx, message) => {
+    ctx.settings.lastErrorResult = { message };
+    writeErr(`\\${ctx.cmdName}: ${message}\n`);
+    // Tell mainloop the diagnostic is already on stderr so it doesn't add
+    // a `psql: ERROR:  <msg>` fallback line.
+    return { status: 'error', errorWritten: true };
+};
+/**
+ * Coerce any thrown / rejected value into a printable string. The
+ * extended-protocol driver in `PgConnection` rejects with raw
+ * ConnectError records (`{severity, code, message, detail, ...}`) —
+ * not `Error` instances — so `String(err)` would produce
+ * `[object Object]` in the conformance output. We probe for a
+ * `.message` property (covering both `Error` and the ConnectError
+ * shape) and fall back to JSON.stringify only when there's no
+ * message field at all.
+ */
+const errorToMessage = (err) => {
+    if (err instanceof Error)
+        return err.message;
+    if (err !== null &&
+        typeof err === 'object' &&
+        'message' in err &&
+        typeof err.message === 'string') {
+        return err.message;
+    }
+    try {
+        return JSON.stringify(err);
+    }
+    catch {
+        return String(err);
+    }
+};
+/**
+ * Render a pipeline-collected ConnectError to stderr in the upstream
+ * shape: a `SEVERITY:  message` line, followed by optional `DETAIL:` /
+ * `HINT:` / `CONTEXT:` lines (each on its own line). Matches the
+ * subset of `formatErrorReport`-style output the conformance corpus
+ * expects from `\endpipeline` for non-FATAL pipeline errors. We
+ * inline a minimal renderer here rather than importing the full
+ * `formatErrorReport` from `cmd_meta` because we always want the
+ * "default verbosity, no LINE/caret context" form — pipeline errors
+ * arrive after the buffered query has been reset and we don't carry
+ * the originating SQL position through `session.lastError`.
+ */
+const renderPipelineError = (err) => {
+    if (err === null || typeof err !== 'object') {
+        writeErr(`ERROR:  ${errorToMessage(err)}\n`);
+        return;
+    }
+    const e = err;
+    // libpq's `PGRES_PIPELINE_ABORTED` marker — the message is the bare
+    // "Pipeline aborted, command did not run" text with no `ERROR:` /
+    // `SEVERITY:` prefix and no DETAIL/HINT/CONTEXT layers. Mirrors the
+    // wording the regress baseline asserts for cascaded skips after a
+    // preceding ErrorResponse.
+    if (e.pipelineAborted) {
+        writeErr(`${e.message ?? 'Pipeline aborted, command did not run'}\n`);
+        return;
+    }
+    const severity = e.severity ?? 'ERROR';
+    const message = e.message ?? '';
+    writeErr(`${severity}:  ${message}\n`);
+    if (e.detail)
+        writeErr(`DETAIL:  ${e.detail}\n`);
+    if (e.hint)
+        writeErr(`HINT:  ${e.hint}\n`);
+    if (e.where)
+        writeErr(`CONTEXT:  ${e.where}\n`);
+};
+const readAllArgs = (ctx) => {
+    const out = [];
+    for (;;) {
+        const arg = ctx.nextArg('normal');
+        if (arg === null)
+            break;
+        out.push(arg);
+    }
+    return out;
+};
+// ---------------------------------------------------------------------------
+// \bind [VALUE ...]
+// ---------------------------------------------------------------------------
+export const cmdBind = {
+    name: 'bind',
+    helpKey: 'bind',
+    run(ctx) {
+        const values = readAllArgs(ctx);
+        stashOf(ctx.settings)[BIND_STATE_KEY] = {
+            name: '',
+            values,
+            byName: false,
+        };
+        return Promise.resolve({ status: 'ok' });
+    },
+};
+// ---------------------------------------------------------------------------
+// \bind_named NAME [VALUE ...]
+// ---------------------------------------------------------------------------
+export const cmdBindNamed = {
+    name: 'bind_named',
+    helpKey: 'bind_named',
+    run(ctx) {
+        const name = ctx.nextArg('normal');
+        // Upstream `exec_command_bind_named` rejects only the missing-arg
+        // case. `''` IS valid — it addresses the unnamed prepared statement
+        // slot (set via `\parse ''`).
+        if (name === null) {
+            // Upstream wipes any prior `\bind_named` state on this error so a
+            // follow-on `\g` falls back to `pset.last_query` (the previous
+            // successful query) instead of executing against a stale handle.
+            stashOf(ctx.settings)[BIND_STATE_KEY] = undefined;
+            return Promise.resolve(errResult(ctx, 'missing required argument'));
+        }
+        const values = readAllArgs(ctx);
+        stashOf(ctx.settings)[BIND_STATE_KEY] = { name, values, byName: true };
+        return Promise.resolve({ status: 'ok' });
+    },
+};
+// ---------------------------------------------------------------------------
+// \parse NAME — prepare current queryBuf as NAME.
+// ---------------------------------------------------------------------------
+export const cmdParse = {
+    name: 'parse',
+    helpKey: 'parse',
+    async run(ctx) {
+        const name = ctx.nextArg('normal');
+        // Upstream `exec_command_parse` rejects only the missing-arg case
+        // with `missing required argument`. An explicit empty string `''`
+        // IS valid — it's the "unnamed" prepared statement slot, addressable
+        // later via `\bind_named ''`.
+        if (name === null) {
+            return errResult(ctx, 'missing required argument');
+        }
+        // Upstream `exec_command_parse` passes the query buffer verbatim to
+        // `PQsendPrepare`, with no trim — the server then stores the bytes
+        // exactly in `pg_prepared_statements.statement`. Trimming here would
+        // strip trailing whitespace that the conformance corpus (and any
+        // `LINE 1:` ErrorResponse echo) expects to round-trip byte-for-byte.
+        // The empty-buffer guard still uses a trimmed view so a whitespace-
+        // only buffer reports `no query buffer` like upstream does.
+        const sql = ctx.queryBuf;
+        if (sql.trim().length === 0) {
+            return errResult(ctx, 'no query buffer');
+        }
+        if (!ctx.settings.db) {
+            return errResult(ctx, 'no connection to the server');
+        }
+        // In pipeline mode, route the Parse through the active session so
+        // it gets queued behind the in-flight P/B/E ops (and the server
+        // defers any ParseError until the next Sync). Doing a `db.prepare`
+        // here would issue its own Sync mid-pipeline, corrupting the
+        // pipeline's reply ordering — the conformance corpus exercises a
+        // `\parse '' \parse '' \parse pipeline_1` triple-Parse and
+        // expects the third Parse's `could not determine data type` error
+        // to surface AT `\endpipeline` time, not synchronously here.
+        const pipelineActive = getPipelineState(ctx.settings);
+        if (pipelineActive !== null) {
+            try {
+                // `\parse NAME` is a USER-level command (one entry on libpq's
+                // result queue), so route through `parseSlot` (real
+                // PipelineSession) which both enqueues the Parse wire op AND
+                // registers a `cmdSlots` entry. `\getresults` walks `cmdSlots`,
+                // so without the slot the cmd would be invisible to drain
+                // accounting. Test mocks that don't implement `parseSlot` fall
+                // through to the plain `parse()` method.
+                const session = pipelineActive.session;
+                if (typeof session.parseSlot === 'function') {
+                    await session.parseSlot(name, sql, []);
+                }
+                else {
+                    await session.parse(name, sql, []);
+                }
+                ctx.settings.lastQuery = sql;
+                // Upstream `exec_command_parse` bumps `pset.piped_commands` after
+                // PQsendPrepare succeeds — the Parse is one queued command.
+                bumpCounter(ctx.settings, 'PIPELINE_COMMAND_COUNT', 1);
+                return { status: 'reset-buf', newBuf: '' };
+            }
+            catch (err) {
+                return errResult(ctx, errorToMessage(err));
+            }
+        }
+        try {
+            const ps = await ctx.settings.db.prepare(name, sql);
+            // Cache for `\bind_named NAME \g` lookup later. Upstream tracks
+            // server-side prepared statements by name in `pset.psqlScanState`-
+            // adjacent state; we keep a local map so a follow-on `\g` can
+            // bind + execute without re-parsing.
+            stashPrepared(ctx.settings, name, ps);
+            // Upstream `exec_command_parse` also updates `pset.last_query` to
+            // the prepared SQL so a subsequent `\g` (e.g. after a failed
+            // `\bind_named NAME` that wipes bind state) re-runs the parsed
+            // text via the simple-query path. Without this, our `\g` would
+            // either no-op or fall back to a stale prior query, missing the
+            // "ERROR: there is no parameter $1" the conformance corpus
+            // expects from `SELECT $1, $2` executed without bind params.
+            ctx.settings.lastQuery = sql;
+            return { status: 'reset-buf', newBuf: '' };
+        }
+        catch (err) {
+            return errResult(ctx, errorToMessage(err));
+        }
+    },
+};
+// ---------------------------------------------------------------------------
+// \close_prepared NAME
+// ---------------------------------------------------------------------------
+export const cmdClosePrepared = {
+    name: 'close_prepared',
+    helpKey: 'close_prepared',
+    async run(ctx) {
+        const name = ctx.nextArg('normal');
+        // Empty string `''` is the valid unnamed prepared statement.
+        if (name === null) {
+            return errResult(ctx, 'missing required argument');
+        }
+        const db = ctx.settings.db;
+        if (!db) {
+            return errResult(ctx, 'no connection to the server');
+        }
+        // Inside an open pipeline, upstream routes through
+        // `PQsendClosePrepared` (queues a `Close('S', name)` behind the
+        // already-pending P/B/E ops, no Sync). Issuing a Sync here — as the
+        // out-of-pipeline `db.closePreparedStatement` path does — would split
+        // the in-flight batch and surface the pipeline's sticky error on the
+        // wire, leading to `\close_prepared: bind message supplies …`
+        // diagnostics that vanilla never emits.
+        const ps = getPipelineState(ctx.settings);
+        if (ps !== null) {
+            try {
+                // `\close_prepared NAME` is a USER-level command — route through
+                // `closeSlot` so it registers on `cmdSlots` like Parse / Execute
+                // (see the parseSlot comment in `\parse` above). Test mocks
+                // that don't implement `closeSlot` fall through to plain
+                // `close()`.
+                const session = ps.session;
+                if (typeof session.closeSlot === 'function') {
+                    await session.closeSlot(name);
+                }
+                else {
+                    await session.close(name);
+                }
+                // Upstream `exec_command_close_prepared` bumps `piped_commands`
+                // (PIPELINE_COMMAND_COUNT) after a successful PQsendClosePrepared.
+                bumpCounter(ctx.settings, 'PIPELINE_COMMAND_COUNT', 1);
+                // Drop any cached binding so a later `\bind_named NAME \g`
+                // errors cleanly instead of using a stale handle.
+                dropPrepared(ctx.settings, name);
+                return { status: 'ok' };
+            }
+            catch (err) {
+                return errResult(ctx, errorToMessage(err));
+            }
+        }
+        try {
+            // Out-of-pipeline path: upstream issues `Close('S', name) + Sync`
+            // directly; the server treats Close on a missing name as a no-op
+            // (CloseComplete without diagnostics), so we don't need to know
+            // whether the statement exists. A previous implementation faked a
+            // `prepare(name, 'SELECT 1')` to reach the same Close, which broke
+            // when the name was already prepared on the server (Parse fails
+            // with `prepared statement "NAME" already exists`).
+            if (db.closePreparedStatement) {
+                await db.closePreparedStatement(name);
+            }
+            else {
+                // Backwards-compat path for Connection mocks that don't
+                // implement the dedicated entry point. The real PgConnection
+                // always provides closePreparedStatement; this branch only
+                // fires under unit tests with bespoke Connection mocks.
+                const stmt = await db.prepare(name, 'SELECT 1');
+                await stmt.close();
+            }
+            // Drop any cached binding so a later `\bind_named NAME \g` errors
+            // cleanly instead of using a stale handle.
+            dropPrepared(ctx.settings, name);
+            return { status: 'ok' };
+        }
+        catch (err) {
+            return errResult(ctx, errorToMessage(err));
+        }
+    },
+};
+// ---------------------------------------------------------------------------
+// \startpipeline / \endpipeline
+// ---------------------------------------------------------------------------
+export const cmdStartPipeline = {
+    name: 'startpipeline',
+    helpKey: 'startpipeline',
+    run(ctx) {
+        if (!ctx.settings.db) {
+            return Promise.resolve(errResult(ctx, 'no connection to the server'));
+        }
+        // Vanilla psql 18.4 treats a duplicate `\startpipeline` as a silent
+        // no-op (no warning on stdout OR stderr) — verified empirically:
+        // `psql --no-psqlrc --echo-all --quiet -X -c '\startpipeline
+        // \startpipeline \endpipeline' 2>&1` prints only the three echoed
+        // lines. Our prior `errResult('pipeline already active')` was a
+        // divergence; match upstream's quiet path.
+        if (getPipelineState(ctx.settings) !== null) {
+            return Promise.resolve({ status: 'ok' });
+        }
+        try {
+            const session = wrapSessionForCounters(ctx.settings.db.pipeline(), ctx.settings);
+            stashOf(ctx.settings)[PIPELINE_KEY] = {
+                session,
+                pending: [],
+                drainedCount: 0,
+            };
+            ctx.settings.sendMode = 'extended-pipeline';
+            // Upstream `exec_command_startpipeline` calls SetVariable for the three
+            // counter vars (zeroing whatever the prior pipeline left behind).
+            resetPipelineCounters(ctx.settings);
+            return Promise.resolve({ status: 'ok' });
+        }
+        catch (err) {
+            return Promise.resolve(errResult(ctx, errorToMessage(err)));
+        }
+    },
+};
+export const cmdEndPipeline = {
+    name: 'endpipeline',
+    helpKey: 'endpipeline',
+    async run(ctx) {
+        const ps = getPipelineState(ctx.settings);
+        if (!ps) {
+            // Upstream `exec_command_endpipeline` writes the diagnostic via
+            // `pg_log_error`; in psql 18.4 the line lands on stderr with NO
+            // `psql:` / `\endpipeline:` prefix (verified empirically with
+            // `psql --no-psqlrc --echo-all --quiet -X -c '\endpipeline'
+            // 2>&1` — the only stderr line is the raw message). The
+            // conformance corpus mirrors that bare form, so we bypass
+            // `errResult` (which would inject `\endpipeline: `) and write
+            // the line directly.
+            ctx.settings.lastErrorResult = {
+                message: 'cannot send pipeline when not in pipeline mode',
+            };
+            writeErr('cannot send pipeline when not in pipeline mode\n');
+            return { status: 'error', errorWritten: true };
+        }
+        try {
+            // Snapshot how many slots were already surfaced by prior
+            // `\getresults` calls — only the residual that the final Sync
+            // inside `session.end()` flushes should be printed. Upstream
+            // psql achieves this implicitly via `PQgetResult()` consuming
+            // results from libpq's queue inside `\getresults`; we mirror
+            // the semantics with an explicit cursor (`drainedCount`).
+            const alreadyDrained = ps.drainedCount;
+            // Hold a reference to the session BEFORE end() clears the stash —
+            // we still need `lastError` after the pipeline has been torn down.
+            // The session is `Pipeline` (interface) but the concrete impl
+            // (`PipelineSession`) exposes per-USER-command slot tracking; cast
+            // and probe for the field so test mocks (which don't carry the
+            // extra fields) still work — they get an empty snapshot and the
+            // path degenerates to the previous `sets`-only rendering.
+            const session = ps.session;
+            // Capture per-USER-command slots as a snapshot — `end()` settles
+            // them but doesn't expose the per-op rejection records, which
+            // we need to interleave errors at the correct ordinal position.
+            const cmdSlotsSnapshot = Array.isArray(session.cmdSlots)
+                ? session.cmdSlots.slice()
+                : [];
+            // FETCH_COUNT-in-pipeline detection — when the user set FETCH_COUNT
+            // and the pipeline is being aborted, upstream emits the
+            // "fetching results in chunked mode failed" wording in lieu of
+            // (or in addition to) the regular Pipeline aborted line. Read
+            // BEFORE end() resets the counters.
+            const fetchCountActive = (ctx.settings.vars.get('FETCH_COUNT') ?? '0') !== '0';
+            const sets = await ps.session.end();
+            stashOf(ctx.settings)[PIPELINE_KEY] = undefined;
+            ctx.settings.sendMode = 'extended-query';
+            // Upstream `exec_command_endpipeline` zeroes the counters once the
+            // pipeline has drained — mirrors the empirical behaviour of vanilla
+            // psql 18.4 where `\echo :PIPELINE_*` reads "0" after `\endpipeline`.
+            resetPipelineCounters(ctx.settings);
+            // Drop any accumulated pipeline-gate diagnostics (`\gdesc not
+            // allowed in pipeline mode` etc.) so a future pipeline starts
+            // with a clean error log. Upstream resets the equivalent
+            // libpq-side error stack at the same boundary.
+            clearPipelineGateErrors(ctx.settings);
+            // Walk the per-USER-command slots in issue order, interleaving
+            // ErrorResponse renderings with successful ResultSets. Upstream
+            // psql 18.4 emits errors EXACTLY where the failed op sat in the
+            // wire stream (see expected/psql_pipeline.out line 433: the
+            // `bind message supplies 0 parameters` ERROR prints BEFORE the
+            // second `\sendpipeline`'s `?column?` table because the failed
+            // bind was the first Execute and the successful query was the
+            // second). Plain "print all sets then error" would invert the
+            // order.
+            const settled = await Promise.allSettled(cmdSlotsSnapshot);
+            let errorRendered = false;
+            // When the snapshot is empty (test mocks that don't track
+            // cmdSlots), fall back to printing the `sets` returned by
+            // `end()` directly. This preserves the historical behaviour for
+            // mocks while keeping the in-order interleaving for the real
+            // PipelineSession.
+            const entries = settled.length > 0
+                ? settled
+                : sets.map((rs) => ({
+                    status: 'fulfilled',
+                    value: rs,
+                }));
+            // Pre-scan THIS slice (entries from `alreadyDrained` onward) for
+            // the first non-aborted rejection. The wire layer cascade-rejects
+            // every queued non-sync op on ErrorResponse: the first failing op
+            // gets the real `ConnectError`, follow-on ops are rejected with
+            // the synthetic `pipelineAborted` marker. When the failing op
+            // lives in `pending` (Parse / Bind / Close — none of which are
+            // tracked on `cmdSlots` as a separate slot), the slot inherits
+            // the cascaded marker — in that case fall through to
+            // `session.lastError` which captures the original ERROR from the
+            // wire-layer `sync()` / `end()` path.
+            const sliceForError = entries.slice(alreadyDrained);
+            const realFromSlice = (() => {
+                for (const r of sliceForError) {
+                    if (r.status !== 'rejected')
+                        continue;
+                    const reason = r.reason;
+                    const isAborted = typeof reason === 'object' &&
+                        reason !== null &&
+                        reason.pipelineAborted === true;
+                    if (!isAborted)
+                        return reason;
+                }
+                return null;
+            })();
+            const realLastError = realFromSlice ??
+                (() => {
+                    const le = session.lastError;
+                    if (le === null || le === undefined)
+                        return null;
+                    if (typeof le === 'object' &&
+                        le.pipelineAborted) {
+                        return null;
+                    }
+                    return le;
+                })();
+            for (let i = alreadyDrained; i < entries.length; i++) {
+                const r = entries[i];
+                if (r.status === 'fulfilled') {
+                    const rs = r.value;
+                    // Emit any NoticeResponse messages attached to this result
+                    // to stderr in the upstream libpq shape
+                    // (`${severity}:  ${message}\n`). In pipeline mode the
+                    // server emits notices interleaved with Bind / Execute
+                    // replies, so they're attached to the corresponding
+                    // ResultSet's `notices` array; vanilla psql 18.4 prints
+                    // them BEFORE the result body at `\endpipeline` time
+                    // (e.g. `regress/psql_pipeline.out` line 671: the
+                    // `WARNING:  SET LOCAL can only be used in transaction
+                    // blocks` lands right before the first `statement_timeout`
+                    // table).
+                    for (const n of rs.notices) {
+                        let out = `${n.severity}:  ${n.message}\n`;
+                        if (n.detail !== undefined)
+                            out += `DETAIL:  ${n.detail}\n`;
+                        if (n.hint !== undefined)
+                            out += `HINT:  ${n.hint}\n`;
+                        writeErr(out);
+                    }
+                    // Print real tuples-producing results — including the 0-column
+                    // 1-row shape from `SELECT \bind \sendpipeline` which upstream
+                    // psql renders as `--\n(1 row)\n` (the table glyphs are just
+                    // the trailing separator row plus the default row-count footer).
+                    // Skip our internal Sync marker (empty `command`, see
+                    // wire/pipeline.ts) and DDL-style CommandComplete-only sets
+                    // (non-empty `command` but no fields and no rows).
+                    const isSyncOrPlaceholder = rs.fields.length === 0 && rs.command === '' && rs.rows.length === 0;
+                    const isCommandOnly = rs.fields.length === 0 && rs.rows.length === 0 && rs.command !== '';
+                    if (!isSyncOrPlaceholder && !isCommandOnly) {
+                        if (rs.fields.length === 0 && rs.rows.length > 0) {
+                            // 0-column tuples result: the aligned printer's
+                            // header/rule machinery degenerates to whitespace because
+                            // there are no column widths to drive the dividers. Emit
+                            // the upstream-shaped placeholder (`--` separator + row
+                            // count) inline so we match `psql_pipeline.out`'s
+                            // `\watch`-rejected SELECT output byte-for-byte.
+                            const tuplesOnly = ctx.settings.popt.topt.tuplesOnly;
+                            if (!tuplesOnly) {
+                                process.stdout.write('--\n');
+                                process.stdout.write(`(${rs.rows.length} ${rs.rows.length === 1 ? 'row' : 'rows'})\n\n`);
+                            }
+                        }
+                        else {
+                            await alignedPrinter.printQuery(rs, ctx.settings.popt, process.stdout);
+                        }
+                    }
+                }
+                else if (!errorRendered) {
+                    // Render only the FIRST rejection inline — subsequent ops
+                    // in an aborted pipeline reject with the synthetic
+                    // `pipelineAborted` marker which we coalesce to one line.
+                    // When the wire layer cascade-rejected from a Parse / Bind /
+                    // Close that lives in `pending`, the only entry visible here
+                    // is one rejected with `pipelineAborted` — fall back to
+                    // `session.lastError` / `peekRealError` for the original
+                    // ERROR.
+                    const reason = r.reason;
+                    const isAborted = typeof reason === 'object' &&
+                        reason !== null &&
+                        reason.pipelineAborted === true;
+                    // FETCH_COUNT-in-pipeline: upstream emits the chunked-mode
+                    // diagnostic in addition to the per-op line. Both go to
+                    // stderr; the chunked-mode line comes FIRST and addresses the
+                    // SQL-shaped failure (libpq's PQsetSingleRowMode rejection
+                    // inside a pipeline). Mirror that for any rejection that
+                    // surfaces at `\endpipeline` time while FETCH_COUNT was set.
+                    // The chunked-mode prefix is gated on FETCH_COUNT, but the REAL
+                    // ERROR must still be surfaced — the old code printed the prefix +
+                    // "Pipeline aborted" for ANY rejection under FETCH_COUNT, swallowing
+                    // the actual ERROR: text (review: minor divergences). "Pipeline
+                    // aborted, command did not run" is shown ONLY for the synthetic
+                    // queue-skip marker (no real error behind it).
+                    if (fetchCountActive) {
+                        writeErr('fetching results in chunked mode failed\n');
+                    }
+                    if (isAborted && realLastError !== null) {
+                        renderPipelineError(realLastError);
+                    }
+                    else if (isAborted) {
+                        writeErr('Pipeline aborted, command did not run\n');
+                    }
+                    else {
+                        renderPipelineError(reason);
+                    }
+                    errorRendered = true;
+                }
+            }
+            // Fallback: if `session.lastError` was set but no per-op
+            // rejection was observed (can happen when the error came from
+            // the trailing Sync rather than a specific Execute), render it
+            // here. Otherwise the diagnostic would be lost.
+            if (!errorRendered) {
+                const lastErr = session.lastError;
+                if (lastErr !== null && lastErr !== undefined) {
+                    // A real trailing-Sync error: name the chunked-mode failure when
+                    // FETCH_COUNT was active, but still render the actual ERROR rather
+                    // than the synthetic "Pipeline aborted" line (review: minor).
+                    if (fetchCountActive) {
+                        writeErr('fetching results in chunked mode failed\n');
+                    }
+                    renderPipelineError(lastErr);
+                }
+            }
+            return { status: 'ok' };
+        }
+        catch (err) {
+            stashOf(ctx.settings)[PIPELINE_KEY] = undefined;
+            ctx.settings.sendMode = 'extended-query';
+            // Even on a failed `\endpipeline` (e.g. server hung up mid-drain),
+            // mirror upstream and clear the counters — the pipeline state is
+            // gone, so any non-zero value would be misleading. Same for the
+            // pipeline-gate error log.
+            resetPipelineCounters(ctx.settings);
+            clearPipelineGateErrors(ctx.settings);
+            return errResult(ctx, errorToMessage(err));
+        }
+    },
+};
+// ---------------------------------------------------------------------------
+// \syncpipeline / \flushrequest / \flush
+// ---------------------------------------------------------------------------
+export const cmdSyncPipeline = {
+    name: 'syncpipeline',
+    helpKey: 'syncpipeline',
+    async run(ctx) {
+        const ps = getPipelineState(ctx.settings);
+        if (!ps)
+            return errResult(ctx, 'no pipeline active');
+        try {
+            await ps.session.sync();
+            // Upstream `exec_command_syncpipeline`:
+            //   piped_results += piped_commands;
+            //   piped_commands = 0;
+            //   piped_syncs++;
+            // The pending commands have transitioned to "queued results" on the
+            // server, and Sync is itself counted as a piped command boundary.
+            const queued = readCounter(ctx.settings, 'PIPELINE_COMMAND_COUNT');
+            setCounter(ctx.settings, 'PIPELINE_COMMAND_COUNT', 0);
+            bumpCounter(ctx.settings, 'PIPELINE_RESULT_COUNT', queued);
+            bumpCounter(ctx.settings, 'PIPELINE_SYNC_COUNT', 1);
+            return { status: 'ok' };
+        }
+        catch (err) {
+            return errResult(ctx, errorToMessage(err));
+        }
+    },
+};
+export const cmdFlushRequest = {
+    name: 'flushrequest',
+    helpKey: 'flushrequest',
+    async run(ctx) {
+        const ps = getPipelineState(ctx.settings);
+        if (!ps)
+            return errResult(ctx, 'no pipeline active');
+        try {
+            await ps.session.flush();
+            // Upstream `exec_command_flushrequest`:
+            //   piped_results += piped_commands;
+            //   piped_commands = 0;
+            // The pending commands move to "queued results" but SYNC isn't issued.
+            const queued = readCounter(ctx.settings, 'PIPELINE_COMMAND_COUNT');
+            setCounter(ctx.settings, 'PIPELINE_COMMAND_COUNT', 0);
+            bumpCounter(ctx.settings, 'PIPELINE_RESULT_COUNT', queued);
+            return { status: 'ok' };
+        }
+        catch (err) {
+            return errResult(ctx, errorToMessage(err));
+        }
+    },
+};
+export const cmdFlush = {
+    name: 'flush',
+    helpKey: 'flush',
+    run(ctx) {
+        return cmdFlushRequest.run(ctx);
+    },
+};
+// ---------------------------------------------------------------------------
+// \sendpipeline — submit current buffer with stashed bind params.
+// ---------------------------------------------------------------------------
+export const cmdSendPipeline = {
+    name: 'sendpipeline',
+    helpKey: 'sendpipeline',
+    async run(ctx) {
+        const ps = getPipelineState(ctx.settings);
+        if (!ps) {
+            // Upstream wording (psql 18.4): "\\sendpipeline not allowed
+            // outside of pipeline mode". Verified empirically; no
+            // `\sendpipeline: ` prefix on stderr.
+            //
+            // Upstream `exec_command_sendpipeline` also calls
+            // `clean_extended_state()` here, which clears any pending
+            // `\bind` / `\bind_named` parameters. Mirror that so a later
+            // `\startpipeline` followed by a bare `\sendpipeline` reports
+            // the missing-bind diagnostic instead of replaying the stale
+            // parameters from before the failed-outside-pipeline send.
+            consumeBindState(ctx.settings);
+            ctx.settings.lastErrorResult = {
+                message: '\\sendpipeline not allowed outside of pipeline mode',
+            };
+            writeErr('\\sendpipeline not allowed outside of pipeline mode\n');
+            return { status: 'error', errorWritten: true };
+        }
+        const bind = consumeBindState(ctx.settings);
+        // Upstream `exec_command_sendpipeline` (in pipeline mode) requires
+        // a preceding `\bind` or `\bind_named`. Without it, the error is
+        // "\sendpipeline must be used after \bind or \bind_named", emitted
+        // BEFORE the empty-buffer check. The conformance test exercises
+        // both `\sendpipeline` (no buffer, no bind) and `SELECT 1
+        // \sendpipeline` (with buffer, no bind) — both must produce the
+        // same diagnostic, so order matters here.
+        if (bind === null) {
+            ctx.settings.lastErrorResult = {
+                message: '\\sendpipeline must be used after \\bind or \\bind_named',
+            };
+            writeErr('\\sendpipeline must be used after \\bind or \\bind_named\n');
+            return { status: 'error', errorWritten: true };
+        }
+        const sql = ctx.queryBuf.trim();
+        const stmtName = bind.name;
+        const params = bind.values;
+        // `\bind_named NAME` re-uses a server-side prep stmt, so an empty
+        // buffer is fine — we skip the Parse and just Bind + Execute. The
+        // anonymous-`\bind` path still needs a buffer because we must
+        // Parse the SQL first.
+        if (!bind.byName && sql.length === 0) {
+            return errResult(ctx, 'no query buffer');
+        }
+        try {
+            // We send the full P/B/E sequence without an intervening Sync — the
+            // user is expected to call \syncpipeline or \endpipeline to commit.
+            // For `\bind_named`, skip Parse (the prep stmt already exists on
+            // the server, named by the user). For anonymous `\bind`, queue
+            // an unnamed Parse so the SQL is parsed on the server in this
+            // batch.
+            if (!bind.byName) {
+                await ps.session.parse('', sql, []);
+            }
+            await ps.session.bind(stmtName, params);
+            const exec = (async () => {
+                await ps.session.execute('', 0);
+                // PipelineSession.execute resolves with void on the public API; the
+                // session internally tracks the ResultSet and surfaces it in end().
+                return {
+                    command: '',
+                    rowCount: null,
+                    oid: null,
+                    fields: [],
+                    rows: [],
+                    notices: [],
+                };
+            })();
+            ps.pending.push(exec);
+            return { status: 'reset-buf', newBuf: '' };
+        }
+        catch (err) {
+            return errResult(ctx, errorToMessage(err));
+        }
+    },
+};
+// ---------------------------------------------------------------------------
+// \getresults [N] — drain N pending results (or all if N omitted).
+// ---------------------------------------------------------------------------
+export const cmdGetResults = {
+    name: 'getresults',
+    helpKey: 'getresults',
+    async run(ctx) {
+        const ps = getPipelineState(ctx.settings);
+        const arg = ctx.nextArg('normal');
+        // Upstream `exec_command_getresults` parses the optional count BEFORE
+        // checking pipeline state, so an invalid count surfaces even when
+        // there's no pipeline active. The wording matches upstream verbatim
+        // ("invalid number of requested results").
+        let requested = null;
+        if (arg !== null && arg.length > 0) {
+            const parsed = parseInt(arg, 10);
+            if (!Number.isFinite(parsed) || parsed < 0) {
+                return errResult(ctx, 'invalid number of requested results');
+            }
+            requested = parsed;
+        }
+        // No active pipeline → upstream prints `No pending results to get`
+        // (the "no-op idle" message), NOT a hard "no pipeline active" error.
+        // This matches the conformance test that runs `\getresults` BOTH
+        // outside of `\startpipeline / \endpipeline` brackets and right
+        // after `\endpipeline`.
+        if (!ps) {
+            process.stdout.write('No pending results to get\n');
+            return { status: 'ok' };
+        }
+        // Available items to drain = PIPELINE_SYNC_COUNT + PIPELINE_RESULT_COUNT.
+        // Sync markers and data-result entries both occupy slots in libpq's
+        // pipeline result queue; vanilla's `\getresults N` walks the queue
+        // FIFO, draining either kind. A `\sendpipeline` queued on the
+        // client but not yet `\flushrequest`-ed / `\syncpipeline`-ed does
+        // NOT count — those commands have a still-pending Execute promise
+        // but the server hasn't been told to flush replies. Verified
+        // empirically with vanilla psql 18.4: SQL like
+        //   \syncpipeline \syncpipeline SELECT $1 \bind 1 \sendpipeline
+        //   \flushrequest \getresults 1
+        // prints nothing on the first \getresults 1 (SyncMarker drained,
+        // SYNC_COUNT: 2 → 1), the second prints nothing (SYNC_COUNT: 1 →
+        // 0), and the third prints the SELECT result.
+        const syncAvailable = readCounter(ctx.settings, 'PIPELINE_SYNC_COUNT');
+        const resultAvailable = readCounter(ctx.settings, 'PIPELINE_RESULT_COUNT');
+        const available = syncAvailable + resultAvailable;
+        if (available === 0) {
+            process.stdout.write('No pending results to get\n');
+            return { status: 'ok' };
+        }
+        // `\getresults 0` and bare `\getresults` mean "all pending"
+        // (upstream semantics).
+        const n = requested === null || requested === 0
+            ? available
+            : Math.min(requested, available);
+        // Pull the next `n` per-USER-COMMAND slots from `cmdSlots`. Each
+        // entry mirrors one `PQgetResult` boundary in libpq: a
+        // `\sendpipeline` (Parse+Bind+Execute → one slot resolving to the
+        // ResultSet), a `\parse NAME` (one slot resolving to a silent
+        // placeholder), a `\close_prepared NAME` (silent placeholder),
+        // or a `\syncpipeline` (silent SyncMarker). `drainedCount`
+        // advances by `n` so a follow-on `\endpipeline` knows to skip
+        // what we've already walked. Test mocks that don't populate
+        // `cmdSlots` fall back to the legacy counter-only path.
+        const session = ps.session;
+        const slots = Array.isArray(session.cmdSlots)
+            ? session.cmdSlots
+            : [];
+        const start = ps.drainedCount;
+        const end = start + n;
+        const slice = slots.slice(start, end);
+        ps.drainedCount = end;
+        // Keep `ps.pending` in sync for any legacy callers that read its
+        // length — splice off the consumed count. The spliced promises are
+        // synthetic placeholders, so we discard the return value.
+        void ps.pending.splice(0, n);
+        try {
+            const settled = await Promise.allSettled(slice);
+            // The wire layer's cascade-reject puts the real `ConnectError` on
+            // the FIRST failing op (Parse / Bind / Close — pushed onto
+            // `pending`, not `cmdSlots` as a separate slot), and stamps the
+            // synthetic `pipelineAborted` marker onto every op queued behind
+            // it. The visible cmdSlot for the Execute in the same `\sendpipeline`
+            // therefore inherits the cascaded marker — we need a separate
+            // look-up to surface the original ERROR.
+            //
+            // Strategy:
+            //   1. Prefer a non-aborted rejection found IN this slice (e.g.
+            //      a Parse-only command whose Parse failed at the SLOT level).
+            //   2. Otherwise fall back to `peekRealError()` which scans
+            //      pending ∪ results for the first non-aborted rejection.
+            //      After `\syncpipeline` clears `pending`, this returns null
+            //      for purely-cascaded batches — which is correct, the slot
+            //      message ("Pipeline aborted, command did not run") is the
+            //      one that should surface.
+            const sliceErr = (() => {
+                for (const r of settled) {
+                    if (r.status !== 'rejected')
+                        continue;
+                    const reason = r.reason;
+                    const isAborted = typeof reason === 'object' &&
+                        reason !== null &&
+                        reason.pipelineAborted === true;
+                    if (!isAborted)
+                        return reason;
+                }
+                return null;
+            })();
+            const sessPeek = session;
+            const realErr = sliceErr ??
+                (typeof sessPeek.peekRealError === 'function'
+                    ? await sessPeek.peekRealError()
+                    : null);
+            // Per upstream `\getresults`: emit AT MOST ONE error / aborted
+            // line per call, even when the slice contains multiple rejections.
+            // First rejection's line wins; subsequent ones are suppressed
+            // inline (still implicitly accounted via the counter decrement
+            // below). Real ERROR trumps the synthetic `Pipeline aborted, …`
+            // marker — see `peekRealError`'s discovery semantics.
+            let errorRenderedHere = false;
+            let walkedItems = 0;
+            let syncsDrained = 0;
+            let resultsDrained = 0;
+            // Cursor into `slots`: indices ≥ this represent SyncMarkers
+            // pushed by `session.sync()`. We can't tag the slot in flight
+            // without changing the public shape; instead we attribute the
+            // first `syncAvailable` silent placeholders to SYNC_COUNT and
+            // the remainder to RESULT_COUNT post-walk.
+            for (const r of settled) {
+                walkedItems++;
+                if (r.status !== 'fulfilled') {
+                    // Rejected promise — Parse / Bind / Execute / Close that the
+                    // server responded to with ErrorResponse, or a cascaded
+                    // pipelineAborted marker. Upstream `\getresults` walks
+                    // libpq's per-Sync result queue inline: the failed entry
+                    // produces an `ERROR: …` (or `Pipeline aborted, …`) on
+                    // stderr at the `\getresults` line, not deferred to
+                    // `\endpipeline`. Match that — but only render the FIRST
+                    // rejection in this call so we don't double-print when an
+                    // aborted pipeline funnels multiple sticky rejections
+                    // through the same `\getresults`.
+                    resultsDrained++;
+                    if (!errorRenderedHere) {
+                        const reason = r.reason;
+                        const isAborted = typeof reason === 'object' &&
+                            reason !== null &&
+                            reason.pipelineAborted ===
+                                true;
+                        if (isAborted && realErr !== null) {
+                            renderPipelineError(realErr);
+                        }
+                        else {
+                            renderPipelineError(reason);
+                        }
+                        errorRenderedHere = true;
+                    }
+                    continue;
+                }
+                const rs = r.value;
+                // Emit any NoticeResponse messages attached to this result to
+                // stderr (libpq shape). Notices arrive interleaved with the
+                // Bind / Execute replies and stick to the relevant ResultSet;
+                // upstream psql renders them inline with each result's prelude.
+                for (const n of rs.notices) {
+                    let out = `${n.severity}:  ${n.message}\n`;
+                    if (n.detail !== undefined)
+                        out += `DETAIL:  ${n.detail}\n`;
+                    if (n.hint !== undefined)
+                        out += `HINT:  ${n.hint}\n`;
+                    writeErr(out);
+                }
+                // Silent placeholder: empty fields, empty command, no rows.
+                // Either a SyncMarker (from `session.sync()`) or a successful
+                // Parse-only / Close-only slot. Both print nothing; counter
+                // attribution is fixed up at the tail of this function based
+                // on `syncAvailable`.
+                if (rs.fields.length === 0 &&
+                    rs.command === '' &&
+                    rs.rows.length === 0) {
+                    syncsDrained++;
+                    continue;
+                }
+                resultsDrained++;
+                if (rs.fields.length === 0 && rs.rows.length > 0) {
+                    // 0-column tuples result — same upstream placeholder shape as
+                    // `\endpipeline` (see comment there).
+                    const tuplesOnly = ctx.settings.popt.topt.tuplesOnly;
+                    if (!tuplesOnly) {
+                        process.stdout.write('--\n');
+                        process.stdout.write(`(${rs.rows.length} ${rs.rows.length === 1 ? 'row' : 'rows'})\n\n`);
+                    }
+                }
+                else if (rs.fields.length > 0) {
+                    await alignedPrinter.printQuery(rs, ctx.settings.popt, process.stdout);
+                }
+            }
+            // Tell the wire layer how far the cmd layer has consumed from its
+            // results queue. `PipelineSession.end()` uses this offset to skip
+            // entries that `\getresults` has already inspected; otherwise the
+            // rejected promise we just rendered here would get re-stashed on
+            // `session.lastError` and `\endpipeline`'s fallback would
+            // double-print the same `ERROR: …` line. The offset is into
+            // `results` (the per-Execute promise list) not `cmdSlots`; we
+            // approximate by passing `end` (close enough for the
+            // `_externalDrained` check, which is only consulted by `end()`
+            // to skip ALREADY-INSPECTED rejections).
+            const sessMark = session;
+            if (typeof sessMark.markDrained === 'function') {
+                sessMark.markDrained(end);
+            }
+            // Once we surface a rejection inline here, also clear any sticky
+            // `lastError` already stashed by a previous wire-layer scan so
+            // `\endpipeline`'s fallback doesn't re-emit the same diagnostic.
+            if (errorRenderedHere) {
+                const sessAny = session;
+                if (typeof sessAny.clearLastError === 'function') {
+                    sessAny.clearLastError();
+                }
+            }
+            // Fallback when `cmdSlots` wasn't populated (test mocks):
+            // decrement RESULT_COUNT first, then SYNC_COUNT. Real
+            // PipelineSession populates `cmdSlots` so the walk above already
+            // attributed each drain to the right counter.
+            if (walkedItems === 0) {
+                const ddata = Math.min(n, resultAvailable);
+                resultsDrained = ddata;
+                syncsDrained = n - ddata;
+            }
+            else {
+                // The walk lumped successful silent placeholders (Parse / Close
+                // OK) into `syncsDrained`. Re-attribute: SYNC_COUNT only goes
+                // down by the number of SyncMarkers we actually drained (capped
+                // at `syncAvailable`); the rest are result-style drains.
+                const actualSyncs = Math.min(syncsDrained, syncAvailable);
+                const extraResults = syncsDrained - actualSyncs;
+                syncsDrained = actualSyncs;
+                resultsDrained += extraResults;
+            }
+            // Decrement counters. Upstream `exec_command_getresults` does the
+            // same accounting: PIPELINE_SYNC_COUNT and PIPELINE_RESULT_COUNT
+            // are decremented by the actually-consumed items in each
+            // category. SYNC_COUNT only goes down when a drain walks an
+            // actual SyncMarker slot — we don't force-reset it when
+            // RESULT_COUNT hits zero, because the queue may still hold the
+            // pending PGRES_PIPELINE_SYNC entry. The regress test
+            // `\getresults 1` x5 after 4 commands + 1 sync drains the 5th
+            // call silently against the SyncMarker; a 6th call would emit
+            // "No pending results to get".
+            bumpCounter(ctx.settings, 'PIPELINE_SYNC_COUNT', -syncsDrained);
+            bumpCounter(ctx.settings, 'PIPELINE_RESULT_COUNT', -resultsDrained);
+            return { status: 'ok' };
+        }
+        catch (err) {
+            return errResult(ctx, errorToMessage(err));
+        }
+    },
+};
+// ---------------------------------------------------------------------------
+// \gdesc — describe the buffered query without executing it.
+//
+// The implementation lives in `./cmd_io.ts` (it shares the printer-routing
+// machinery used by `\g` / `\gx` / `\watch`); we re-export the spec here
+// so the existing pipeline test (which imports `cmdGdesc` from this
+// module) continues to compile. Registration is left to `cmd_io.ts`'s
+// `registerIoCommands` so we don't double-register.
+// ---------------------------------------------------------------------------
+export { cmdGdesc } from './cmd_io.js';
+// ---------------------------------------------------------------------------
+// Registration entry point.
+// ---------------------------------------------------------------------------
+export const registerPipelineCommands = (registry) => {
+    registry.register(cmdBind);
+    registry.register(cmdBindNamed);
+    registry.register(cmdParse);
+    registry.register(cmdClosePrepared);
+    registry.register(cmdStartPipeline);
+    registry.register(cmdEndPipeline);
+    registry.register(cmdSyncPipeline);
+    registry.register(cmdFlushRequest);
+    registry.register(cmdFlush);
+    registry.register(cmdSendPipeline);
+    registry.register(cmdGetResults);
+};