pgsql/src/bin/initdb initdb.sh

Tatsuo Ishii writes:

CVSROOT: /home/projects/pgsql/cvsroot
Module name: pgsql
Changes by: ishii@hub.org 01/03/27 00:45:50

Modified files:
src/bin/initdb : initdb.sh

Log message:
Add checking for valid database encoding.

Why do you need this check? Shouldn't pg_encoding fail if the encoding id
is invalid?

--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/

Tatsuo Ishii writes:

CVSROOT: /home/projects/pgsql/cvsroot
Module name: pgsql
Changes by: ishii@hub.org 01/03/27 00:45:50

Modified files:
src/bin/initdb : initdb.sh

Log message:
Add checking for valid database encoding.

Why do you need this check? Shouldn't pg_encoding fail if the encoding id
is invalid?

No. Encoding ids greater than 31 are not valid for database (backend)
encoding. i.e. SJIS and BIG5 cannot be used for database encoding, but
are ok for frontend encoding.

Will fix create database command soon...
--
Tatsuo Ishii