Bruce,

in
http://www.postgresql.org/docs/8.3/s...ARCH-THESAURUS
I think
ALTER TEXT SEARCH CONFIGURATION russian
ADD MAPPING FOR asciiword, asciihword, hword_asciipart WITH thesaurus_simple;

should be
ALTER TEXT SEARCH CONFIGURATION russian
ALTER MAPPING FOR asciiword, asciihword, hword_asciipart WITH thesaurus_simple;

since configuration russian already exists.


Regards,
Oleg
__________________________________________________ ___________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Oleg Bartunov <oleg@sai.msu.su> writes:
> in
> http://www.postgresql.org/docs/8.3/s...ARCH-THESAURUS
> I think
> ALTER TEXT SEARCH CONFIGURATION russian
> ADD MAPPING FOR asciiword, asciihword, hword_asciipart WITH thesaurus_simple;
> should be
> ALTER TEXT SEARCH CONFIGURATION russian
> ALTER MAPPING FOR asciiword, asciihword, hword_asciipart WITH thesaurus_simple;
> since configuration russian already exists.

Done. I notice that if you try to do it the other way, you get:

regression=# ALTER TEXT SEARCH CONFIGURATION russian
ADD MAPPING FOR asciiword, asciihword, hword_asciipart WITH simple;
ERROR: duplicate key value violates unique constraint "pg_ts_config_map_index"

This is not very good --- we usually try to provide a more friendly
error message than "unique constraint violation" for duplicate system
catalog entries. Not sure how hard it is to fix.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster