@rebasepro/server-postgres 0.23.0 → 0.24.1-canary.g19596ef

package/dist/services/cdc/trigger-cdc.d.ts

@@ -6,9 +6,13 @@ import type { RawSqlRunner } from "../../security/rls-enforcement.js";
  * — like Supabase Realtime — sees *every* commit regardless of how it was made.
  * When logical replication is unavailable (managed Postgres without
  * `wal_level=logical`, no replication privilege, no `REPLICA IDENTITY`), this
- * trigger-based fallback provides the same guarantee at the row level:
+ * trigger-based fallback provides the same guarantee:
  *
- *   AFTER INSERT/UPDATE/DELETE trigger  →  pg_notify('rebase_cdc', payload)
+ *   AFTER INSERT/UPDATE/DELETE/TRUNCATE statement trigger  →  pg_notify('rebase_cdc', payload)
+ *
+ * once per statement, naming the changed rows by key in batches of about a
+ * thousand — a 1M-row UPDATE is ~1,000 notifications, where a row trigger sent
+ * a million into Postgres's shared notification queue, to every instance.
  *
  * A single dedicated LISTEN client per backend instance consumes the channel
  * (see {@link CdcListener}) and feeds the change into the existing
@@ -21,29 +25,127 @@ import type { RawSqlRunner } from "../../security/rls-enforcement.js";
  */
 /** Postgres NOTIFY channel carrying database-level change events. */
 export declare const CDC_CHANNEL = "rebase_cdc";
-/** Schema-qualified name of the generic trigger function. */
+/**
+ * Schema-qualified name of the row-level trigger function: one notification
+ * per changed row. What every version before statement-level capture attached
+ * everywhere, and still what a partitioned or foreign table gets — see
+ * {@link levelForRelkind}.
+ */
 export declare const CDC_TRIGGER_FUNCTION = "rebase.rebase_cdc_notify";
-/** Name of the per-table trigger (unqualified — triggers are namespaced by table). */
+/**
+ * Schema-qualified name of the statement-level trigger function: one
+ * notification per ~1,000 changed rows. See {@link buildCdcFunctionSql}.
+ *
+ * A function of its own rather than a new body for the row function, because
+ * an instance of an older version replaces the row function's body every time
+ * it boots: a statement trigger calling it would then run a row trigger's body,
+ * for every write, until the next boot of this version.
+ */
+export declare const CDC_STATEMENT_FUNCTION = "rebase.rebase_cdc_notify_statement";
+/** Name of the per-table row-level trigger (unqualified — triggers are namespaced by table). */
 export declare const CDC_TRIGGER_NAME = "rebase_cdc_trigger";
+/** How a table is instrumented: one notification per statement's ~1,000 rows, or one per row. */
+export type CdcTriggerLevel = "statement" | "row";
+/** One trigger this module creates, as `pg_trigger` describes it. */
+interface CdcTriggerSpec {
+    name: string;
+    /** The function it calls. */
+    fn: "row" | "statement";
+    /** `CREATE TRIGGER` between the name and `ON`. */
+    timing: string;
+    /** `CREATE TRIGGER` between the table and `EXECUTE`. */
+    forEach: string;
+    /** `tgtype`: ROW (1), BEFORE (2), INSERT (4), DELETE (8), UPDATE (16), TRUNCATE (32), INSTEAD (64). */
+    type: number;
+    /** `tgnewtable` / `tgoldtable`: the transition tables it captures. */
+    newTable: string | null;
+    oldTable: string | null;
+}
+/**
+ * The statement-level triggers a plain table gets. One per event, because
+ * Postgres refuses transition tables on a trigger with more than one event.
+ * The TRUNCATE one is new with them: a row trigger never fires on `TRUNCATE`,
+ * so a truncated table used to be announced to nobody.
+ */
+export declare const CDC_STATEMENT_TRIGGERS: readonly CdcTriggerSpec[];
+/**
+ * The level a table is instrumented at, by `pg_class.relkind`.
+ *
+ * A plain table gets statement triggers. A partitioned table keeps the row
+ * trigger: Postgres clones a row trigger onto every partition, so a write made
+ * straight to a partition is still captured, while a statement trigger on the
+ * parent fires only for statements against the parent. A foreign table
+ * cannot have transition tables at all.
+ */
+export declare const levelForRelkind: (relkind: string | null | undefined) => CdcTriggerLevel;
 /**
- * SQL that (re)creates the generic CDC trigger function. Safe to run repeatedly:
- * `CREATE OR REPLACE` updates in place without dropping dependent triggers.
- *
- * The function emits `{ schema, table, op, row }`. The `row` is the full changed
- * tuple (NEW for insert/update, OLD for delete) so the consumer can route it to
- * a collection and extract the primary key. It is *not* trusted for delivery:
- * the consumer marks the row invalidated and each subscriber re-reads it under
- * its own RLS context, so a subscriber never receives a row it cannot read.
+ * How long after a boot first converts a table from the row trigger, the
+ * statement triggers still announce every change one row per notification.
+ *
+ * The triggers are the database's, and an instance of the previous version
+ * still running beside this one — a rolling deploy, a rollback — reads the
+ * same channel with a parser that knows one row per notification: given a
+ * batch it sees no key, so its lists refetch but its single-row and
+ * many-to-many subscribers hear nothing. While any such instance may be up,
+ * the statement triggers speak its protocol; after this window they batch.
+ * Every version that batches reads both. A boot of the older version re-attaches its row trigger (it
+ * creates a missing one), and the next boot of this one converts it back and
+ * re-opens the window, so a rollback is covered the same way.
  */
-export declare function buildCdcFunctionSql(): string;
+export declare const CDC_ROW_COMPAT_MS: number;
 /**
- * SQL that (re)attaches the CDC trigger to a single table. `DROP ... IF EXISTS`
- * before `CREATE` keeps it idempotent and picks up any function signature change.
+ * SQL that (re)creates both CDC trigger functions. Safe to run repeatedly:
+ * `CREATE OR REPLACE` updates in place without dropping dependent triggers —
+ * which is also how a database instrumented by an older version gets these
+ * bodies on its next boot, for every table at once, re-attached or not.
+ *
+ * Both functions emit `{ schema, table, op, ... }`, and the rows are named by
+ * **identity, never the tuple**. Postgres puts no privilege on `LISTEN`: any
+ * role that can connect can listen on this channel, whatever it may `SELECT`.
+ * When `row` was `to_jsonb(NEW)`, a login with no grant on anything received
+ * every changed row of every instrumented table — `password_hash` and
+ * verification tokens from the auth table included — past RLS and column
+ * grants. The consumer never read anything but the key: every subscriber
+ * re-reads the row under its own scope.
+ *
+ * The identity is, in order:
+ *  - the columns the trigger was attached with (`TG_ARGV`) — the key the
+ *    consumer addresses the row by, and for a junction table the two ids that
+ *    name the child list it changed; see {@link buildCdcTriggerSql};
+ *  - otherwise the table's primary key, read from the catalogue — a trigger
+ *    attached with no columns, by an older boot or on a table no collection
+ *    maps any more;
+ *  - otherwise `id`, if the table has one, and else nothing: a change the
+ *    consumer can only treat as collection-wide.
+ *
+ * `compatUntil` is the end of the window in which the statement function
+ * still sends one row per notification — see {@link CDC_ROW_COMPAT_MS}. A
+ * timestamp, or `-infinity` for none.
  */
-export declare function buildCdcTriggerSql(schema: string, table: string): string;
+export declare function buildCdcFunctionSql(options?: {
+    compatUntil?: string;
+}): string;
+/**
+ * SQL that (re)attaches the CDC triggers to a single table, at `level`.
+ * Every trigger this module owns is dropped first, whichever level it was
+ * created at, so a table moves between levels — a row trigger left by an
+ * older version becomes the statement triggers — in one transaction, with no
+ * moment at which a write is announced by neither.
+ *
+ * `identityColumns` are what the payload names the changed rows by — see
+ * {@link buildCdcFunctionSql}. Passed as trigger arguments, so one shared
+ * function serves every table. Empty means "the primary key".
+ */
+export declare function buildCdcTriggerSql(schema: string, table: string, identityColumns?: readonly string[], level?: CdcTriggerLevel): string;
 export interface CdcTableRef {
     schema: string;
     table: string;
+    /**
+     * The columns a change to this table is announced by — the collection's
+     * key columns, or a junction's two id columns. Absent means the primary
+     * key. Nothing else ever leaves the trigger; see {@link buildCdcFunctionSql}.
+     */
+    identityColumns?: string[];
 }
 export interface ProvisionResult {
     /** Tables the trigger was successfully attached to. */
@@ -54,11 +156,71 @@ export interface ProvisionResult {
     }>;
 }
 /**
- * Idempotently install the CDC trigger function and per-table triggers.
+ * Replace the already-installed trigger functions with the current bodies, and
+ * install nothing where there is none.
+ *
+ * For a process that owns the schema but is not provisioning capture on this
+ * boot — `REALTIME_CDC=off`, or no direct URL to listen on. The triggers an
+ * earlier boot attached keep firing whether anything consumes them or not, so
+ * a database instrumented by a version whose function put whole rows on the
+ * channel kept doing so, for every login that cares to `LISTEN`, until capture
+ * was switched back on. The statement function keeps its compatibility
+ * window. Returns whether a function was there to replace.
+ */
+export declare function refreshInstalledCdcFunction(run: RawSqlRunner): Promise<boolean>;
+/**
+ * Take change capture off the database: detach every capture trigger and drop
+ * both functions. Returns how many triggers were attached.
+ *
+ * For `REALTIME_CDC=off`. Capture switched off used to leave the triggers in
+ * place, so every write to every instrumented table still ran one and sent a
+ * notification on a channel nothing listened to. Nothing depends on them once
+ * capture is off: a process without capture announces its own writes on the
+ * cross-instance channel, and the instances that serve realtime listen there.
+ *
+ * `DROP FUNCTION … CASCADE` takes the triggers with it in one statement. It
+ * waits for each table's lock like any trigger DDL, so it runs with the boot's
+ * lock budget and is retried on a lock timeout; a database still contended
+ * after that keeps its triggers and the caller reports it.
+ */
+export declare function removeTriggerCdc(run: RawSqlRunner): Promise<number>;
+/**
+ * What a boot that does not provision capture does with capture an earlier
+ * boot installed.
+ *
+ *  - `capture: "off"` — `REALTIME_CDC=off` — removes it ({@link removeTriggerCdc}).
+ *  - `capture: "not-provisioned"` — capture is wanted but this boot could not
+ *    install it (no direct URL, `auto` fell back) — leaves the triggers and
+ *    brings the functions up to date ({@link refreshInstalledCdcFunction}),
+ *    since they keep firing.
+ */
+export declare function settleInstalledCapture(run: RawSqlRunner, options: {
+    capture: "off" | "not-provisioned";
+}): Promise<{
+    removed: number;
+} | {
+    refreshed: boolean;
+}>;
+/**
+ * Idempotently install the CDC trigger functions and per-table triggers.
+ *
+ * A plain table gets the statement-level triggers, a partitioned or foreign
+ * one the row trigger ({@link levelForRelkind}). A table whose triggers are
+ * already exactly the ones this would create — same function, same events,
+ * enabled, same identity arguments — is left alone; one with a trigger
+ * missing, disabled, attached with different arguments or at the other level
+ * is (re-)attached, all of it in one transaction.
+ *
+ * Converting a table from a row trigger an older version attached opens the
+ * statement function's compatibility window ({@link CDC_ROW_COMPAT_MS}): the
+ * instances that attached it may still be listening.
  *
  * Runs as the owner (server) connection at bootstrap. A table that does not yet
  * exist in the database (schema drift) is skipped with a warning rather than
  * aborting the whole install, so one un-migrated collection cannot disable CDC
  * for the rest.
  */
-export declare function provisionTriggerCdc(run: RawSqlRunner, tables: CdcTableRef[]): Promise<ProvisionResult>;
+export declare function provisionTriggerCdc(run: RawSqlRunner, tables: CdcTableRef[], options?: {
+    now?: number;
+}): Promise<ProvisionResult>;
+export {};

package/dist/services/channel-bus/PostgresChannelBus.d.ts

@@ -6,13 +6,15 @@
  * properties of `NOTIFY` shape everything below:
  *
  *  - **8000 bytes per payload.** Presence and cursors fit with room to spare; a
- *    scene snapshot does not. Rather than truncate or drop, an oversized frame
- *    on a *retained* channel is published as a pointer — the body is already in
- *    `rebase.channel_messages` with a sequence number, so the receiver reads it
- *    back. That is the same trick the entity path uses (notify an address,
- *    refetch the row), applied to a different table. On an ephemeral channel
- *    there is nothing to point at, so the publish is refused loudly instead of
- *    reaching some instances and not others.
+ *    scene snapshot does not. A message on a *retained* channel never travels
+ *    here at all, whatever its size: the statement that numbers it notifies a
+ *    pointer — the body is already in `rebase.channel_messages` with a sequence
+ *    number, so the receiver reads it back (`ChannelHistoryStore.append`). That
+ *    is the same trick the entity path uses (notify an address, refetch the
+ *    row), applied to a different table, and for the same reason: any database
+ *    login can `LISTEN`. On an ephemeral channel there is nothing to point at,
+ *    so the frame carries the message, and an oversized one is refused loudly
+ *    instead of reaching some instances and not others.
  *
  *  - **A notify is a query on the primary database.** Not a slow one, but it
  *    competes with the application's real queries, and that — not throughput —
@@ -26,6 +28,7 @@
  *    than correctness. That is what makes coalescing safe.
  */
 import { NodePgDatabase } from "drizzle-orm/node-postgres";
+import { type PgNotifyListenerStatus } from "../pg-notify-listener.js";
 import { ChannelBus, ChannelBusFrame, ChannelBusHandler } from "./ChannelBus.js";
 /** NOTIFY channel carrying channel-bus frames. */
 export declare const CHANNEL_BUS_NOTIFY_CHANNEL = "rebase_channel_bus";
@@ -79,6 +82,8 @@ export declare class PostgresChannelBus implements ChannelBus {
      * still holds.
      */
     publish(frame: ChannelBusFrame): Promise<void>;
+    /** The LISTEN connection's state, for `/health` — see {@link PgNotifyListener}. */
+    status(): PgNotifyListenerStatus | undefined;
     stop(): Promise<void>;
     private openWindow;
     /** Send everything queued and settle the promises waiting on it. */

package/dist/services/channel-bus/index.d.ts

@@ -36,7 +36,7 @@ export interface ChannelBusDeps {
  * transports this package knows how to construct, so honouring it there would
  * mean silently discarding the object the application handed us.
  */
-export declare function resolveChannelBusSetting(configured?: ChannelBusSetting): ChannelBusSetting;
+export declare function resolveChannelBusSetting(configured?: ChannelBusSetting, env?: NodeJS.ProcessEnv): ChannelBusSetting;
 /**
  * Produce the bus a setting asks for.
  *

package/dist/services/channel-history.d.ts

@@ -53,6 +53,22 @@ export interface ResolvedRetention {
     limit?: number;
     ttlMs?: number;
 }
+/**
+ * A bus frame to send in the statement that numbers a retained message — see
+ * {@link ChannelHistoryStore.append}.
+ *
+ * It is always a pointer, `{ kind: "broadcast_ref", sid, channel, seq }`, and
+ * never the message. Postgres puts no privilege on `LISTEN`, so a NOTIFY payload
+ * reaches every role that can connect to the database; the body stays in
+ * `rebase.channel_messages`, behind the table grants, and each receiving
+ * instance reads it back by `(channel, seq)` — the sender's id with it.
+ */
+export interface RetainedAnnouncement {
+    /** The NOTIFY channel the bus listens on. */
+    notifyChannel: string;
+    /** The sending instance. */
+    sid: string;
+}
 /**
  * Persistence and replay for retained channels.
  *
@@ -63,10 +79,21 @@ export interface ResolvedRetention {
 export declare class ChannelHistoryStore {
     private db;
     private rules;
-    /** Resolved rule per channel name, so the match runs once per channel. */
-    private resolved;
-    /** Channel → timestamp of its last prune, for {@link PRUNE_THROTTLE_MS}. */
+    /**
+     * Each rule with its retention resolved, once. Matched per call rather
+     * than cached per channel name: a cache keyed by the names clients invent
+     * grew by every one of them for the life of the process, and matching a
+     * handful of prefixes costs less than the hashing a lookup does.
+     */
+    private resolvedRules;
+    /**
+     * Channel → timestamp of its last prune, for {@link PRUNE_THROTTLE_MS}.
+     * An entry older than the window throttles nothing, so they are swept once
+     * a window: the map holds the channels pruned recently, not every channel
+     * ever pruned.
+     */
     private lastPruned;
+    private nextPruneSweepAt;
     private tablesReady;
     constructor(db: NodePgDatabase<Record<string, unknown>>, rules?: ChannelRetentionRule[]);
     /** Whether any channel retains anything at all. */
@@ -91,7 +118,7 @@ export declare class ChannelHistoryStore {
      * broadcasts to one channel line up in a single order — and what keeps
      * different channels from contending with each other at all.
      */
-    append(channel: string, event: string, payload: unknown, senderId?: string): Promise<{
+    append(channel: string, event: string, payload: unknown, senderId?: string, announce?: RetainedAnnouncement): Promise<{
         seq: number;
         at: string;
     }>;
@@ -124,6 +151,6 @@ export declare class ChannelHistoryStore {
      * volume, which is what makes retention affordable on a hot channel.
      */
     prune(channel: string, retention: ResolvedRetention): Promise<number>;
-    /** Forget throttle and match caches. Called on shutdown. */
+    /** Forget the prune throttle. Called on shutdown. */
     clear(): void;
 }

package/dist/services/collection-helpers.d.ts

@@ -1,5 +1,5 @@
 import { PgTable, AnyPgColumn } from "drizzle-orm/pg-core";
-import { SQL } from "drizzle-orm";
+import { type SQL } from "drizzle-orm";
 import { CollectionConfig, ResolvedHasMany, ResolvedHasOne } from "@rebasepro/types";
 import { PostgresCollectionRegistry } from "../collections/PostgresCollectionRegistry.js";
 import { ApiError } from "@rebasepro/server";
@@ -133,6 +133,31 @@ export declare function getPrimaryKeys(collection: CollectionConfig, registry: P
  * wrong and which collection it is wrong about.
  */
 export declare function requirePrimaryKeys(collection: CollectionConfig, registry: PostgresCollectionRegistry): PrimaryKeyInfo[];
+/**
+ * The table's key columns, in key order.
+ *
+ * Throws when there are none, or when the table has no column for one of them:
+ * a WHERE built from fewer columns than the key matches every row that shares
+ * the columns it did find, so there is no partial answer worth returning.
+ *
+ * @param collectionPath named in the error.
+ */
+export declare function primaryKeyColumns(table: PgTable, primaryKeys: PrimaryKeyInfo[], collectionPath: string): AnyPgColumn[];
+/**
+ * The column a `joinPath` step names, on a table that may key it either way.
+ *
+ * A `JoinStep` is written in database terms — `on: { from: "author_id" }` —
+ * because there is no collection to translate through: the step names a raw
+ * table. A table the boot reads back out of the catalogue is keyed by the
+ * *wire* name, `authorId`, while a hand-written Drizzle schema may key it by
+ * the column name. Looking the step's name up as a key therefore found
+ * nothing on every booted table, and a `via` relation loaded nothing at all.
+ *
+ * The key first, as the step may already name one; then the column whose SQL
+ * name it is. `undefined` when the table has neither, which the caller turns
+ * into an error naming the step.
+ */
+export declare function columnNamed(table: PgTable, name: string): AnyPgColumn | undefined;
 /**
  * The column on the *source* table that a `hasOne`/`hasMany` link points at.
  *

package/dist/services/field-viewer.d.ts

@@ -1,4 +1,5 @@
-import type { FieldViewer } from "@rebasepro/common";
+import { type FieldViewer } from "@rebasepro/common";
+import type { CollectionConfig } from "@rebasepro/types";
 /**
  * Run `fn` with `viewer` as the caller every row strip judges against.
  *
@@ -17,3 +18,16 @@ export declare function withFieldViewer<T>(viewer: FieldViewer | undefined, fn:
  * that is what establishes the viewer.
  */
 export declare function currentFieldViewer(): FieldViewer | undefined;
+/**
+ * The names an API caller's query may not see on `collection`: its
+ * `excludeFromApi` fields, in every spelling. Empty on the trusted server plane
+ * (no viewer), which may filter and sort on those columns — the auth adapter
+ * looks rows up by them — and empty with no collection in hand.
+ *
+ * A query naming one of these is answered exactly as a query naming a column
+ * the table does not have. The REST check passes such a name through to this
+ * driver rather than refusing it itself, so the two answers come from one throw
+ * and cannot drift: a "not readable" there would confirm a column OpenAPI and
+ * `list_collections` hide.
+ */
+export declare function namesHiddenFromCaller(collection: CollectionConfig | undefined): ReadonlySet<string>;

package/dist/services/pg-notify-listener.d.ts

@@ -3,11 +3,11 @@
  *
  * Every cross-instance feature in the backend needs the same thing: one
  * connection *outside* the Drizzle pool that stays open, holds a `LISTEN`, and
- * comes back on its own after the database or the network drops it. CDC needed
- * it first; the channel bus needs it too. This is that connection, with the one
- * behaviour that matters to callers preserved: the **first** connect is
- * validated and rethrown, so a caller can fall back to a different strategy,
- * while every later drop is repaired quietly in the background.
+ * comes back on its own after the database or the network drops it. CDC, the
+ * channel bus and the cross-instance broadcast all use this one. By default the
+ * **first** connect is validated and rethrown, so a caller can fall back to a
+ * different strategy, while every later drop is repaired quietly in the
+ * background; `retryInitialConnect` repairs the first one the same way.
  *
  * `LISTEN` is session state, so this connection must not go through a
  * transaction-mode pooler (PgBouncer): give it the direct database URL.
@@ -30,25 +30,114 @@ export interface PgNotifyListenerOptions {
      * gone for good; a caller that mirrors state from the channel resyncs here.
      */
     onReconnect?: () => void;
+    /**
+     * How often the connection proves it is alive with a round trip. `0`
+     * turns the heartbeat off. See {@link PgNotifyListener} for why it exists.
+     */
+    heartbeatIntervalMs?: number;
+    /** How long a heartbeat may take before the connection is declared dead. */
+    heartbeatTimeoutMs?: number;
+    /**
+     * Treat a failed first connect like any later drop: `start()` resolves,
+     * the listener reports itself down, and it keeps dialling in the
+     * background. For a caller with nothing to fall back to, for whom a
+     * database that is unreachable at boot is an outage to wait out rather
+     * than a reason to run without the channel. Off by default: `start()`
+     * rejects, so a caller with a fallback can take it.
+     */
+    retryInitialConnect?: boolean;
+    /**
+     * The `application_name` the connection reports in `pg_stat_activity`.
+     * Visible to every role, which is what lets one instance count the others
+     * (see `RealtimeService.warnIfMemoryBusOnMultiplePods`). A connection
+     * string that sets its own `application_name` wins.
+     */
+    applicationName?: string;
+}
+/**
+ * What a listener can say about itself — read by `/health`.
+ *
+ * `connected` is "listening, and the last heartbeat answered", not "a socket
+ * object exists": a half-open connection has a perfectly good socket object.
+ */
+export interface PgNotifyListenerStatus {
+    channel: string;
+    connected: boolean;
+    /** Since when (epoch ms) it has been down, while it is down. */
+    downSince?: number;
+    /** When (epoch ms) it last answered a heartbeat. */
+    lastHeartbeatAt?: number;
 }
+/**
+ * Below every common idle-flow timeout: Azure's load balancer drops an idle
+ * flow at 4 minutes, AWS's NLB at 350 s, and NAT and conntrack tables and
+ * pooler-side reapers are often shorter. A LISTEN connection is idle by
+ * nature, so it is exactly the connection those timeouts kill.
+ */
+export declare const DEFAULT_HEARTBEAT_INTERVAL_MS = 30000;
+export declare const DEFAULT_HEARTBEAT_TIMEOUT_MS = 10000;
+/**
+ * A half-open connection — one whose packets stop arriving, with no FIN and no
+ * RST, which is what an idle-flow timeout on a load balancer, a NAT, a dead
+ * middlebox or a failed-over network looks like — fires no `error` and no
+ * `end`. The connection object stays, `LISTEN` stays registered on a backend
+ * that may no longer exist, and every notification from then on is lost: CDC,
+ * the cross-instance broadcast and the channel bus all went quiet with no
+ * error, no reconnect and a green `/health`, while writes made through this
+ * instance still looked live because they are delivered locally.
+ *
+ * So the connection proves itself: TCP keepalive is on, and every
+ * {@link DEFAULT_HEARTBEAT_INTERVAL_MS} a `SELECT 1` must come back within
+ * {@link DEFAULT_HEARTBEAT_TIMEOUT_MS}. One that does not is torn down and
+ * replaced, and `onReconnect` resyncs whatever was missed.
+ */
 export declare class PgNotifyListener {
     private readonly options;
     private client?;
     private running;
     private reconnectTimer?;
+    private heartbeatTimer?;
+    private heartbeatInFlight;
+    private downSince?;
+    private lastHeartbeatAt?;
     constructor(options: PgNotifyListenerOptions);
     /** Whether the listener is meant to be connected right now. */
     get active(): boolean;
+    /** Whether it is listening on a connection that answered its last heartbeat. */
+    get connected(): boolean;
+    status(): PgNotifyListenerStatus;
     /**
      * Connect and begin listening. Idempotent.
      *
      * Rejects if the *initial* connection or `LISTEN` fails, leaving the
      * listener stopped — callers use that to degrade deliberately instead of
-     * running blind against a channel nothing is delivering.
+     * running blind against a channel nothing is delivering. With
+     * `retryInitialConnect` it resolves instead, reports itself down, and
+     * keeps dialling.
      */
     start(): Promise<void>;
     /** Stop listening and release the connection. Idempotent. */
     stop(): Promise<void>;
+    /**
+     * @param first The connect `start()` makes: never a reconnect, so it owes
+     *        no resync, and — unless `retryInitialConnect` — a failure is
+     *        thrown to the caller rather than retried.
+     */
     private connect;
+    /**
+     * Give up on the current connection: it is no longer the listener's, so
+     * its late events are ignored and `connected` says so at once; it is
+     * ended without waiting on it; and a replacement is scheduled.
+     */
+    private abandon;
+    private startHeartbeat;
+    private stopHeartbeat;
+    /**
+     * One round trip on the LISTEN connection. Not answered in time, it is
+     * treated as dead: the client is ended — which, with the query still
+     * outstanding, destroys the socket rather than waiting on a goodbye that
+     * cannot arrive — and replaced.
+     */
+    private heartbeat;
     private scheduleReconnect;
 }