Engine / PRODUCT DOSSIER

PostgreSQL

Relational SQL engine with JSON types and extensibility.

Self-managed · Open source · PostgreSQL LicenseRevision 2026-09-14.1 · unreviewedNeeds recheck · recheck 2026-10-140 attestations · checked 2026-09-14

What we do not know yet · 2 open gaps

  • Which pinned versions, topology and service tier fit the intended workload?
  • What are measured correctness, latency, recovery and total operating cost under that workload?

Applies to: Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use. · Operator manages deployment, backups and upgrades. This target excludes extensions.

Applicability, 1 recheck triggers & verification plan

Applicability

Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.

Operator manages deployment, backups and upgrades. This target excludes extensions.

Excludes: Runtime verification; Workload benchmarks and cost comparisons; Unlisted extensions, service tiers and deployment configurations

Recheck when

  • Upstream version, license, API, service plan or storage topology changes.

Needs recheck · due

Verification plan

  1. Pin the target configuration and define workload fixtures, access and budget.
  2. With authorization, test concurrent writes and recovery against explicit correctness expectations.
  3. For vector workloads, measure filtered recall against an exact-search baseline and record index settings.

Provenance & review

Testedknowhow database research

Commissioned by a Nimbalyst maintainer. Documentation synthesis; no independent review or product execution.

Revision 2026-09-14.1 · unreviewed · checked

0 attestations · Content: Unlicensed prototype; redistribution decision pending

← Databases & storage

Relational · Engine

Operator manages deployment, backups and upgrades. This target excludes extensions.

Target sources: PostgreSQL overview ↗ PostgreSQL license ↗

Capability claims · 5 / 17 sourced

Standing condition: these are documentation claims at the source capture date, with outcome “claimed”; no runtime execution is recorded. Dossier applicability and limitations apply throughout. Expand a row for its statement, specific scope and contradictions. Numbered citations resolve to the source locator and capture date below. Missing evidence means Unknown, not No. Sources are unpinned unless marked “Pinned”; this marks source stability, not stronger support or runtime verification. Reuse counts refer to claims in the full dossier; repeated citations do not represent independent sources.

Yes Documented within scope Partial Limited form of the feature No Explicit evidence of absence Unknown No evidence recorded. These are support assessments, not quality scores or runtime verification.

Data model

SQL queriesYes
Explore SQL queries →

Queries relational tables using SQL.

JSON valuesYes
Explore JSON values →

Supports JSON and JSONB values.

Consistency

Multi-record transactionsYes
Explore Multi-record transactions →

Supports transactions and isolation levels including Serializable.

Operations

ReplicationYes
Explore Replication →

Supports synchronous, asynchronous and logical replication.

Point-in-time recoveryYes
Explore Point-in-time recovery →

Supports WAL-based point-in-time recovery.

Scope: Operator must configure recovery and retain the required WAL and backups.

Unknown · 12 capabilities without evidence

Interface images & local attachments

Sources · 2

[1]PostgreSQL overview ↗5 / 5 claims
vendor-documentation · locator & rights

Data types; transactions; recovery; security

Link and original paraphrase only; upstream rights retained.

[2]PostgreSQL license ↗0 / 5 claims
vendor-documentation · locator & rights

PostgreSQL License

Link and original paraphrase only; upstream rights retained.