From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | splarv(at)ya(dot)ru |
Subject: | ^@ operator vs start_with function |
Date: | 2023-10-31 12:41:13 |
Message-ID: | 169875607385.1769272.18010444720249291234@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/functions-string.html
Description:
https://www.postgresql.org/docs/16/functions-string.html
Said
text ^@ text → boolean
Returns true if the first string starts with the second string (equivalent
to the starts_with() function).
'alphabet' ^@ 'alph' → t
This is not true equivalent, because ^@ can be accelerated by special
SP-GiST index
https://www.postgresql.org/docs/14/spgist-builtin-opclasses.html
while function starts_with() perhaps no.
Thus need to mention in the description of ^@ it can be accelerated by the
special index with link to it. And in the description on start_with() need
to mention that alternative ^@ is better, because it can be accelerated by
index, while the function is not.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-10-31 13:10:56 | Re: The documentation for storage type 'plain' actually allows single byte header |
Previous Message | Daniel Westermann (DWE) | 2023-10-30 13:30:12 | Re: Missing word? https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-ARCHIVING-WAL |