Re: EXCLUDE COLLATE in CREATE/ALTER TABLE document

Поиск
Список
Период
Сортировка
От Daniel Verite
Тема Re: EXCLUDE COLLATE in CREATE/ALTER TABLE document
Дата
Msg-id ef8b3cbb-724c-41b7-9d00-87fe01c8effc@manitou-mail.org
обсуждение исходный текст
Ответ на Re: EXCLUDE COLLATE in CREATE/ALTER TABLE document  (shihao zhong <zhong950419@gmail.com>)
Ответы Re: EXCLUDE COLLATE in CREATE/ALTER TABLE document  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
    shihao zhong wrote:

> Thanks for your comments, a new version is attached.

In this hunk:

@@ -1097,8 +1097,8 @@ WITH ( MODULUS <replaceable
class="parameter">numeric_literal</replaceable>, REM
       method <replaceable>index_method</replaceable>.
       The operators are required to be commutative.
       Each <replaceable class="parameter">exclude_element</replaceable>
-      can optionally specify an operator class and/or ordering options;
-      these are described fully under
+      can optionally specify any of the following: a collation, a
+      operator class, or ordering options; these are described fully under
       <xref linkend="sql-createindex"/>.
      </para>

"a" should be "an" as it's followed by "operator class".

Also the use of "and/or" in the previous version conveys the fact
that operator class and ordering options are not mutually
exclusive. But when using "any of the following" in the new text,
doesn't it loose that meaning?

In case it does, I would suggest the attached diff.

Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Karl O. Pinc"
Дата:
Сообщение: Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector
Следующее
От: Nurul Karim Rafi
Дата:
Сообщение: Re: Materialized view in Postgres from the variables rather than SQL query results