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
ceil(target_encoding.max_char_len / source_encoding.min_char_len)
...without going through every possible conversion.
In response to
pgsql-hackers by date
|Next:||From: Gregory Stark||Date: 2007-05-29 15:23:38|
|Subject: Re: TOAST usage setting|
|Previous:||From: Michael Fuhr||Date: 2007-05-29 14:34:11|
|Subject: Re: What is the maximum encoding-conversion growth rate, anyway?|