1. dialects
prorm
  • prorm documentation
  • Known test gaps
  • Architecture
  • Core concepts
  • Database types & coverage
  • Getting started
  • Going further
  • compliance
    • Compliance
    • The security toolkit: `prorm audit`
    • Checklists by regulation
    • Declaring personal data
    • Evidence bundles
    • Evidence
    • Frameworks: `@Security`
    • Jurisdictions
    • Platform policies
    • Protecting data
    • The regulation dataset
    • Residency and cross-border transfers
    • Retention & integrity
    • Status
    • Subject rights
  • decorators
    • prorm with decorators
    • Models with decorators
    • Querying a decorated model
    • Relations with decorators
  • diagrams
    • Diagram generators
    • Chen diagram
    • Class diagram
    • Dependency diagram
    • ER diagram
    • Flow diagram
    • From your models to a diagram
    • Gantt diagram
    • Index diagram
    • Migration diagram
    • Model diagram
    • Package diagram
    • Crow’s-foot diagram
    • Schema documentation
    • Sequence diagram
    • State diagram
    • Tree diagram
  • dialects
    • SQL dialects
    • AlloyDB Dialect
    • AlloyDB Omni Dialect
    • Amazon Athena Dialect
    • Aurora DSQL Dialect
    • Amazon Aurora MySQL Dialect
    • Amazon Aurora PostgreSQL Dialect
    • Azure Database for MySQL Dialect
    • Azure Database for PostgreSQL Dialect
    • Azure SQL Database Dialect
    • Azure SQL Managed Instance Dialect
    • Google BigQuery Dialect
    • Citus Dialect
    • ClickHouse dialect
    • Cloud Authentication (`cloud-auth`)
    • Cloud SQL for SQL Server Dialect
    • Cloud SQL for MySQL Dialect
    • Cloud SQL for PostgreSQL Dialect
    • CockroachDB Dialect
    • Azure Cosmos DB for PostgreSQL Dialect
    • CrateDB Dialect
    • Cloudflare D1 Dialect
    • Databricks dialect
    • IBM Db2 Dialect
    • Dolt Dialect
    • Apache Doris Dialect
    • Druid Dialect
    • DuckDB Dialect
    • Exasol dialect
    • Microsoft Fabric Data Warehouse Dialect
    • Firebird Dialect
    • Greenplum Dialect
    • SAP HANA Dialect
    • MySQL HeatWave Dialect
    • Azure Data Explorer (Kusto) Dialect — T-SQL
    • MariaDB Dialect
    • Materialize Dialect
    • MonetDB Dialect
    • MotherDuck Dialect
    • Microsoft SQL Server Dialect
    • MySQL Dialect
    • Neon Dialect
    • OceanBase Dialect
    • openGauss Dialect
    • Oracle Dialect
    • Oracle Autonomous Database Dialect
    • ParadeDB Dialect
    • PolarDB Dialect
    • PostgreSQL Dialect
    • Presto Dialect
    • QuestDB Dialect
    • Aurora RDS Data API Dialect (`rdsdata`)
    • Amazon RDS for Db2 Dialect
    • Amazon RDS for MariaDB Dialect
    • Amazon RDS for SQL Server Dialect
    • Amazon RDS for MySQL Dialect
    • Amazon RDS for Oracle Dialect
    • Amazon RDS for PostgreSQL Dialect
    • Amazon Redshift
    • Amazon Redshift Data API Dialect
    • RisingWave Dialect
    • rqlite Dialect
    • SingleStore Dialect
    • Snowflake Dialect
    • Google Cloud Spanner Dialect
    • Spanner (PostgreSQL interface) Dialect
    • SQLite Dialect
    • StarRocks Dialect
    • Supabase Dialect
    • Azure Synapse Analytics (dedicated SQL pool)
    • Teradata Dialect
    • TiDB Dialect
    • TimescaleDB Dialect
    • Trino Dialect
    • Turso / libSQL Dialect
    • Vertica dialect
    • Vitess Dialect
    • Yellowbrick Dialect
    • YugabyteDB Dialect
  • guides
    • Access rules and behaviour profiles
    • ArangoDB (AQL)
    • Associations
    • Audit levels and escalation
    • Audit logging
    • In the browser
    • Bulk operations
    • Caching
    • Capabilities, tiers and team roles
    • CLI
    • Cloudflare
    • Compliance & data protection
    • Connection Pooling & Performance
    • Security in the console
    • Couchbase: structured N1QL queries
    • Data types
    • Decorators
    • Eager loading
    • Enums and constants
    • Error handling & error types
    • Extensions
    • External fields
    • Foreign data wrappers
    • Graph databases
    • Hooks & lifecycle events
    • Indexes & constraints
    • InfluxDB: structured Flux pipelines
    • klock-errors
    • klock — the `.klock` file
    • Local databases (`prorm db up`)
    • Structured log search — Splunk, Graylog, Papertrail, Sumo Logic
    • Logging
    • Grafana Loki: structured LogQL queries
    • MCP server
    • Migrate — the data transfer subsystem
    • Migrations & Schema Sync
    • Models from an existing database
    • Defining models
    • Multiple databases
    • OrientDB, Neptune and TigerGraph
    • Passwords
    • Importing a Prisma schema
    • Structured PromQL and MetricsQL
    • Query firewall
    • QueryInterface
    • Query operators reference
    • Query optimization
    • Composing find options with `pipe()` and `Q`
    • Query safety: the fail-closed WHERE guard
    • Querying
    • Raw Queries & Query Building
    • Read replicas
    • Schema diffing & migration generation
    • Views, triggers & other schema objects
    • Scopes & default scopes
    • Seeders
    • SPARQL / RDF triplestores
    • SQL constants
    • SQL features
    • SQL function builders
    • SQLite advanced features
    • StoreKey — a prod-orm database as the storage
    • Streaming results
    • Terraform
    • Transactions & Isolation Levels
    • Type mapping: legacy and modern
    • TypeScript types
    • Database users, roles & privileges
    • Validation & constraints
    • Virtual & Computed Fields
    • Writing docs
  • javascript
    • prorm in JavaScript
    • Models in JavaScript
    • Querying in JavaScript
    • Relations in JavaScript
  • runbooks
    • Operational runbooks
    • Connection failures
    • Credential rotation
    • Failover
    • Incident checklist
    • Deploying klock v2
    • Migration rollback
  • running-databases
    • Running databases in Docker
    • Running prorm under Bun in Docker
    • Running Cassandra in Docker with prorm
    • Running ClickHouse in Docker with prorm
    • Running CockroachDB in Docker with prorm
    • Running prorm under Deno in Docker
    • Running Elasticsearch in Docker with prorm
    • Running MariaDB in Docker with prorm
    • Running MongoDB in Docker with prorm
  • prorm control plane
    • Introduction
    • Authentication
    • Errors
    • Getting started
      • Service
        • Is it up
        • This description
    • Account
      • Sign-up and verification
        • Create an account
        • Exchange credentials for a token
        • Verify with the emailed code
        • Verify by clicking the emailed link
        • Name the parent or guardian
        • What a consent link is about
        • Give consent for a child's account
        • Ask the parent or guardian again
        • Send a new code and link
      • Family
        • Everyone this account is responsible for
        • One child, in detail
        • Turn a limit on or off
      • Profile
        • Who am I
        • Change the account
        • Every address on the account
        • Add an address
        • Confirm an address with the code mailed to it
        • Mail a fresh code to an unconfirmed address
        • Make an address primary
        • Remove an address
        • What this caller may do
    • Security
      • Sessions
        • Everywhere this account is signed in
        • Sign out everywhere else
        • Sign one out
        • A token for the CLI on a named machine
        • A token for the customer console, from the staff one
        • Park a sign-in for the CLI to collect
        • The CLI collecting its sign-in
        • The team's members' live sessions
        • Sign a member's session out
        • Sign an account out everywhere
        • Everywhere the account is signed in
        • Sign an account's session out
      • Single sign-on
        • Begin a single sign-on
        • The provider's return
        • Link the signed-in account to a team's provider
        • Which team an address signs in to
        • The team's single sign-on, as a member sees it
        • Set the team's OpenID Connect provider up, or change it
        • Remove the provider
        • The team's domain claims and the DNS record each needs
        • Prove a claimed domain
      • MFA and passwords
        • Start enrolling a second factor
        • Prove the app has it
        • Remove the second factor
        • Ask for a reset link
        • Set a new password with the emailed token
      • Klock
        • Open a device-bound klock session
        • Check in, for the next grant
        • Step up the session asking
        • Rotate the device key
        • Freeze a session
        • Unfreeze a session
        • A guest grant
        • The revocation feed
        • The published keyset
        • What this control plane supports
      • Devices
        • Your devices, or a team's
        • Approve a new device's pairing code
        • One device
        • Rename a device
        • Revoke a device
        • Suspend a device
        • Reinstate a suspended device
        • Wipe a device
        • Ask a device to rotate its key
        • The team's members' devices
        • Revoke a member's device
        • An account's devices
        • Revoke an account's device
        • Wipe an account's device
        • The device fleet
      • Access rules and behaviour
        • The access rules that bear on you
        • Add an access rule
        • This request, as the rules see it
        • One access rule
        • Remove an access rule
        • The behaviour profiles that bear on you
        • Add or change a behaviour profile
        • The profile presets
        • Your behaviour findings
        • Acknowledge a finding
        • One behaviour profile
        • Remove a behaviour profile
        • The team's access rules
        • Add a team access rule
        • Remove a team access rule
        • The team's behaviour profiles
        • Add or change a team behaviour profile
        • Remove a team behaviour profile
        • What the team's profiles caught
        • Acknowledge a team finding
      • Recovery and lockdown
        • Ask for a recovery link
        • Recover access with the emailed code
        • Is the account locked down
        • Lock the account down
        • Release a lockdown
        • Lock a member down
        • Release a member's lockdown
      • MCP tokens
        • Make a delegated token for one MCP client
        • The account's delegated tokens
        • Revoke a delegated token
        • What a delegated token may do now
        • Run one MCP tool with a delegated token
        • Run a device-signed MCP tool call relayed by the MCP Worker
      • Kerberos
        • Give the team its own Kerberos realm
        • The team's realm
        • Remove the team's realm
    • Logging and monitoring
      • Audit log
        • What has been done to the account
        • What has happened to this account
        • The account's audit trail
      • Operations
        • Everything that has been asked of this database
        • One, with its steps
        • Stop it
        • Put a failed one back in the queue
        • Every operation, across all accounts
      • Metrics and events
        • Every measurement, for a graph
        • Who did what to it
    • Billing
      • Plans and pricing
        • What the plans allow
        • The rate card
        • What one database would cost
        • What this account is paying for, itemised
      • Subscriptions and invoices
        • What this month's invoice will say
        • What this account is on
        • What it has been charged
        • Start a Stripe Checkout session
        • Open the customer portal
        • Stripe's events
        • Buy more connection pools
      • Team billing
        • The team's billing account
        • What the team has been charged
        • What this month's invoice will say
        • The team's cards
        • Add a card, through a Stripe-hosted setup session
        • Make a card the team's default
        • Remove a card
        • Start the team paying
        • Open the Stripe portal on the team's customer
        • Change the team's plan
        • Who receives the team's bills
        • How the team pays for transfers
    • Support
      • Support chat
        • My conversations
        • Start a conversation
        • Every support conversation, open first
        • A ticket for the socket
        • One conversation, with who is in it and who is connected
        • Rename a group; open or close a support conversation
        • The lines, oldest first
        • Say something
        • Add somebody
        • Mark read
    • Administration
      • Users
        • Every account
        • One account, with everything hanging off it
        • Grant or revoke admin
        • Verify an account by hand
        • Lock or unlock sign-in
        • Allow or hold provisioning
        • Send the verification mail again
        • Set the plan by hand
      • Platform
        • Every database and store, across all accounts
        • The counts worth putting on a dashboard
      • Staff and permissions
        • What kind of admin the caller is, and which scopes they hold
        • The admin presets
        • Every admin, and the scopes each resolves to
        • Make an account an admin of a kind
        • Change an admin's kind, or a custom admin's scopes
        • Revoke admin
      • Team administration
        • Every team, with its owner and size
        • One team in full — members with their accounts, and projects
        • Hand the team to another member
        • Put an account in the team, active at once
        • Change a member's role
        • Remove a member
      • Assumed identities
        • Assume an identity — act as a customer account
        • The identities the caller holds open
        • End an assumed identity
      • Support inbox
        • The platform's addresses
        • Add a platform address
        • One address, with its counts
        • Change an address's label, routing, or whether it accepts mail
        • Remove an address that holds no mail
        • Make, adopt or repair the address's routing rule
        • Every admin's personal address, made where missing
        • File a raw message, as if it had arrived
        • The inbox
        • One message, whole
        • Mark a message
        • Hand a message to an admin, or take it back
        • Leave an internal note
        • Reply, from the address the message came to
        • What is waiting
    • Databases
      • Databases
        • Data stores
          • Every data store on the account
          • Provision a data store
          • Change a data store that is already running
          • One data store
          • Deprovision it
          • Report what it is using
          • How to reach a data store
        • Connections and credentials
          • The api keys on a database
          • Issue a key
          • Revoke a key
          • The engine users we created
          • Create a user inside the database
          • Give a user a new password
          • Drop a user
          • How the database is reached
          • Set how it is reached
          • Revoke every api key on it
          • How to connect to it
          • The ssh keys that open its bastion
          • Add a key, or have one made
          • The private half of a generated key, once
          • Revoke an ssh key
        • Schema and objects
          • The SQL objects we put in it
          • Create one, and apply it
          • What is in the database, as the engine reports it
          • One table
          • What it would run, without running it
          • Redefine an object in place
          • Drop it
          • The extensions installed in it
        • Migrations
          • A plan compiled to statements, recording nothing
          • The migrations recorded for it
          • Record one
          • Apply everything recorded and not yet run
          • Apply everything pending, oldest version first
        • Lifecycle
          • Grow or shrink it
          • Stop it accepting connections
          • Start it again
          • Move it to another region
        • Backups and replicas
          • Take a backup
          • The backups it has
          • Restore one into it
          • What has been restored into it, and from where
          • Its read copies
          • Add one
        • Policies
          • The catalog
          • One policy
          • What this database is held to
          • Switch a policy on, or change its knobs
          • Switch it off
          • Mark the policies reviewed
          • Evaluate the periodic policies now
          • Who is behind a credential
        • Passwordless
          • The database's passwordless sessions
          • Issue a passwordless session (v1)
          • Revoke a passwordless session
          • Bind a session to a device key
          • Issue a v2 session for a host to bind
          • Redeem an enrolment ticket on the host
          • Check a passwordless credential
          • Run one described query under a passwordless credential
        • Database roles
          • The database's roles
          • Define a role
          • One role
          • Change what a role permits
          • Delete a role, and revoke every key granted it
          • Grant a role, which mints a key
          • Who holds a role
          • The api keys bound to a role
        • Pools
          • A database's connection pools, and how busy each is
          • Open another pool
          • Rename a pool or change its size
          • Close a pool
        • Data plane
          • Run a query against a database
          • Several statements, in order, over one connection
          • Is this database answering
          • What the proxy itself is holding
        • Transfers
          • The strategies this account's tier may use
          • Price a transfer without creating it
          • The account's transfer jobs, newest first
          • Create a transfer job
          • One job, and whether its certificate holds
          • Cancel an unfinished job
          • Start a created job, confirming its price
          • Report a job's status (the runner, or the owner's side of a local run)
        • Every database on the account
        • Provision a database
        • Change a database that is already running
        • One database
        • Deprovision it
        • Read or write it
        • Report what it is using
        • The engines this API will provision
        • Where a managed database can be put
    • Teams
      • Teams
        • Members
          • Who is on it
          • Invite somebody
          • Accept an invitation
          • Change somebody's role
          • Remove somebody
        • Projects
          • The projects a team runs
          • Start one
          • Rename a project, or move its environment
          • Delete a project
          • One project, and what is in it
          • Put a database or store in it
          • What is in a project
          • Take one out
        • The teams this account is on
        • Start one
        • The twelve roles, and what each may do
        • Rename a team
        • Close a team
        • One team
        • Hand the team to somebody else
        • Leave a team
    • Schemas
      • Error
      • ValidationErrors
      • Token
      • PolicyCategory
      • PolicySeverity
      • PolicyAction
      • PolicyTrigger
      • PolicyParam
      • Policy
      • PolicyCatalog
      • PolicyAssignment
      • PolicyOutcome
      • PolicyFiring
      • CredentialTrace
      • Relation
      • Restrictions
      • ChildSummary
      • SignupRequest
      • SigninRequest
      • UpdateMeRequest
      • User
      • Address
      • GeoPoint
      • D1Region
      • Usage
      • UsageReport
      • Resource
      • Database
      • DataStore
      • NewDatabase
      • NewDataStore
      • QueryRequest
      • DatabasePrivilege
      • ApiKey
      • DbUser
      • Access
      • AccessRequest
      • DatabaseObject
      • NewDatabaseObject
      • NewMigration
      • SchemaOperation
      • Migration
      • Operation
      • Session
      • AdminPowers
      • Admin
      • AuditEntry
      • TeamRole
      • Conversation
      • ChatMessage
      • TeamSso
      • Team
      • TeamMember
      • SshKey
      • ConnectionInfo
      • InboxAddress
      • InboxMailbox
      • InboxMessageSummary
      • InboxMessage
      • InboxNote
      • Page
      • Quote
      • Plan
      • ApiError
      • CapabilityRefusal
      • KlockErrorCode
      • PageWindow
      • SessionView
      • KlockStepUpRequest
      • KlockOpenRequest
      • KlockOpenedSession
      • UpdateMeResult
      • CapabilitiesView
      • SessionLimits
      • Device
      • DeviceListed
      • DeviceTeamRef
      • DeviceCommand
      • DeviceAuditLine
      • DeviceActionRequest
      • StaffActionRequest
      • ManagedSession
      • SessionRevoked
      • AccessRule
      • AccessRuleRequest
      • BehaviourProfile
      • BehaviourProfileRequest
      • BehaviourProfileSaved
      • BehaviourFinding
      • BehaviourFindingAck
      • StepUpProof
      • Removed
      • MemberLockdownRequest
      • McpClient
      • McpDelegatedView
      • McpToolCall
      • McpForwardRequest
      • PasswordlessScope
      • RoleScope
      • PasswordlessSession
      • PasswordlessTlsMaterial
      • PasswordlessKerberosMaterial
      • ServiceDeviceKeys
      • ServiceSession
      • DatabaseRole
      • TransferEndpoint
      • TransferJobRequest
      • TransferQuote
      • TransferStrategy
      • TransferJob
      • TransferJobAccess
      • Pool
      • PoolAllowance
      • BillingSubscription
      • Invoice
      • BillingContact
      • PaymentMethod
      • UpcomingCharges
      • TeamBilling
      • TeamKerberosRealm
      • TeamSsoDomain
      • TeamSsoResponse
      • StoreConnection
      • BatchFailure
      • ProxyStatus
  1. dialects

Citus Dialect

Reference for the citus SQL dialect.
Source: citus
Tests: citus

Overview#

Citus is not a separate engine — it is a
PostgreSQL extension (CREATE EXTENSION citus) that turns a group of
PostgreSQL servers into a distributed database. A coordinator holds the
metadata; workers hold the shards. Clients connect to the coordinator with
the ordinary pg driver on the ordinary port and speak ordinary PostgreSQL,
so CitusDialect extends PostgresDialect and inherits everything —
tables, indexes, sequences, triggers, transactions, LISTEN/NOTIFY —
unchanged. What it adds is placement: builders for turning a plain local
table into a distributed or reference table, cluster management, the shard
rebalancer, and columnar storage.
PropertyValue
Dialect namecitus
ExtendsPostgresDialect
Driverpg
Default port5432 (CITUS_DEFAULT_PORT)
Extensioncitus
Cloud SDKnone
Local runtimeself-hosted; no image in this repo
Unlike some dialects in this package, Citus is registered with Prorm's
dialect loader (SqlDialect.Citus in src/dialects/loaders.ts), so it is
constructible through the normal Prorm connection path as well as directly:
import { Prorm } from 'ts-prorm-orm';

Quick start#

Install#

$ npm install ts-prorm-orm pg
$ pnpm add ts-prorm-orm pg
$ yarn add ts-prorm-orm pg
$ bun add ts-prorm-orm pg
pg is the same driver the postgres dialect uses. pg-copy-streams is optional: only the features that need it load it.

Connect#

import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'citus',
  host: 'coordinator.internal',
  database: 'app',
  username: 'postgres',
  password: process.env.DB_PASSWORD,
});
import { Prorm } from 'ts-prorm-orm';

export const db = new Prorm({
  dialect: 'citus',
  url: 'citus://postgres:secret@coordinator.internal:5432/app',
});
A URL is folded into host, port, database, username and password before the dialect is built; any of those passed alongside it wins.

Define a model#

import { DataTypes } from 'ts-prorm-orm';

const User = db.define('User', {
  id: { type: DataTypes.INTEGER(), primaryKey: true, autoIncrement: true },
  email: { type: DataTypes.STRING(255), allowNull: false, unique: true },
  name: { type: DataTypes.STRING(100) },
  meta: { type: DataTypes.JSONB() },
});

await db.sync(); // CREATE TABLE — see Generated SQL below
meta is JSONB, which the containment query below needs.

Query#

import { Op } from 'ts-prorm-orm';

await User.create({ email: 'ada@example.com', name: 'Ada' });

const page = await User.findAll({
  where: { name: { [Op.like]: 'A%' } },
  order: [['id', 'ASC']],
  limit: 20,
  offset: 40,
});

Generated SQL#

Each block is the statement the model call above it hands the dialect's query(), captured with the driver stubbed out. The model layer inlines the values.

Create table#

db.sync() for the model in the Quick start:
CREATE TABLE

Insert, update and delete#

await User.create({ email: 'ada@example.com', name: 'Ada' });
await User.update({ name: 'Grace' }, { where: { email: 'ada@example.com' } });
await User.destroy({ where: { id: 1 } });

Upsert#

await User.upsert({ id: 1, email: 'ada@example.com', name: 'Ada Lovelace' });
upsert() also reads the row by primary key before and after the write, to return the instance.

Pagination#

await User.findAll({
  where: { name: { [Op.like]: 'A%' } },
  order: [['id', 'ASC']],
  limit: 20,
  offset: 40,
});

JSON#

Containment on the meta column:
import { Op } from 'ts-prorm-orm';

await User.findAll({ where: { meta: { [Op.contains]: { plan: 'pro' } } } });

Transaction with a savepoint#

await db.transaction(async (t) => {
  await User.create({ email: 'grace@example.com', name: 'Grace' }, { transaction: t });
  // A nested transaction is a SAVEPOINT; its failure undoes only its own work.
  await db
    .transaction(async (sp) => {
      await User.destroy({ where: { id: 1 }, transaction: sp });
      throw new Error('keep the row');
    }, { transaction: t })
    .catch(() => {});
});

Skip locked rows (SKIP LOCKED)#

A worker that claims rows from a queue table should pass over rows another transaction holds rather than wait for them. lock with skipLocked inside a transaction:
await db.transaction(async (t) => {
  await User.findAll({ where: { name: 'Ada' }, lock: { level: 'UPDATE', skipLocked: true }, transaction: t });
});
Type mapping for the portable descriptors: STRING → VARCHAR(255), auto-increment INTEGER → SERIAL, BOOLEAN → BOOLEAN, DATE → TIMESTAMP, UUID → UUID, JSON → JSON. The type comparison lines the major engines up side by side.

Connection#

CitusDialectOptions is identical to PostgresDialectOptions — Citus reads
no extra connection fields beyond what Postgres already reads, since the
coordinator is a PostgreSQL server.
const dialect = new Prorm({
  dialect: 'citus',
  host: 'coordinator.internal',
  // port defaults to 5432 (CITUS_DEFAULT_PORT); pass port to override
  username: 'postgres',
  password: process.env.PG_PASSWORD,
  database: 'app',
});
await dialect.query(dialect.createExtensionSQL());
// CREATE EXTENSION IF NOT EXISTS "citus"
OptionDefaultNotes
port5432Set in the constructor before being spread with the rest of config, so a caller-supplied port overrides it.
everything else—Inherited unchanged from PostgresDialectOptions (host, username, password, database, ...).

What differs from Postgres#

CitusDialect extends PostgresDialect (postgres) and
overrides 34 of its methods (Object.getOwnPropertyNames(CitusDialect.prototype),
computed by the scratch test); everything else is inherited unchanged.
AreaOverridden
DML buildersformatDefaultValue
DDL and schemaaddIndex, alterDistributedTable, alterTableSetAccessMethod, buildColumnarIndexSql, buildCreateColumnarTableSql, buildPartialIndexSql, createAndDistributeTable, createDistributedFunction, createDistributedTable, createExtensionSQL, createReferenceTable, truncateLocalDataAfterDistributingTable
IntrospectionassertDistributable, getShardIdForDistributionColumn, isolateTenantToNewShard
OthercitusAddNode, citusDrainNode, citusRebalanceStart, citusRebalanceStatus, citusRebalanceStop, citusRebalanceWait, citusRemoveNode, citusSchemaDistribute, citusSchemaUndistribute, citusSetCoordinatorHost, colocateArg, columnarSettings, port, rebalanceTableShards, regclass, setColumnarOptions, transferMode, undistributeTable

Rendering: table names as regclass#

Table names passed to a Citus UDF are regclass arguments, so they are
rendered as a quoted identifier inside a string literal — '"events"', not
"events" — which keeps mixed-case and hostile names exact. Every other
value is escaped with the inherited escape(). Dotted names are
schema-qualified:
dialect.createReferenceTable('app.Countries');
// SELECT create_reference_table('"app"."Countries"')

Distributing tables#

dialect.createDistributedTable('events', 'tenant_id', { colocateWith: 'tenants', shardCount: 64 });
// SELECT create_distributed_table('"events"', 'tenant_id', colocate_with => '"tenants"', shard_count => 64)

dialect.createDistributedTable('e', 'k', { colocateWith: 'none' });
// SELECT create_distributed_table('"e"', 'k', colocate_with => 'none')  -- 'default'/'none' are keywords, not tables

dialect.createDistributedTable('e', 'k', { concurrently: true });
// SELECT create_distributed_table_concurrently('"e"', 'k')  -- Citus 11.1+, cannot run inside a transaction block

dialect.createReferenceTable('countries');
// SELECT create_reference_table('"countries"')

dialect.undistributeTable('e', { cascadeViaForeignKeys: true });
// SELECT undistribute_table('"e"', cascade_via_foreign_keys => true)

dialect.alterDistributedTable('e', { distributionColumn: 'k2', shardCount: 16, colocateWith: 'none', cascadeToColocated: false });
// SELECT alter_distributed_table('"e"', distribution_column => 'k2', shard_count => 16, colocate_with => 'none', cascade_to_colocated => false)

dialect.truncateLocalDataAfterDistributingTable('e');
// SELECT truncate_local_data_after_distributing_table('"e"')

dialect.getShardIdForDistributionColumn('e', 42);
// SELECT get_shard_id_for_distribution_column('"e"', 42)

dialect.isolateTenantToNewShard('e', 135, { cascade: true });
// SELECT isolate_tenant_to_new_shard('"e"', 135, cascade_option => 'CASCADE')

dialect.citusSchemaDistribute('tenant_1');   // SELECT citus_schema_distribute('"tenant_1"')
dialect.citusSchemaUndistribute('tenant_1'); // SELECT citus_schema_undistribute('"tenant_1"')

dialect.createDistributedFunction('app.deliver', ['int', 'character varying(10)', 'text[]'], {
  distributionArgName: '$1',
  colocateWith: 'orders',
});
// SELECT create_distributed_function('"app"."deliver"(int, character varying(10), text[])', distribution_arg_name => '$1', colocate_with => '"orders"')
alterDistributedTable throws (needs at least one of distributionColumn, shardCount or colocateWith) if called with no options.

Checking the distribution key before distributing#

Citus can only enforce PRIMARY KEY / UNIQUE within a shard, so those
constraints must include the distribution column. assertDistributable
checks a table definition against that rule and throws naming the offending
constraint; createAndDistributeTable runs it before issuing any SQL:
await dialect.createAndDistributeTable(
  'events',
  { tenant_id: { type: T('BIGINT'), primaryKey: true }, id: { type: T('BIGINT'), primaryKey: true } },
  'tenant_id',
  { shardCount: 8 },
);
// 1. assertDistributable(...) — throws first if the PK/UNIQUE keys don't include 'tenant_id'
// 2. CREATE TABLE "events" (...)
// 3. SELECT create_distributed_table('"events"', 'tenant_id', shard_count => 8)
assertDistributable also rejects an unknown distribution column and any
UNIQUE column, UNIQUE constraint or unique key that omits it.

Cluster management and rebalancing#

dialect.citusAddNode('worker-1', 5432, { groupId: 3, nodeRole: 'secondary', nodeCluster: 'c1' });
// SELECT citus_add_node('worker-1', 5432, groupid => 3, noderole => 'secondary', nodecluster => 'c1')

dialect.citusRemoveNode('worker-1', 5432);
// SELECT citus_remove_node('worker-1', 5432)

dialect.citusDrainNode('worker-1', 5432, { shardTransferMode: 'block_writes' });
// SELECT citus_drain_node('worker-1', 5432, shard_transfer_mode => 'block_writes'::citus.shard_transfer_mode)

dialect.citusSetCoordinatorHost('coord', 5433);
// SELECT citus_set_coordinator_host('coord', port => 5433)

dialect.rebalanceTableShards({
  table: 'events',
  threshold: 0.1,
  maxShardMoves: 10,
  excludedShardList: [102008, BigInt(102009)],
  shardTransferMode: 'force_logical',
  drainOnly: false,
  rebalanceStrategy: 'by_disk_size',
});
// SELECT rebalance_table_shards(relation => '"events"', threshold => 0.1, max_shard_moves => 10,
//   excluded_shard_list => ARRAY[102008, 102009]::bigint[],
//   shard_transfer_mode => 'force_logical'::citus.shard_transfer_mode, drain_only => false,
//   rebalance_strategy => 'by_disk_size')

dialect.citusRebalanceStart({ drainOnly: true, rebalanceStrategy: 'by_shard_count' });
// SELECT citus_rebalance_start(drain_only => true, rebalance_strategy => 'by_shard_count')  -- background, Citus 11.1+

dialect.citusRebalanceStatus(); // SELECT * FROM citus_rebalance_status()
dialect.citusRebalanceStop();   // SELECT citus_rebalance_stop()
dialect.citusRebalanceWait();   // SELECT citus_rebalance_wait()
shardTransferMode is checked against 'auto' | 'force_logical' | 'block_writes';
threshold must be between 0 and 1; node ports must be an integer 1–65535.

Columnar storage#

Citus columnar is a table access method: append-only storage that compresses
well and scans fast, with no UPDATE/DELETE, no foreign keys, and no
UNLOGGED/TEMPORARY tables.
dialect.buildCreateColumnarTableSql(
  'metrics',
  {
    id: { type: T('BIGINT'), autoIncrement: true, primaryKey: true },
    at: { type: T('DATE'), allowNull: false, defaultValue: 'CURRENT_TIMESTAMP' },
    host: { type: T('STRING', { length: 64 }) },
  },
  { ifNotExists: true, compression: 'zstd', compressionLevel: 3, stripeRowLimit: 150000 },
);
An autoIncrement column is rendered BIGSERIAL only when its underlying
type is BIGINT/BIGSERIAL; every other auto-incrementing type collapses to
plain SERIAL (there is no SMALLSERIAL special-case).
dialect.alterTableSetAccessMethod('events', 'columnar');
// SELECT alter_table_set_access_method('"events"', 'columnar')

dialect.setColumnarOptions('events', { compression: 'lz4', chunkGroupRowLimit: 5000 });
// ALTER TABLE "events" SET (columnar.compression = lz4, columnar.chunk_group_row_limit = 5000)
// (applies only to data written afterwards; existing stripes keep their encoding)

dialect.buildColumnarIndexSql('m', 'm_id', ['id'], { unique: true });
// CREATE UNIQUE INDEX "m_id" ON "m" USING btree ("id")
dialect.buildColumnarIndexSql('m', 'm_h', ['host'], { using: 'hash' });
// CREATE INDEX "m_h" ON "m" USING hash ("host")

Partial indexes#

The inherited Postgres index builder decides partial-index support by
dialect name and would refuse Citus. addIndex is overridden to route a
where predicate through a Citus-local builder instead; everything else
delegates to PostgresDialect:
await dialect.addIndex('t', 'i', ['a'], { unique: true, using: 'btree', where: { b: null } });
// CREATE UNIQUE INDEX "i" ON "t" USING btree ("a") WHERE "b" IS NULL

dialect.buildPartialIndexSql('orders', 'open_orders', ['tenant_id', 'id'], {
  where: { status: 'shipped', total: { [Op.gt]: 0 } },
  include: ['total'],
});
// CREATE INDEX "open_orders" ON "orders" ("tenant_id", "id") INCLUDE ("total")
//   WHERE "status" = 'shipped' AND "total" > 0

Refused, by name#

Citus is PostgreSQL, so there is little to refuse at the dialect level. These
are the rules Citus itself enforces, checked before the statement is sent so
the error names the rule:
MethodRefusesMessage contains
createDistributedTablemissing distribution columnneeds a distribution column
createDistributedTable / alterDistributedTable / rebalanceTableShardsnon-positive-integer shardCount / maxShardMoves / shard idsmust be a positive integer
alterDistributedTablecalled with no optionsneeds at least one of
createDistributedFunctionan argument that isn't a type nameis not a type name
assertDistributable (and createAndDistributeTable)unknown distribution columnno such column
assertDistributable (and createAndDistributeTable)PRIMARY KEY / UNIQUE column, constraint or key that omits the distribution columndoes not include the distribution column
citusAddNodebad groupId, nodeRole not primary/secondary, bad portgroupid must be an integer, noderole must be primary or secondary, port must be an integer
citusDrainNode / rebalanceTableShardsunknown shardTransferModeno shard_transfer_mode
rebalanceTableShards / citusRebalanceStartthreshold outside 0–1between 0 and 1
buildCreateColumnarTableSqlno columns, temporary: true, unlogged: true, a column with referencesno columns, cannot be TEMPORARY, cannot be UNLOGGED, no foreign keys
buildCreateColumnarTableSql / setColumnarOptionsunknown compression, compressionLevel outside 1–19, no options givenno compression, compression_level must be 1–19, at least one option
alterTableSetAccessMethodaccess method other than columnar/heapcolumnar or heap
buildColumnarIndexSqlindex type other than btree/hash, no columnsonly btree and hash, at least one column
buildPartialIndexSqlwhere given as a raw SQL string, or an using value that isn't an access-method-shaped identifierwhere-object, not raw SQL, is not an access method
regclass (internal, used by every UDF builder)empty/non-string table nameCitus needs a table name

Caveats / not-yet-verified#

create_distributed_table_concurrently (concurrently: true) cannot run
inside a transaction block — enforced by Citus itself, not checked here.
Columnar tables lose UPDATE/DELETE, foreign keys, UNLOGGED/TEMPORARY
storage, and index support down to btree/hash only — all Citus
constraints, refused here rather than left to fail server-side.
Auto-incrementing columnar columns only distinguish BIGINT (→
BIGSERIAL) from everything else (→ SERIAL); there is no
SMALLSERIAL case.
The class doc comment states every builder here is "pure and synchronous,"
but createAndDistributeTable and the overridden addIndex are async and
execute query() themselves (create-then-distribute, and partial-index
creation) — most builders are pure SQL-string factories, but not all of
the public surface is.
CitusDialectOptions adds no fields beyond PostgresDialectOptions; there
is currently no dedicated option for worker topology, replication factor,
or citus.shard_count server defaults — those are set via SQL (e.g.
citusAddNode) rather than connection options.

Capabilities#

Computed from the code — capabilitiesOf() (src/transaction-support.ts),
whereSupportOf() (src/query-builders/expression-render.ts),
sqlObjectCapabilitiesOf() (src/sql-objects/capabilities.ts) and the
builders — by the scratch test described in the
capability matrix.
Capabilitycitus
Transactions atomicyes
Savepointsyes
Isolationup to SERIALIZABLE
Transaction modesread-only yes; deferrable yes; constraint deferral yes
RETURNINGRETURNING on INSERT
UpsertINSERT … ON CONFLICT (…) DO UPDATE
JSON columnJSON (JSONB → JSONB)
Vector columnVECTOR(3)
Array columnINTEGER[]
WHERE builder62 operator keys; $and/$or/$not; $exists: yes; $in subquery: yes; expression operands: yes
SQL objectsfamily postgres: triggers yes; procedures yes; functions multiStatement; materialized views native; sequences yes; enums named; RLS policy
StreamingqueryStream() present; LISTEN present; createExtension() present

Related reading#

./postgres.md — the parent dialect; everything not
listed above (tables, indexes, sequences, transactions, LISTEN/NOTIFY)
behaves exactly as documented there.
Citus UDF reference
Citus table management guide
./README.md
Modified at 2026-10-04 00:40:16
Previous
Google BigQuery Dialect
Next
ClickHouse dialect
Built with