Re: initdb: FATAL: conversion between LATIN2 and UNICODE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ludek Finstrle <ludek(dot)finstrle(at)pzkagis(dot)cz>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: initdb: FATAL: conversion between LATIN2 and UNICODE
Date: 2004-05-05 15:40:49
Message-ID: 3582.1083771649@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Ludek Finstrle <ludek(dot)finstrle(at)pzkagis(dot)cz> writes:
> bash-2.05$ /opt/software/postgresql/7.4.2/bin/initdb -D /data.sql/pgsql/7.4.X/standard -E UNICODE
> ...
> creating template1 database in /data.sql/pgsql/7.4.X/standard/base/1... ok
> initializing pg_shadow... FATAL: conversion between LATIN2 and UNICODE is not supported

Hm, it would seem that for some reason CLIENT_ENCODING is getting set to
LATIN2. Digging in the code, the only reason I can find for that to
happen within initdb is if you have set PGCLIENTENCODING as an
environment variable in your shell.

If you want to use LATIN2 as your client encoding, it'd probably be a
good idea not to use UNICODE as the database encoding ...

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jim Seymour 2004-05-05 15:56:25 Re: Limiting user access to a view only
Previous Message Sally Sally 2004-05-05 15:22:38 postgres mirroring (real-time)