mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Doc fix: Interfacing Extensions to Indexes

Browse Source 
Refer to CREATE ACCESS METHOD rather than suggesting direct changes to
pg_am. Also corrects index-specific language that predated table
access methods.

Discussion: https://postgr.es/m/20231025172551.685b7799455f9a6addcf5afa@sraoss.co.jp
Reported-by: Yugo NAGATA <nagata@sraoss.co.jp>
This commit is contained in:
Jeff Davis 2023-10-25 13:20:15 -07:00
parent 9ba9c7074f
commit e9d12a5e22
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/src/sgml/xindex.sgml
View File

@ -29,14 +29,11 @@
<title>Index Methods and Operator Classes</title>
<para>
The <classname>pg_am</classname> table contains one row for every
index method (internally known as access method). Support for
regular access to tables is built into
<productname>PostgreSQL</productname>, but all index methods are
described in <classname>pg_am</classname>. It is possible to add a
new index access method by writing the necessary code and
then creating an entry in <classname>pg_am</classname> &mdash; but that is
beyond the scope of this chapter (see <xref linkend="indexam"/>).
Operator classes are associated with an index access method, such
as <link linkend="btree">B-Tree</link>
or <link linkend="gin">GIN</link>. Custom index access method may be
defined with <xref linkend="sql-create-access-method"/>. See
<xref linkend="indexam"/> for details.
</para>
<para>