Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane?
От | Tom Lane |
---|---|
Тема | Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane? |
Дата | |
Msg-id | 28416.1187746002@sss.pgh.pa.us обсуждение исходный текст |
Ответы |
Re: Is ALTER TEXT SEARCH CONFIGURATION PARSER =
new_parser really sane?
Re: Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane? Re: Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane? |
Список | pgsql-hackers |
After starting to document this stuff I'm wondering whether it really makes sense to change the parser associated with a tsearch configuration. The problem is that the new parser might have an unrelated set of token types, but we don't do anything about updating the configuration's mappings. Ensuring sane behavior here would take a whole lot of new code, and I'm not sure that I see a use-case that justifies it. So I'm tempted to take out that particular ALTER capability altogether. I note that the corresponding feature of changing a dictionary's template on-the-fly doesn't exist (though it'd actually be a lot easier to support). Comments? regards, tom lane
В списке pgsql-hackers по дате отправления: