Re: Add ENCODING option to COPY

Поиск
Список
Период
Сортировка
От Itagaki Takahiro
Тема Re: Add ENCODING option to COPY
Дата
Msg-id AANLkTi=kU9k6Yk6ZPvAXjiWsmYATQ6n10-63XZLZbLZ4@mail.gmail.com
обсуждение исходный текст
Ответ на Add ENCODING option to COPY  (Hitoshi Harada <umi.tanuki@gmail.com>)
Ответы Re: Add ENCODING option to COPY  (Hitoshi Harada <umi.tanuki@gmail.com>)
Список pgsql-hackers
On Sat, Jan 15, 2011 at 02:25, Hitoshi Harada <umi.tanuki@gmail.com> wrote:
> The patch overrides client_encoding by the added ENCODING option, and
> restores it as soon as copy is done.

We cannot do that because error messages should be encoded in the original
encoding even during COPY commands with encoding option. Error messages
could contain non-ASCII characters if lc_messages is set.

> I see some complaints ask to use
> pg_do_encoding_conversion() instead of
> pg_client_to_server/server_to_client(), but the former will surely add
> slight overhead per reading line

If we want to reduce the overhead, we should cache the conversion procedure
in CopyState. How about adding something like "FmgrInfo file_to_server_covv"
into it?

-- 
Itagaki Takahiro


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

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: Seeking Mentors for Funded Reviewers
Следующее
От: Richard Broersma
Дата:
Сообщение: Re: Seeking Mentors for Funded Reviewers