@jam-overture/loom/signals/postgres

The Postgres buffer and counters, for a deployment that keeps what its readers did.

Everything below is exported from that import. The names, the signatures and the sentences are read from the package itself rather than written here, so this page says what the copy of Loom in your node_modules says — and it changes in the same pull request the code does.

5 exports, in 2 modules. Generated from ./dist/signals/postgres.d.ts, which is the declaration file this package publishes for @jam-overture/loom/signals/postgres.

Install this first. @jam-overture/loom/signals/postgres loads it the moment the import runs. Without it, the import itself fails — before any of your own code has run.

drizzle-orm^0.45.2optional peer dependency

pnpm add drizzle-orm

No import here has everything behind it. @jam-overture/loom/signals/postgres publishes 5 of the 1,298 names this package publishes. The other 1,293 are behind one of the 16 other imports, and not one of those imports publishes a single name this one does. The imports do not nest: a name that is not on this page is not a name that does not exist, and the search at the top of the page says which import it comes from.

Migrate

signals/migrate

Creating the five reader-signal tables, with row level security switched on.

READER_SIGNALS_DDLvalue

The five tables, as statements a host can run.

const READER_SIGNALS_DDL: readonly string[]

ensureReaderSignalsSchemafunction

Idempotent, so running it against a populated database is a no-op.

const ensureReaderSignalsSchema: (db: LoomDatabase) => Promise<void>

Postgres

signals/postgres

The Drizzle tables are **not** re-exported, unlike the journal's.

postgresReaderSignalJournalfunction

const postgresReaderSignalJournal: (db: LoomDatabase) => ReaderSignalJournal

postgresReaderTallyStorefunction

const postgresReaderTallyStore: (db: LoomDatabase) => ReaderTallyStore

postgresReaderRegionStorefunction

const postgresReaderRegionStore: (db: LoomDatabase) => ReaderRegionStore