Commite9d12a5

committed

Doc fix: Interfacing Extensions to Indexes

Refer to CREATE ACCESS METHOD rather than suggesting direct changes topg_am. Also corrects index-specific language that predated tableaccess methods.Discussion:https://postgr.es/m/20231025172551.685b7799455f9a6addcf5afa@sraoss.co.jpReported-by: Yugo NAGATA <nagata@sraoss.co.jp>

1 parent9ba9c70 commite9d12a5Copy full SHA for e9d12a5

File tree

-8

lines changed

-8

lines changed

Lines changed: 5 additions & 8 deletions

Original file line number	Diff line number	Diff line change
`@@ -29,14 +29,11 @@`
`29`	`29`	`<title>Index Methods and Operator Classes</title>`
`30`	`30`
`31`	`31`	`<para>`
`32`		`- The <classname>pg_am</classname> table contains one row for every`
`33`		`- index method (internally known as access method). Support for`
`34`		`- regular access to tables is built into`
`35`		`- <productname>PostgreSQL</productname>, but all index methods are`
`36`		`- described in <classname>pg_am</classname>. It is possible to add a`
`37`		`- new index access method by writing the necessary code and`
`38`		`- then creating an entry in <classname>pg_am</classname> — but that is`
`39`		`- beyond the scope of this chapter (see <xref linkend="indexam"/>).`
	`32`	`+ Operator classes are associated with an index access method, such`
	`33`	`+ as <link linkend="btree">B-Tree</link>`
	`34`	`+ or <link linkend="gin">GIN</link>. Custom index access method may be`
	`35`	`+ defined with <xref linkend="sql-create-access-method"/>. See`
	`36`	`+ <xref linkend="indexam"/> for details.`
`40`	`37`	`</para>`
`41`	`38`
`42`	`39`	`<para>`

Comments

(0)