Re: Add ENCODING option to COPY

Hitoshi Harada <umi.tanuki@gmail.com> writes:
> 2011/2/5 Tom Lane <tgl@sss.pgh.pa.us>:
>> 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.

> What about SET client_encoding TO encoding?

SET is in its own little world --- it will interchangeably take names
with or without quotes.  It is not a precedent to follow elsewhere.

			regards, tom lane