vendor-documentation · locator & rights
Data types; transactions; recovery; security
Link and original paraphrase only; upstream rights retained.
Operations / FEATURE
Point-in-time recovery
Restore an earlier database state; setup and retention depend on the target.
4connected products
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.
4 products have Yes or Partial documentation. Review freshness and attestation counts describe the dossier, not runtime quality. Gaps below are product-wide, not necessarily specific to this feature.
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.
2 open gaps · applicability & verification plan
What we do not know yet about PostgreSQL
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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
Sources · 1
Unknown — no evidence recorded
2 open gaps · applicability & verification plan
What we do not know yet about SQLite
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
Application owns the database file, lifecycle and backup procedure; no separate database server.
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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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
Unknown — no evidence recorded
2 open gaps · applicability & verification plan
What we do not know yet about MongoDB Community
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
Operator manages the deployment. This target does not include an Atlas service or configured vector-search component.
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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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
Unknown — no evidence recorded
2 open gaps · applicability & verification plan
What we do not know yet about PostgreSQL + pgvector
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
PostgreSQL plus an installed and enabled pgvector extension; operator manages both.
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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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
Unknown — no evidence recorded
2 open gaps · applicability & verification plan
What we do not know yet about Qdrant
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
Self-managed server deployment; Qdrant Cloud and Edge are outside this target.
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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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
Point-in-time recoveryYes
Explore Point-in-time recovery →
Time Travel restores earlier database state.
Scope: Available retention depends on the current service plan.
2 open gaps · applicability & verification plan
What we do not know yet about Cloudflare D1
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
Database is a managed service separate from Worker application compute; do not assume arbitrary SQLite 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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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
Sources · 1
vendor-documentation · locator & rights
SQL; Time Travel; read replication
Link and original paraphrase only; upstream rights retained.
Point-in-time recoveryYes
Explore Point-in-time recovery →
Provides point-in-time recovery for SQLite-backed object storage.
2 open gaps · applicability & verification plan
What we do not know yet about Durable Objects + SQLite
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
Each object owns private storage. Application implements Worker routing and cross-object coordination.
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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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
Sources · 1
vendor-documentation · locator & rights
Access storage; SQL in Durable Objects vs D1
Link and original paraphrase only; upstream rights retained.
Point-in-time recoveryYes
Explore Point-in-time recovery →
Documents instant restore.
Scope: Restore window and availability depend on configuration and plan.
2 open gaps · applicability & verification plan
What we do not know yet about Neon Postgres
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
Neon hosted Postgres; vector claims require enabling pgvector per database. Other backend services are excluded.
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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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
Sources · 1
vendor-documentation · locator & rights
Products: Lakebase Postgres
Link and original paraphrase only; upstream rights retained.
Unknown — no evidence recorded
2 open gaps · applicability & verification plan
What we do not know yet about MongoDB Atlas
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
Atlas cluster plus configured search indexes; region, cluster type and search resources must be specified.
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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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
Unknown — no evidence recorded
2 open gaps · applicability & verification plan
What we do not know yet about Pinecone
- Which pinned versions, topology and service tier fit the intended workload?
- What are measured correctness, latency, recovery and total operating cost under that workload?
Applicability
Unpinned upstream documentation accessed 2026-09-14; pin engine, extension and service versions before use.
Hosted index and namespace configuration; attached metadata is not classified as a general document database.
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
- Pin the target configuration and define workload fixtures, access and budget.
- With authorization, test concurrent writes and recovery against explicit correctness expectations.
- 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