database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-12-19 17:02:53 +03:00
Code Activity

Remove option to change parser of an existing text search configuration.

Browse Source 
This prevents needing to do complex and poorly-defined updates of the
mapping table if the new parser has different token types than the old.
Per discussion.
This commit is contained in:
Tom Lane
2007-08-22 05:13:50 +00:00
parent 40c1d7c10e
commit 8a5592daf1
5 changed files with 33 additions and 139 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/ref/create_tsconfig.sgml
View File

@@ -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>