Search Postgresql Archives

Re: initdb --encoding=LATIN1 fails on Windows

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Abraham, Danny" <danny_abraham@xxxxxxx>, "pgsql-general@xxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxx>
Subject: Re: initdb --encoding=LATIN1 fails on Windows
From: "Abraham, Danny" <danny_abraham@xxxxxxx>
Date: Thu, 16 Jul 2009 03:11:06 -0500
Accept-language: en-US
Acceptlanguage: en-US
Cc: "peter_e@xxxxxxx" <peter_e@xxxxxxx>
In-reply-to: <D460EBE8A3D1D246830283AE0478D8FED7BD25CED9@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Thread-index: AQHKBbphx6Cu31uHSUeYIkCZwqnOXZB3zcmw
Thread-topic: initdb --encoding=LATIN1 fails on Windows

Thanks. I guess my question is then, how should I configure
Windows to have the right locale so that I can create a LATIN1 encoding cluster.


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- initdb --encoding=LATIN1 fails on Windows
  - From: Abraham, Danny

Prev by Date: Re: How to DB export XML File in PostgreSQL?
Next by Date: Re: psql \du
Previous by thread: initdb --encoding=LATIN1 fails on Windows
Next by thread: Concurrency issue under very heay loads
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux