aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/create_tsconfig.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/sgml/ref/create_tsconfig.sgml')
-rw-r--r--doc/src/sgml/ref/create_tsconfig.sgml9
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/src/sgml/ref/create_tsconfig.sgml b/doc/src/sgml/ref/create_tsconfig.sgml
index 49be9411d56..048cb63ce9a 100644
--- a/doc/src/sgml/ref/create_tsconfig.sgml
+++ b/doc/src/sgml/ref/create_tsconfig.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_tsconfig.sgml,v 1.1 2007/08/21 21:08:47 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_tsconfig.sgml,v 1.2 2007/08/22 05:13:50 tgl Exp $
PostgreSQL documentation
-->
@@ -98,10 +98,9 @@ CREATE TEXT SEARCH CONFIGURATION <replaceable class="parameter">name</replaceabl
<title>Notes</title>
<para>
- It is allowed to specify both <literal>PARSER</> and <literal>COPY</>,
- resulting in the specified parser being used with whatever mappings
- are in the source configuration. This is generally inadvisable,
- unless you know that both parsers involved use the same token type set.
+ The <literal>PARSER</> and <literal>COPY</> options are mutually
+ exclusive, because when an existing configuration is copied, its
+ parser selection is copied too.
</para>
</refsect1>