mirror of
https://github.com/postgres/postgres.git
synced 2025-06-13 07:41:39 +03:00
Spell checking and markup refinement
This commit is contained in:
@ -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];
|
||||
|
@ -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;
|
||||
|
@ -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.
|
||||
*/
|
||||
|
Reference in New Issue
Block a user