Re: BUG #15181: pg_dump - missing schema in CREATE TEXT SEARCH DICTIONARY
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #15181: pg_dump - missing schema in CREATE TEXT SEARCH DICTIONARY |
| Дата | |
| Msg-id | 11813.1525102225@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | BUG #15181: pg_dump - missing schema in CREATE TEXT SEARCH DICTIONARY (PG Bug reporting form <noreply@postgresql.org>) |
| Ответы |
Re: BUG #15181: pg_dump - missing schema in CREATE TEXT SEARCHDICTIONARY
|
| Список | pgsql-bugs |
=?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 по дате отправления: