Re: initdb: FATAL: conversion between LATIN2 and UNICODE

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: initdb: FATAL: conversion between LATIN2 and UNICODE
Дата
Msg-id 3582.1083771649@sss.pgh.pa.us
обсуждение исходный текст
Ответ на initdb: FATAL: conversion between LATIN2 and UNICODE  (Ludek Finstrle <ludek.finstrle@pzkagis.cz>)
Ответы Re: initdb: FATAL: conversion between LATIN2 and UNICODE
Список pgsql-admin
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 по дате отправления:

Предыдущее
От: jseymour@LinxNet.com (Jim Seymour)
Дата:
Сообщение: Re: Limiting user access to a view only
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Limiting user access to a view only