Doc fix: Interfacing Extensions to Indexes

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>

diff --git a/doc/src/sgml/xindex.sgml b/doc/src/sgml/xindex.sgml
index c753d8005acd49e0f07fd3cb0f5b984338646e3b..22d8ad1aac43b38a119780da45de0159af6c6062 100644 (file)
--- a/doc/src/sgml/xindex.sgml
+++ b/doc/src/sgml/xindex.sgml
@@ -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>