Re: BUG #15382: Error create dictionary in pg_dump

From: Андрей Ковальчук <mr(dot)kovalchuk(dot)andrey(at)gmail(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15382: Error create dictionary in pg_dump
Date: 2018-09-14 01:13:29
Message-ID: CAC-xdgppXQS1Njih2H6XqK09nDjDZ-Zq9UPonACu35Xd3nHytQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

It worked. Big thanks!

пт, 14 сент. 2018 г. в 10:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> =?UTF-8?B?0JDQvdC00YDQtdC5INCa0L7QstCw0LvRjNGH0YPQug==?= <
> mr(dot)kovalchuk(dot)andrey(at)gmail(dot)com> writes:
> > Understood why. But I did not know what doing. Particularly, I need for
> > upgrade my cluster to new version (9.5 to 10) and i used pg_upgrade
> > command. Upgrade in turn used pg_dump, pg_restore combination and I can't
> > affect for this.
>
> I think what you need to do is fix the dictionary definition in the
> source database, probably like this:
>
> ALTER TEXT SEARCH DICTIONARY "public"."thesaurus_apteka25" (
> dictionary = 'public.ispell_apteka25'
> );
>
> regards, tom lane
>

--
С уважением, Ковальчук Андрей.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message 'Bruce Momjian' 2018-09-14 02:20:33 Re: BUG #15373: null / utf-8
Previous Message David Rowley 2018-09-14 01:02:14 Re: BUG #15383: Join Filter cost estimation problem in 10.5