X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3E920D1E6C9 for ; Wed, 5 May 2004 12:41:16 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 99962-03 for ; Wed, 5 May 2004 12:40:51 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 54307D1E7CE for ; Wed, 5 May 2004 12:40:50 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i45FenhK003583; Wed, 5 May 2004 11:40:49 -0400 (EDT) To: Ludek Finstrle Cc: pgsql-admin@postgresql.org Subject: Re: initdb: FATAL: conversion between LATIN2 and UNICODE In-reply-to: <20040505112707.GA18319@soptik.pzkagis.cz> References: <20040505112707.GA18319@soptik.pzkagis.cz> Comments: In-reply-to Ludek Finstrle message dated "Wed, 05 May 2004 13:27:07 +0200" Date: Wed, 05 May 2004 11:40:49 -0400 Message-ID: <3582.1083771649@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/48 X-Sequence-Number: 13364 Ludek Finstrle 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