Ron Johnson wrote:
> On 09/28/07 21:12, Tom Lane wrote:
>> Michael Fuhr <mike@fuhr.org> writes:
>>> No, it isn't. If you get UTF8 (formerly UNICODE) as a default then
>>> it's because initdb is picking it up from your environment.
>> Which initdb has done since 8.0. If the OP is such a rabid UTF8 fan,
>> one wonders why his default locale setting isn't using UTF8 ...
>
> He uses Windows?
Just FYI: The next version of the Windows installer will attempt to pick
up the locale from the environment. If that succeeds, it will use that
locale and UNICODE encoding. Only if that fails will it pick SQL_ASCII.
//Magnus