picking the correct locale when doing initdb

From: "Harald Armin Massa" <haraldarminmassa(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: picking the correct locale when doing initdb
Date: 2006-03-16 10:15:06
Message-ID: 7be3f35d0603160215n5f04683u1ebc7d860a8b04dd@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

on bugs Magnus wrote:

> It's a matter of picking the correct locale when you initdb your database.

and he is PERFECTLY right. Getting the locale wrong while doing intidb can
really screw up ones day.

But: because of initdb being at the very beginning, it is a really tough
decision based on not a lot of information. I know, same problem appears in
"bigger" databases too.

On the same time my impression is that since PostgreSQL is totally easy to
install on win32 (ok, still need to understand what are user rights, and
have ntfs), lots of "first timers" are upgrading from My to Postgre.

What can we do to make their first steps with "encodings" and "locale"
easier?

Harald

--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
-
PostgreSQL - supported by a community that does not put you on hold

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Leonardo Francalanci 2006-03-16 10:33:34 Replication & web apps
Previous Message jia ding 2006-03-16 09:46:08 Re: \copy combine with SELECT