PostgreSQL Documentation¶
PostgreSQL Global Development Group. PostgreSQL Documentation: Routine Vacuuming and Replication Progress Tracking.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Database Vacuum or Compaction
- It is a first-class, automated feature of production engines precisely because the accumulation it fights is unavoidable under versioned concurrency.
This sourcePostgreSQL documents autovacuum as a default-enabled automation facility and explains that MVCC necessarily retains obsolete row versions until VACUUM reclaims their space.
- It is a first-class, automated feature of production engines precisely because the accumulation it fights is unavoidable under versioned concurrency.
- Synchronization Origin Token
- Provenance draws the line where it actually belongs: at who caused this.
This sourcePostgreSQL replication origins attach changes to their remote provenance so replication behavior can distinguish who caused a row and prevent loops.
- Provenance draws the line where it actually belongs: at who caused this.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:597ec3c61f93 · see in the full table