Skip site navigation (1) Skip section navigation (2)

Re: What is the maximum encoding-conversion growth rate, anyway?

From: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
To: "Tatsuo Ishii" <ishii(at)postgresql(dot)org>
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-05-29 15:02:25
Message-ID: 23061.125.24.217.69.1180450945.squirrel@webmail.xs4all.nl (view raw or flat)
Thread:
Lists: pgsql-hackers
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.


Jeroen



In response to

Responses

pgsql-hackers by date

Next:From: Gregory StarkDate: 2007-05-29 15:23:38
Subject: Re: TOAST usage setting
Previous:From: Michael FuhrDate: 2007-05-29 14:34:11
Subject: Re: What is the maximum encoding-conversion growth rate, anyway?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group