aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/cache
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-05-14 10:54:47 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2017-05-14 10:55:01 -0400
commitf04c9a61468904b6815b2bc73a48878817766e0e (patch)
treeb8eb1b9a131023b1ab0f7e151e036988d02eb8a3 /src/backend/utils/cache
parent12ad38b3b4b5004001a525e0a0eda2ec45329e8e (diff)
downloadpostgresql-f04c9a61468904b6815b2bc73a48878817766e0e.tar.gz
postgresql-f04c9a61468904b6815b2bc73a48878817766e0e.zip
Standardize terminology for pg_statistic_ext entries.
Consistently refer to such an entry as a "statistics object", not just "statistics" or "extended statistics". Previously we had a mismash of terms, accompanied by utter confusion as to whether the term was singular or plural. That's not only grating (at least to the ear of a native English speaker) but could be outright misleading, eg in error messages that seemed to be referring to multiple objects where only one could be meant. This commit fixes the code and a lot of comments (though I may have missed a few). I also renamed two new SQL functions, pg_get_statisticsextdef -> pg_get_statisticsobjdef pg_statistic_ext_is_visible -> pg_statistics_obj_is_visible to conform better with this terminology. I have not touched the SGML docs other than fixing those function names; the docs certainly need work but it seems like a separable task. Discussion: https://postgr.es/m/22676.1494557205@sss.pgh.pa.us
Diffstat (limited to 'src/backend/utils/cache')
-rw-r--r--src/backend/utils/cache/relcache.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/utils/cache/relcache.c b/src/backend/utils/cache/relcache.c
index c3721d9e431..0cd6289f916 100644
--- a/src/backend/utils/cache/relcache.c
+++ b/src/backend/utils/cache/relcache.c
@@ -4462,7 +4462,7 @@ RelationGetIndexList(Relation relation)
/*
* RelationGetStatExtList
- * get a list of OIDs of extended statistics on this relation
+ * get a list of OIDs of statistics objects on this relation
*
* The statistics list is created only if someone requests it, in a way
* similar to RelationGetIndexList(). We scan pg_statistic_ext to find
@@ -4470,7 +4470,7 @@ RelationGetIndexList(Relation relation)
* won't have to compute it again. Note that shared cache inval of a
* relcache entry will delete the old list and set rd_statvalid to 0,
* so that we must recompute the statistics list on next request. This
- * handles creation or deletion of a statistic.
+ * handles creation or deletion of a statistics object.
*
* The returned list is guaranteed to be sorted in order by OID, although
* this is not currently needed.