| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] Shared Ispell dictionaries |
| Date: | 2018-03-07 13:10:12 |
| Message-ID: | CAFj8pRB=FWzq=FfoSPeoJfXG4a7P0Abp+0XKmet3E34tiuTUFA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2018-03-07 13:58 GMT+01:00 Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)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.
Regards
Pavel
>
> --
> Arthur Zakirov
> Postgres Professional: http://www.postgrespro.com
> Russian Postgres Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-03-07 13:12:32 | Re: [PROPOSAL] Shared Ispell dictionaries |
| Previous Message | Arthur Zakirov | 2018-03-07 12:58:48 | Re: [PROPOSAL] Shared Ispell dictionaries |