Re: initdb fails on Windows with encoding=LATIN1

From: "Abraham, Danny" <danny_abraham(at)bmc(dot)com>
To: "Abraham, Danny" <danny_abraham(at)bmc(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: initdb fails on Windows with encoding=LATIN1
Date: 2009-07-19 09:35:43
Message-ID: 2C0926ABD16BB641A8E2F11A5492004212EC5CB9AB@PHXCCRPRD01.adprod.bmc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We do need LATIN1.

The error message is:

initdb: encoding mismatch
The encoding you selected (LATIN1) and the encoding that the
selected locale uses (WIN1252) do not match. This would lead to
misbehavior in various character string processing functions.
Rerun initdb and either do not specify an encoding explicitly,
or choose a matching combination.

The version is 8.3.7.

It worked fine with 8.2.4

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pedro Doria Meunier 2009-07-19 10:15:39 Timestamp indicies not being used!
Previous Message Sim Zacks 2009-07-19 06:03:28 Re: Function does not exist