From fe186b4c200b76a5c0f03379fe8645ed1c70a844 Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Mon, 22 Jun 2020 13:40:04 +0900 Subject: [PATCH] Fix inconsistent markups in catalogs.sgml Some fields related to pg_opclass and pg_opfamily were using incorrect markups, listing them as structname instead of structfield. Author: Fabien Coelho Discussion: https://postgr.es/m/alpine.DEB.2.22.394.2006210903560.859381@pseudo --- doc/src/sgml/catalogs.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 700271fd40..5a66115df1 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -897,7 +897,7 @@ An entry's amopmethod must match the - opfmethod of its containing operator family (including + opfmethod of its containing operator family (including amopmethod here is an intentional denormalization of the catalog structure for performance reasons). Also, amoplefttype and amoprighttype must match @@ -5064,10 +5064,10 @@ SCRAM-SHA-256$<iteration count>:&l An operator class's opcmethod must match the - opfmethod of its containing operator family. + opfmethod of its containing operator family. Also, there must be no more than one pg_opclass - row having opcdefault true for any given combination of - opcmethod and opcintype. + row having opcdefault true for any given combination of + opcmethod and opcintype.