rust/neon
1
0
Fork 0
mirror of https://github.com/neondatabase/neon.git synced 2025-12-22 21:59:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix a couple of typos in comments.

Browse Source
This commit is contained in:
Heikki Linnakangas
2021-05-27 14:32:04 +03:00
parent 1af6607fc3
commit cffc979058
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
pageserver/src/branches.rs
View File

@@ -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 // 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, // 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 // 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. // server quickly.
let repo = crate::repository::rocksdb::RocksRepository::new( let repo = crate::repository::rocksdb::RocksRepository::new(
conf, conf,

2
pageserver/src/walredo.rs
View File

@@ -3,7 +3,7 @@
//! //!
//! We rely on Postgres to perform WAL redo for us. We launch a //! We rely on Postgres to perform WAL redo for us. We launch a
//! postgres process in special "wal redo" mode that's similar to //! 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 //! and all the WAL records we want to apply, to the postgres
//! process. Then we get the page image back. Communication with the //! process. Then we get the page image back. Communication with the
//! postgres process happens via stdin/stdout //! postgres process happens via stdin/stdout