From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: preload dictionary new version |
Date: | 2010-07-12 04:02:09 |
Message-ID: | 12652.1278907329@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> writes:
> 2010/7/8 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
Yeah. Actually we'd *have* to do something like that because $PGSHARE
should contain only architecture-independent files, while the
precompiled files would presumably have dependencies on endianness etc.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | KaiGai Kohei | 2010-07-12 04:09:08 | Re: Reworks of DML permission checks |
Previous Message | Itagaki Takahiro | 2010-07-12 03:32:24 | Re: patch (for 9.1) string functions |