From 8fa6019b405f9d39539a77c6f5f11fe640ddf955 Mon Sep 17 00:00:00 2001 From: Fujii Masao <fujii@postgresql.org> Date: Mon, 16 Jan 2017 18:55:34 +0900 Subject: [PATCH] Fix typos in comments. Masahiko Sawada --- src/backend/storage/lmgr/condition_variable.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/storage/lmgr/condition_variable.c b/src/backend/storage/lmgr/condition_variable.c index e2cfc58221c..67fe177a7dd 100644 --- a/src/backend/storage/lmgr/condition_variable.c +++ b/src/backend/storage/lmgr/condition_variable.c @@ -83,7 +83,7 @@ ConditionVariablePrepareToSleep(ConditionVariable *cv) /*-------------------------------------------------------------------------- * Wait for the given condition variable to be signaled. This should be - * called in a predicate loop that tests for a specfic exit condition and + * called in a predicate loop that tests for a specific exit condition and * otherwise sleeps, like so: * * ConditionVariablePrepareToSleep(cv); [optional] @@ -108,7 +108,7 @@ ConditionVariableSleep(ConditionVariable *cv, uint32 wait_event_info) * return can be avoided by calling ConditionVariablePrepareToSleep(cv) * first. Whether it's worth doing that depends on whether you expect the * condition to be met initially, in which case skipping the prepare - * allows you to skip manipulation of the wait list, or not met intiailly, + * allows you to skip manipulation of the wait list, or not met initially, * in which case preparing first allows you to skip a spurious test of the * caller's exit condition. */ -- GitLab