From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ludek Finstrle <ludek.finstrle@pzkagis.cz>
Cc: pgsql-admin@postgresql.org
Subject: Re: initdb: FATAL: conversion between LATIN2 and UNICODE
Date: Wed, 05 May 2004 11:40:49 -0400
Message-ID: <3582.1083771649@sss.pgh.pa.us> (raw)
In-Reply-To: <20040505112707.GA18319@soptik.pzkagis.cz>
References: <20040505112707.GA18319@soptik.pzkagis.cz>
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
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: tgl@sss.pgh.pa.us, ludek.finstrle@pzkagis.cz
Subject: Re: initdb: FATAL: conversion between LATIN2 and UNICODE
In-Reply-To: <3582.1083771649@sss.pgh.pa.us>
References: <20040505112707.GA18319@soptik.pzkagis.cz> <3582.1083771649@sss.pgh.pa.us>
* 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