Skip site navigation (1) Skip section navigation (2)

Re: Database Encoding

From: Aarni Ruuhimäki <aarni(at)kymi(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Database Encoding
Date: 2005-04-16 16:58:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice

Yes, and thanks for correction and guidance, another thing to consider when 
planning new system surroundings, well, the general idea ..., bearing in mind 
the installed locale(s) etc., amongst other things.

Long way to Tipitina's,


On Saturday 16 April 2005 19:18, you wrote:
> Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <aarni(at)kymi(dot)com> writes:
> > initdb -E LATIN1 ..., so one way to change it is to re-init.
> >
> > You can create databases with different encoding (from template1) with
> > same switch e.g.
> >
> > createdb mydb -E UTF8 ...
> Note that in most cases you can't just whack the encoding around without
> paying attention to locale.  I believe the only locale that really works
> with multiple encodings is "C" --- all the other ones assume a
> particular encoding.  You'll get very odd and unpleasant results from
> text sorting and functions like upper/lower if you have the database
> locale and encoding set incompatibly.
> Unfortunately we don't currently support changing locale on the fly ---
> so you can only set it at initdb time.  So the -E switch to createdb
> is a bit dangerous.
> This stuff is covered in the docs at
>    regards, tom lane

This is a bugfree broadcast to you
from **Kmail**
on **Fedora Core 2** linux system

In response to

pgsql-novice by date

Next:From: Abe BurnettDate: 2005-04-16 17:19:39
Subject: Help! "Access is Denied" Install Rolled back... WinXP, PostgreSQL 8.0.2
Previous:From: Tom LaneDate: 2005-04-16 16:18:35
Subject: Re: Database Encoding

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group