← System overview

STORAGE / PROFESSIONAL

PostgreSQL

Use PostgreSQL as a managed storage backend through RightMV's modular boundary.

01 / DESIGN

How PostgreSQL stores data.

The PostgreSQL provider maps accounts, files and item bytes into database tables accessed through JDBC. A bounded connection pool serves concurrent work, while record-lock ownership and heartbeat timestamps are stored in the database.

AVAILABILITYProfessional storage option.
  1. 01BASIC file operation
  2. 02JDBC storage adapter
  3. 03Connection pool
  4. 04PostgreSQL tables
  5. 05Database durability

02 / TRADE-OFFS

Choose the engine for the workload.

Storage engines balance memory, I/O, recovery, concurrency and operational complexity. These profiles show where each engine fits.

STRENGTHS

  • Uses established database operations and tooling
  • Centralised backups, monitoring and access control
  • Strong concurrent access model
  • Suitable for estates already standardised on PostgreSQL

WEAKNESSES

  • Requires a separately operated database service
  • Network and SQL overhead affect small item operations
  • Pool sizing must match server capacity
  • Schema and database upgrades need operational coordination

03 / ABILITIES

What it provides.

The PostgreSQL backend connects RightMV runtime services to a widely operated database platform, with operational guidance and supported deployment patterns in Professional Edition.

01

Binary-safe item storage

02

Pooled JDBC connections

03

Database-backed record locks with stale-lock recovery

04

Account and file metadata tables

BEST FIT

  • Managed database operations
  • Existing PostgreSQL estates
  • Professional deployments

CORE CAPABILITIES

  • PostgreSQL-backed persistence
  • ExecutionContext integration
  • Centralised database operations
  • Professional support path

CONFIGURATION

  • MVDB_PG_URL
  • MVDB_PG_DB
  • MVDB_PG_USER
  • MVDB_PG_PASSWORD
  • MVDB_PG_CONNECTION_POOL_SIZE
  • MVDB_PG_ITEM_CACHE_SIZE
  • MVDB_PG_RECORD_LOCK_TTL_MS