From c71faae2c61b1c2578f33afcbe877b206e4867c9 Mon Sep 17 00:00:00 2001 From: Ryan Russell Date: Wed, 1 Jun 2022 14:59:16 -0500 Subject: [PATCH] Docs readability cont Signed-off-by: Ryan Russell --- docs/core_changes.md | 2 +- docs/rfcs/002-storage.md | 2 +- pageserver/src/layered_repository/README.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/core_changes.md b/docs/core_changes.md index db311e3667..82c5addd16 100644 --- a/docs/core_changes.md +++ b/docs/core_changes.md @@ -188,7 +188,7 @@ Not currently committed but proposed: 3. Prefetching - Why? As far as pages in Zenith are loaded on demand, to reduce node startup time - and also sppedup some massive queries we need some mechanism for bulk loading to + and also speedup some massive queries we need some mechanism for bulk loading to reduce page request round-trip overhead. Currently Postgres is supporting prefetching only for bitmap scan. diff --git a/docs/rfcs/002-storage.md b/docs/rfcs/002-storage.md index 6e756df4bf..f99683cf09 100644 --- a/docs/rfcs/002-storage.md +++ b/docs/rfcs/002-storage.md @@ -77,7 +77,7 @@ Upon storage node restart recent WAL files are applied to appropriate pages and ### **Checkpointing** -No such mechanism is needed. Or we may look at the storage node as at kind of continuous chekpointer. +No such mechanism is needed. Or we may look at the storage node as at kind of continuous checkpointer. ### **Full page writes (torn page protection)** diff --git a/pageserver/src/layered_repository/README.md b/pageserver/src/layered_repository/README.md index 81f585d2e2..15040d21b2 100644 --- a/pageserver/src/layered_repository/README.md +++ b/pageserver/src/layered_repository/README.md @@ -409,7 +409,7 @@ removed because there is no newer layer file for the table. Things get slightly more complicated with multiple branches. All of the above still holds, but in addition to recent files we must also -retain older shapshot files that are still needed by child branches. +retain older snapshot files that are still needed by child branches. For example, if child branch is created at LSN 150, and the 'customers' table is updated on the branch, you would have these files: