2010/9/7 Robert Haas <robertmhaas@gmail.com>:
> On Tue, Sep 7, 2010 at 12:44 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>>> I don't see how you could do anything with this that you can't do with
>>> the existing implementation. It's not as if you can store pointers
>>> into an mmap'd block and then count on them being valid the next time
>>> you map the file... it might not end up at the same offset.
>>
>> you can, but you have to do preallocation and you have to use a FIXED flag.
>
> MAP_FIXED? As TFM says: "Because requiring a fixed address for a
> mapping is less portable, the use of this option is discouraged."
yes, I know. This will be used for proprietary Czech language - 95% of
postgresql instalations are on Linux, 10% on MS Windows (in Czech
Republic)
I don't plan to try to move this module to core. And it's useless -
other languages has not our problems.
Regards
Pavel
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise Postgres Company
>