Re: BUG #15181: pg_dump - missing schema in CREATE TEXT SEARCHDICTIONARY
От | Adam Bartoszewicz |
---|---|
Тема | Re: BUG #15181: pg_dump - missing schema in CREATE TEXT SEARCHDICTIONARY |
Дата | |
Msg-id | 63d6eb96-844d-4d86-a46b-c19119b48bad@gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #15181: pg_dump - missing schema in CREATE TEXT SEARCH DICTIONARY (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-bugs |
You are right. "Dictionary = public.polish_ispell" resolves the problem. Thank you. Adam Bartoszewicz W dniu 2018-04-30 o 17:30, Tom Lane pisze: > =?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes: >> CREATE TEXT SEARCH DICTIONARY polish_thesaurus ( >> TEMPLATE = thesaurus, >> DictFile = polish, -- tsearch_data/polish.ths >> Dictionary = polish_ispell >> ); >> The bug ocurs when I try to dump and reload database structure. >> pg_dump creates command with missing schema: >> CREATE TEXT SEARCH DICTIONARY public.polish_thesaurus ( >> TEMPLATE = pg_catalog.thesaurus, >> dictfile = 'polish', dictionary = 'polish_ispell' ); > Hm. There is not a lot that pg_dump can do about that: it's really > a design shortcoming in the thesaurus template, namely that the > sub-dictionary is referenced by a string rather than by OID. You could > break it equally well with "ALTER TEXT SEARCH DICTIONARY polish_ispell > RENAME ...", or for that matter by trying to use polish_thesaurus in any > context where you didn't have the public schema in your search path. > > I'd recommend explicitly specifying "Dictionary = public.polish_ispell" > when you create the thesaurus dictionary. > > I suppose we should adjust the docs to point out this hazard, as well. > > regards, tom lane
В списке pgsql-bugs по дате отправления: