Postgres Pro
Downloads
Home   >   mailing lists

Re: initdb: FATAL: conversion between LATIN2 and UNICODE - Mailing list pgsql-admin

From Tom Lane
Subject Re: initdb: FATAL: conversion between LATIN2 and UNICODE
Date
Msg-id 3582.1083771649@sss.pgh.pa.us
Whole thread Raw
In response to initdb: FATAL: conversion between LATIN2 and UNICODE  (Ludek Finstrle <ludek.finstrle@pzkagis.cz>)
Responses Re: initdb: FATAL: conversion between LATIN2 and UNICODE  (Ludek Finstrle <luf@pzkagis.cz>)
List pgsql-admin
Tree view 
Ludek Finstrle <ludek.finstrle@pzkagis.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

pgsql-admin by date:

Previous
From: jseymour@LinxNet.com (Jim Seymour)
Date:
Subject: Re: Limiting user access to a view only
Next
From: Peter Eisentraut
Date:
Subject: Re: Limiting user access to a view only