From d87ab88686fb60ad5a34373de05bb20e632cf003 Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Fri, 12 Apr 2019 12:56:38 +0900 Subject: [PATCH] Fix typos in reloptions.c Author: Kirk Jamison Discussion: https://postgr.es/m/D09B13F772D2274BB348A310EE3027C6493463@g01jpexmbkw24 --- src/backend/access/common/reloptions.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/access/common/reloptions.c b/src/backend/access/common/reloptions.c index da66faf687..cfbabb5265 100644 --- a/src/backend/access/common/reloptions.c +++ b/src/backend/access/common/reloptions.c @@ -77,7 +77,7 @@ * n_distinct options can be set at ShareUpdateExclusiveLock because they * are only used during ANALYZE, which uses a ShareUpdateExclusiveLock, * so the ANALYZE will not be affected by in-flight changes. Changing those - * values has no affect until the next ANALYZE, so no need for stronger lock. + * values has no effect until the next ANALYZE, so no need for stronger lock. * * Planner-related parameters can be set with ShareUpdateExclusiveLock because * they only affect planning and not the correctness of the execution. Plans @@ -93,7 +93,7 @@ * vacuum_truncate can be set at ShareUpdateExclusiveLock because it * is only used during VACUUM, which uses a ShareUpdateExclusiveLock, * so the VACUUM will not be affected by in-flight changes. Changing its - * value has no affect until the next VACUUM, so no need for stronger lock. + * value has no effect until the next VACUUM, so no need for stronger lock. */ static relopt_bool boolRelOpts[] =