pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bjoern Metzdorf <bm@turtle-entertainment.de>
To: Pgsql-Admin (E-mail) <pgsql-admin@postgresql.org>
Subject: Re: invalid multibyte character for locale
Date: Wed, 23 Feb 2005 22:12:46 +0100
Message-ID: <421CF1CE.3000800@turtle-entertainment.de> (raw)
In-Reply-To: <421CF15C.6010306@turtle-entertainment.de>
References: <421CF15C.6010306@turtle-entertainment.de>

I forgot to say that I am using UNICODE for database encoding (initdb -E 
UNICODE and createdb -E UNICODE).

Bjoern Metzdorf wrote:
> Hi,
> 
> I am testdriving postgresql 8.0.1.
> 
> On importing my old dump which works fine on 7.4.6 I am getting errors 
> like this one:
> 
> CREATE INDEX foobar_uvalue_key ON foobar USING btree 
> (upper((value)::text));
> ERROR:  invalid multibyte character for locale
> HINT:  The server's LC_CTYPE locale is probably incompatible with the 
> database encoding.
> 
> pg_controldatas output (this is an EM64T machine (debian pure64), but 
> the issue also comes on 32bit Linux):
> 
> pg_control version number:            74
> Catalog version number:               200411041
> Database system identifier:           4763589314759867390
> Database cluster state:               in production
> pg_control last modified:             Wed Feb 23 22:07:43 2005
> Current log file ID:                  1
> Next log file segment:                214
> Latest checkpoint location:           1/D56163E8
> Prior checkpoint location:            1/D56163A0
> Latest checkpoint's REDO location:    1/D56163E8
> Latest checkpoint's UNDO location:    0/0
> Latest checkpoint's TimeLineID:       1
> Latest checkpoint's NextXID:          3704
> Latest checkpoint's NextOID:          50861184
> Time of latest checkpoint:            Wed Feb 23 21:40:25 2005
> Database block size:                  8192
> Blocks per segment of large relation: 131072
> Bytes per WAL segment:                16777216
> Maximum length of identifiers:        64
> Maximum number of function arguments: 32
> Date/time type storage:               floating-point numbers
> Maximum length of locale name:        128
> LC_COLLATE:                           C
> LC_CTYPE:                             C
> 
> Should I be using de_DE or de_DE.UTF_8 locale? C locale always worked 
> fine for us (with 7.3 and 7.4).
> 
> Any hints?
> 
> Regards,
> Bjoern
> 



view thread (11+ messages)  latest in thread

Message-ID: <421CF1CE.3000800@turtle-entertainment.de>
Permalink:  ../421CF1CE.3000800@turtle-entertainment.de/
Also on:    postgresql.org/message-id/421CF1CE.3000800@turtle-entertainment.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: bm@turtle-entertainment.de
  Subject: Re: invalid multibyte character for locale
  In-Reply-To: <421CF1CE.3000800@turtle-entertainment.de>
  References: <421CF15C.6010306@turtle-entertainment.de> <421CF1CE.3000800@turtle-entertainment.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox