PostgreSQL Adapter

The PostgreSQL adapter is experimental, shadow-only code for tests and migration rehearsal. It is not active production storage, it does not replace JSON, and production writes remain blocked.

Feature Flags

• VORLIQ_STORAGE_BACKEND=json is the default and production setting.
• VORLIQ_STORAGE_BACKEND=postgres is refused in production.
• Non-production adapter tests require VORLIQ_ALLOW_EXPERIMENTAL_POSTGRES=true.
• Shadow/test runtime selection also requires VORLIQ_POSTGRES_SHADOW_ONLY=true.
• PostgreSQL writes are disabled unless VORLIQ_POSTGRES_WRITE_MODE=shadow_test is explicitly set, and current imports still use the guarded shadow migration tool.

What It Can Read

When pointed at a shadow database, the adapter can read chain blocks, confirmed transactions, pending transactions, profiles, forum posts, governance proposals, exchange offers, lending loans, treasury proposals, registry nodes, faucet claims, price signals, achievements, table counts, and latest block metadata from the preparation schema.

What It Cannot Do

It must not connect production runtime to a production database, mutate production JSON, rewrite historical blocks, change block hashes, expose database credentials, or become active storage without a future approved cutover. Write methods are blocked by default.

Parity

The shadow rehearsal supports --check-adapter, which loads the PostgreSQL adapter after verification and compares adapter-read counts with the verification report. This is additional evidence only; it is not a migration.

Related

• Storage adapter interface
• PostgreSQL readiness
• Database migration plan
• Database rollback plan