Skip site navigation (1) Skip section navigation (2)

Re: ToDo: preload for fulltext dictionary

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ToDo: preload for fulltext dictionary
Date: 2010-02-16 08:43:05
Message-ID: 162867791002160043u46213690v7fba2c78df40b563@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2010/2/16 Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>:
>
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>> The dictionary data could be shared or minimally dictionary could be
>> preloaded like some PL language.
>>
>> What do you think about this?
>
> Surely preloading is the most realistic approach, but I hope we would support
> dynamic allocation of shared memory, and load dictionaries in the area and
> share it with backends. We should avoid additonal calls of shmget() or mmap()
> in the additional shared memory allocation, but we can shrink shared buffers
> and reuse the area for general purposes. We often have serveral GB of shared
> buffers nowadays, so dividing some MB of buffers will not be problem.
>

I am for all solution, but using a shared memory isn't realistic now,
and can be a problem on MS Windows. More - it can be difficult with
some special custom non ro dictionaries.

Regards
Pavel

> Regards,
> ---
> Takahiro Itagaki
> NTT Open Source Software Center
>
>
>

In response to

pgsql-hackers by date

Next:From: David FetterDate: 2010-02-16 08:45:08
Subject: OpenVMS?
Previous:From: Jakub OuhrabkaDate: 2010-02-16 08:40:28
Subject: Re: Problem with 8.4 stats collector high load

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group