diff options
author | Peter Eisentraut <peter_e@gmx.net> | 2011-06-29 09:26:14 +0300 |
---|---|---|
committer | Peter Eisentraut <peter_e@gmx.net> | 2011-07-02 23:30:01 +0300 |
commit | 6b23ba1093d298a41463a24f091c6f86be406449 (patch) | |
tree | 70329bb4476d1226cea9547b23a18535d1785c32 /src/backend/utils/cache/relcache.c | |
parent | 678a6d03441fc5acb18fdd43afdd2dd4145c0593 (diff) |
Unify spelling of "canceled", "canceling", "cancellation"
We had previously (af26857a2775e7ceb0916155e931008c2116632f)
established the U.S. spellings as standard.
Diffstat (limited to 'src/backend/utils/cache/relcache.c')
-rw-r--r-- | src/backend/utils/cache/relcache.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/utils/cache/relcache.c b/src/backend/utils/cache/relcache.c index d7e94ffc125..1a400a0a576 100644 --- a/src/backend/utils/cache/relcache.c +++ b/src/backend/utils/cache/relcache.c @@ -1897,7 +1897,7 @@ RelationClearRelation(Relation relation, bool rebuild) * on next access. Meanwhile it's not any less valid than it was * before, so any code that might expect to continue accessing it * isn't hurt by the rebuild failure. (Consider for example a - * subtransaction that ALTERs a table and then gets cancelled partway + * subtransaction that ALTERs a table and then gets canceled partway * through the cache entry rebuild. The outer transaction should * still see the not-modified cache entry as valid.) The worst * consequence of an error is leaking the necessarily-unreferenced new |