@cozycodr/lipila-store-postgres

Preview PostgreSQL adapter for Lipila lifecycle state. Install it with its peer driver:

npm install @cozycodr/lipila-store-postgres pg

import { postgresPaymentStore } from "@cozycodr/lipila-store-postgres";

const store = postgresPaymentStore({
  connectionString: process.env.DATABASE_URL!,
  namespace: "lipila:sandbox:merchant-123",
});
await store.migrate();

Pass either connectionString or an existing pg.Pool, never both. close() closes only a pool created from connectionString; caller-owned pools remain open. Migrations are explicit, repeatable, forward-only, and never run during payment handling.

This package remains preview until the real PostgreSQL multi-process conformance and migration-upgrade release gates pass.

Webhook leases expire on the database clock, not the application's, so a worker with a skewed clock cannot take over a lease that is still live. The default lease is 30 seconds; set leaseMs above your slowest webhook handler.

Test against PostgreSQL

The suite skips unless LIPILA_POSTGRES_TEST_URL is set. It uses a unique namespace per run and deletes only rows in that namespace — it never drops a database, schema, or table.

LIPILA_POSTGRES_TEST_URL='postgresql://postgres:[email protected]:5432/lipila_test' \
  npm run test:integration -w @cozycodr/lipila-store-postgres

It covers two layers: the shared store conformance suite, and SDK-level lifecycle behaviour driven through a real client — handler retry after a failure, no concurrent re-run when a lease is taken over, and duplicate acknowledgement. Those paths depend on real transactions, SELECT … FOR UPDATE row locks, and database-clock lease expiry, none of which the in-memory adapter can reproduce.