summaryrefslogtreecommitdiff
path: root/src/backend/utils/cache
diff options
context:
space:
mode:
authorBruce Momjian2018-03-29 19:18:53 +0000
committerBruce Momjian2018-03-29 19:18:53 +0000
commit20b4323bd107920a3c3e60452442e8e2cee302d2 (patch)
treef1536ef784d5432263fb8b537ada80c35c408318 /src/backend/utils/cache
parent3282c4c136e4e5ad22d57dbe7a98fbac2962500a (diff)
C comments: "a" <--> "an" corrections
Reported-by: Michael Paquier, Abhijit Menon-Sen Discussion: https://postgr.es/m/[email protected] Author: Michael Paquier, Abhijit Menon-Sen, me
Diffstat (limited to 'src/backend/utils/cache')
-rw-r--r--src/backend/utils/cache/relcache.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/utils/cache/relcache.c b/src/backend/utils/cache/relcache.c
index 48f92dc430d..69a2114a104 100644
--- a/src/backend/utils/cache/relcache.c
+++ b/src/backend/utils/cache/relcache.c
@@ -2420,7 +2420,7 @@ RelationDestroyRelation(Relation relation, bool remember_tupdesc)
* NB: when rebuilding, we'd better hold some lock on the relation,
* else the catalog data we need to read could be changing under us.
* Also, a rel to be rebuilt had better have refcnt > 0. This is because
- * an sinval reset could happen while we're accessing the catalogs, and
+ * a sinval reset could happen while we're accessing the catalogs, and
* the rel would get blown away underneath us by RelationCacheInvalidate
* if it has zero refcnt.
*