Re: Add ENCODING option to COPY

Поиск
Список
Период
Сортировка
От Hitoshi Harada
Тема Re: Add ENCODING option to COPY
Дата
Msg-id AANLkTikOAE5gAN-q21Kb6EnJ_jSbiFqYMN3KJ-Bk12PR@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Add ENCODING option to COPY  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
2011/2/8 Robert Haas <robertmhaas@gmail.com>:
> On Fri, Feb 4, 2011 at 1:54 PM, Hitoshi Harada <umi.tanuki@gmail.com> wrote:
>> 2011/2/5 Tom Lane <tgl@sss.pgh.pa.us>:
>>> Hitoshi Harada <umi.tanuki@gmail.com> writes:
>>>> 2011/2/5 Tom Lane <tgl@sss.pgh.pa.us>:
>>>>> Yeah, putting backend-only stuff into that header is a nonstarter.
>>>
>>>> Do you mean you think it' all right to define
>>>> pg_cached_encoding_conversion() in pg_conversion_fn.h?
>>>
>>> That seems pretty random too.  I still think you've designed this API
>>> badly and it'd be better to avoid exposing the FmgrInfo to callers
>>> by letting the function manage the cache internally.
>>
>> I'll try it in a few days, but only making struct that holds FmgrInfo
>> in a file local like tuplestorestate comes up with so far....
>
> We've been through several iterations of this patch now and haven't
> come up with something committable.  I think it's time to mark this
> one Returned with Feedback and revisit this for 9.2.

As I've been thinking these days. The design isn't fixed yet even now.
Thanks for all the reviews.

Regards,


--
Hitoshi Harada


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Steve Singer
Дата:
Сообщение: Re: pl/python explicit subtransactions
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql