|
77 | 77 | * n_distinct options can be set at ShareUpdateExclusiveLock because they |
78 | 78 | * are only used during ANALYZE, which uses a ShareUpdateExclusiveLock, |
79 | 79 | * so the ANALYZE will not be affected by in-flight changes. Changing those |
80 | | - * values has noaffect until the next ANALYZE, so no need for stronger lock. |
| 80 | + * values has noeffect until the next ANALYZE, so no need for stronger lock. |
81 | 81 | * |
82 | 82 | * Planner-related parameters can be set with ShareUpdateExclusiveLock because |
83 | 83 | * they only affect planning and not the correctness of the execution. Plans |
|
93 | 93 | * vacuum_truncate can be set at ShareUpdateExclusiveLock because it |
94 | 94 | * is only used during VACUUM, which uses a ShareUpdateExclusiveLock, |
95 | 95 | * so the VACUUM will not be affected by in-flight changes. Changing its |
96 | | - * value has noaffect until the next VACUUM, so no need for stronger lock. |
| 96 | + * value has noeffect until the next VACUUM, so no need for stronger lock. |
97 | 97 | */ |
98 | 98 |
|
99 | 99 | staticrelopt_boolboolRelOpts[]= |
|