Re: [PROPOSAL] Shared Ispell dictionaries - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [PROPOSAL] Shared Ispell dictionaries
Date
Msg-id CAFj8pRDm9nhZCf16XDer-eeciqy0wipR0Y4+ZdwGMAWuv-k6ag@mail.gmail.com
Whole thread Raw
In response to Re: [PROPOSAL] Shared Ispell dictionaries  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [PROPOSAL] Shared Ispell dictionaries  (Arthur Zakirov <a.zakirov@postgrespro.ru>)
List pgsql-hackers


2018-03-07 14:10 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:


2018-03-07 13:58 GMT+01:00 Arthur Zakirov <a.zakirov@postgrespro.ru>:
On Wed, Mar 07, 2018 at 01:47:25PM +0100, Pavel Stehule wrote:
> > Do you mean that a shared dictionary should be reloaded if its .affix
> > and .dict files was changed? IMHO we can store last modification
> > timestamp of them in a preprocessed file, and then we can rebuild the
> > dictionary if files was changed.
> >
>
> No, it is not necessary - just there should be commands (functions)  for
> preload dictiory and unload dictionary.

Oh understood. Tomas suggested those commands too earlier. I'll
implement them. But I think it is better to track files modification time
too. Because now, without the patch, users don't have to call additional
commands to refresh their dictionaries, so without such tracking we'll
made dictionaries maintenance harder.

Postgres hasn't any subsystem based on modification time, so introduction this sensitivity, I don't see, practical.

Usually the shared dictionaries are used for complex language based fulltext. The frequence of updates of these dictionaries is less than updates PostgreSQL. The czech dictionary is same 10 years.

Regards

Pavel
 

Regards

Pavel

 

--
Arthur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [PROPOSAL] Shared Ispell dictionaries
Next
From: Prabhat Sahu
Date:
Subject: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)