From cffc9790588fefdeccc84ace573a5e3ea69565d2 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Thu, 27 May 2021 14:32:04 +0300 Subject: [PATCH] Fix a couple of typos in comments. --- pageserver/src/branches.rs | 2 +- pageserver/src/walredo.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pageserver/src/branches.rs b/pageserver/src/branches.rs index fa4c24dca3..84e737ba6d 100644 --- a/pageserver/src/branches.rs +++ b/pageserver/src/branches.rs @@ -96,7 +96,7 @@ pub fn init_repo(conf: &'static PageServerConf, repo_dir: &Path) -> Result<()> { // and it kept running even after the "zenith init" had exited. In tests, we started the // page server immediately after that, so that initdb was still running in the background, // and we failed to run initdb again in the same directory. This has been solved for the - // rapid init+start case now, but the general race condition remains if you restart the the + // rapid init+start case now, but the general race condition remains if you restart the // server quickly. let repo = crate::repository::rocksdb::RocksRepository::new( conf, diff --git a/pageserver/src/walredo.rs b/pageserver/src/walredo.rs index 4ade6d786e..f1101e1e82 100644 --- a/pageserver/src/walredo.rs +++ b/pageserver/src/walredo.rs @@ -3,7 +3,7 @@ //! //! We rely on Postgres to perform WAL redo for us. We launch a //! postgres process in special "wal redo" mode that's similar to -//! single-user mode. We then pass the the previous page image, if any, +//! single-user mode. We then pass the previous page image, if any, //! and all the WAL records we want to apply, to the postgres //! process. Then we get the page image back. Communication with the //! postgres process happens via stdin/stdout