Re: patch: preload dictionary new version - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: patch: preload dictionary new version
Date
Msg-id AANLkTim0wGYySF85U_AjcXTnzo_gkUghJc13SaC2DbcS@mail.gmail.com
Whole thread Raw
In response to Re: patch: preload dictionary new version  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: patch: preload dictionary new version
List pgsql-hackers
2010/7/8 Tom Lane <tgl@sss.pgh.pa.us>:
> For example, the dictionary-load code could automatically execute
> the precompile step if it observed that the precompiled copy of the
> dictionary was missing or had an older file timestamp than the source.

There might be a problem in automatic precompiler -- Where should we
save the result? OS users of postgres servers don't have write-permission
to $PGSHARE in normal cases. Instead, we can store the precompiled
result to $PGDATA/pg_dict_cache or so.

> I like the idea of a precompiler step mainly because it still gives you
> most of the benefits of the patch on platforms without mmap.

I also like the precompiler solution. I think the most important benefit
in the approach is that we don't need to declare dictionaries to be preloaded
in configuration files; We can always use mmap() for all dictionary files.

-- 
Takahiro Itagaki


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: crash-recovery replay of CREATE TABLESPACE is broken in HEAD
Next
From: Itagaki Takahiro
Date:
Subject: Re: patch (for 9.1) string functions