| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | jtv(at)xs4all(dot)nl |
| Cc: | mike(at)fuhr(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: What is the maximum encoding-conversion growth rate, anyway? |
| Date: | 2007-07-18 09:48:17 |
| Message-ID: | 20070718.184817.32729713.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sorry for dealy.
> On Tue, May 29, 2007 20:51, Tatsuo Ishii wrote:
>
> > Thinking more, it striked me that users can define arbitarily growing
> > rate by using CFREATE CONVERSION. So it seems we need functionality to
> > define the growing rate anyway.
>
> Would it make sense to define just the longest and shortest character
> lengths for an encoding? Then for any conversion you'd have a safe
> estimate of
>
> ceil(target_encoding.max_char_len / source_encoding.min_char_len)
>
> ...without going through every possible conversion.
This will not work since certain CONVERSION allows n char to m char
conversion.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2007-07-18 09:48:24 | Re: What is the maximum encoding-conversion growth rate, anyway? |
| Previous Message | Simon Riggs | 2007-07-18 09:21:16 | Re: SetBufferCommitInfoNeedsSave and race conditions |