Skip to Content
TwinsPostgreSQL

PostgreSQL

A real embedded PostgreSQL cluster, reached over the native wire protocol.

Your application’s own database: a real PostgreSQL cluster your code connects to over the native wire protocol.

ProtocolPostgreSQL wire
AuthPostgres role auth

Coverage

This is not a twin of a vendor API, so there is no manual and no operation list to browse. The control plane still gives you schema, seed and reset.

The schema is whatever you create. It is introspected from the live tables rather than declared, and you seed it with DDL rather than rows. See Seeding.

Your connection string arrives in your command’s environment as DATABASE_URL, pointing at the cluster’s own network address rather than the HTTP gateway. A DATABASE_URL you set yourself still wins.

Credentials

Your existing role and password work by default: the first connection with a well-formed credential creates the login role. Set auth to enforced to demand the credential the world holds. See Credentials.

Under enforced auth a wrong password is Postgres’s own 28P01, arriving on the wire protocol rather than as an HTTP status.

Vendor specific details

  • Nothing here stands in for a database. Migrations, extensions, transactions, locks and query plans all behave the way they do in production, because it is the same Postgres.
  • The proxy never sees this traffic. Your connection goes straight to the cluster, so database calls do not appear alongside your intercepted HTTP calls.
  • A sandbox reset drops open database connections. Pooled clients have to reconnect afterwards.
NotionQuickBooks