diff options
Diffstat (limited to 'src/backend/access/gist')
| -rw-r--r-- | src/backend/access/gist/gist.c | 4 | ||||
| -rw-r--r-- | src/backend/access/gist/gistget.c | 2 | ||||
| -rw-r--r-- | src/backend/access/gist/gistxlog.c | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/src/backend/access/gist/gist.c b/src/backend/access/gist/gist.c index 4881a7dd48b..0e779e09d71 100644 --- a/src/backend/access/gist/gist.c +++ b/src/backend/access/gist/gist.c @@ -227,7 +227,7 @@ gistbuildempty(PG_FUNCTION_ARGS) { ereport(ERROR, (errcode(ERRCODE_FEATURE_NOT_SUPPORTED), - errmsg("unlogged GIST indexes are not supported"))); + errmsg("unlogged GiST indexes are not supported"))); PG_RETURN_VOID(); } @@ -1405,7 +1405,7 @@ initGISTstate(GISTSTATE *giststate, Relation index) * functions don't care about collation, so we just do it * unconditionally. (We could alternatively call get_typcollation, * but that seems like expensive overkill --- there aren't going to be - * any cases where a GIST storage type has a nondefault collation.) + * any cases where a GiST storage type has a nondefault collation.) */ if (OidIsValid(index->rd_indcollation[i])) giststate->supportCollation[i] = index->rd_indcollation[i]; diff --git a/src/backend/access/gist/gistget.c b/src/backend/access/gist/gistget.c index 4eb31318ffd..1aba6868447 100644 --- a/src/backend/access/gist/gistget.c +++ b/src/backend/access/gist/gistget.c @@ -71,7 +71,7 @@ gistindex_keytest(IndexScanDesc scan, int i; if (GistPageIsLeaf(page)) /* shouldn't happen */ - elog(ERROR, "invalid GIST tuple found on leaf page"); + elog(ERROR, "invalid GiST tuple found on leaf page"); for (i = 0; i < scan->numberOfOrderBys; i++) so->distances[i] = -get_float8_infinity(); return true; diff --git a/src/backend/access/gist/gistxlog.c b/src/backend/access/gist/gistxlog.c index 51354c1c185..02c4ec3a6f5 100644 --- a/src/backend/access/gist/gistxlog.c +++ b/src/backend/access/gist/gistxlog.c @@ -306,7 +306,7 @@ gist_redo(XLogRecPtr lsn, XLogRecord *record) MemoryContext oldCxt; /* - * GIST indexes do not require any conflict processing. NB: If we ever + * GiST indexes do not require any conflict processing. NB: If we ever * implement a similar optimization we have in b-tree, and remove killed * tuples outside VACUUM, we'll need to handle that here. */ |