From e9d12a5e22e02bace45dc2ba0e0dcca5b5d4fc52 Mon Sep 17 00:00:00 2001 From: Jeff Davis Date: Wed, 25 Oct 2023 13:20:15 -0700 Subject: [PATCH] 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 --- doc/src/sgml/xindex.sgml | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/xindex.sgml b/doc/src/sgml/xindex.sgml index c753d8005a..22d8ad1aac 100644 --- a/doc/src/sgml/xindex.sgml +++ b/doc/src/sgml/xindex.sgml @@ -29,14 +29,11 @@ Index Methods and Operator Classes - The pg_am table contains one row for every - index method (internally known as access method). Support for - regular access to tables is built into - PostgreSQL, but all index methods are - described in pg_am. It is possible to add a - new index access method by writing the necessary code and - then creating an entry in pg_am — but that is - beyond the scope of this chapter (see ). + Operator classes are associated with an index access method, such + as B-Tree + or GIN. Custom index access method may be + defined with . See + for details.