Re: What is the maximum encoding-conversion growth rate, anyway?
От
Tatsuo Ishii
Тема
Re: What is the maximum encoding-conversion growth rate,
anyway?
Дата
Msg-id
20070529.114900.23027278.t-ishii@sraoss.co.jp
Ответ на
Список
Дерево обсуждения
What is the maximum encoding-conversion growth rate, anyway? Tom Lane <tgl@sss.pgh.pa.us>
Re: What is the maximum encoding-conversion growth rate,
anyway? Tatsuo Ishii <ishii@postgresql.org>
Re: What is the maximum encoding-conversion growth rate, anyway? Tom Lane <tgl@sss.pgh.pa.us>
Re: What is the maximum encoding-conversion growth rate,
anyway? Tatsuo Ishii <ishii@postgresql.org>
Re: What is the maximum encoding-conversion growth rate, anyway? Michael Fuhr <mike@fuhr.org>
Re: What is the maximum encoding-conversion growth rate,
anyway? Tatsuo Ishii <ishii@postgresql.org>
Re: What is the maximum encoding-conversion growth rate,
anyway? Tatsuo Ishii <ishii@postgresql.org>
Re: What is the maximum encoding-conversion growth rate,
anyway? "Jeroen T. Vermeulen" <jtv@xs4all.nl>
Re: What is the maximum encoding-conversion growth rate,
anyway? Tatsuo Ishii <ishii@postgresql.org>
Re: What is the maximum encoding-conversion growth rate, anyway? Tom Lane <tgl@sss.pgh.pa.us>
Re: What is the maximum encoding-conversion growth rate, anyway? Michael Fuhr <mike@fuhr.org>
Re: What is the maximum encoding-conversion growth
rate, anyway? Bruce Momjian <bruce@momjian.us>
Re: What is the maximum encoding-conversion growth
rate, anyway? Bruce Momjian <bruce@momjian.us>
Re: What is the maximum encoding-conversion growth rate,
anyway? Tatsuo Ishii <ishii@postgresql.org>
Re: What is the maximum encoding-conversion growth
rate, anyway? Bruce Momjian <bruce@momjian.us>
> > Can we add a column to pg_conversion which represents the "growth > > rate"? This would reduce the rate for most encodings much smaller than > > 6. > > We need to do something, but the pg_conversion catalog seems a bad place > to put the info --- don't we have places that need to be able to do > conversion without catalog access? Can you tell me where? I thought conversion functions are always called by using OidFunctionCall5 thus we need to consult the pg_conversion catalog beforehand anyway. > Perhaps better would be to redefine the API for the conversion functions > so that they palloc their own result space. Then each conversion > function would have to know the maximum growth rate for its particular > conversion. This change would also make it feasible for a conversion > function to prescan the data and determine an exact output size, if that > seemed worthwhile because the potential growth rate was too extreme. -- Tatsuo Ishii SRA OSS, Inc. Japan
В списке pgsql-hackers по дате отправления