Re: Add ENCODING option to COPY

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Add ENCODING option to COPY
Дата
Msg-id 19656.1297180438@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Add ENCODING option to COPY  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: Add ENCODING option to COPY  (Hitoshi Harada <umi.tanuki@gmail.com>)
Re: Add ENCODING option to COPY  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On fre, 2011-02-04 at 10:47 -0500, Tom Lane wrote:
>> The reason that we use quotes in CREATE DATABASE is that encoding
>> names aren't assumed to be valid SQL identifiers.  If this patch isn't
>> following the CREATE DATABASE precedent, it's the patch that's wrong,
>> not CREATE DATABASE.

> Since encoding names are built-in and therefore well known, and the
> names have been aligned with the SQL standard names, which are
> identifiers, I don't think this argument is valid (anymore).

What about "UTF-8"?
        regards, tom lane


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

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: SSI patch version 14
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql