Re: pgsql/src/bin/initdb initdb.sh

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: peter_e(at)gmx(dot)net
Cc: ishii(at)hub(dot)org, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src/bin/initdb initdb.sh
Date: 2001-03-28 01:07:27
Message-ID: 20010328100727W.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

> Tatsuo Ishii writes:
>
> > CVSROOT: /home/projects/pgsql/cvsroot
> > Module name: pgsql
> > Changes by: ishii(at)hub(dot)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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2001-03-28 20:46:34 pgsql/doc/src/sgml mvcc.sgml
Previous Message Tom Lane 2001-03-27 18:02:19 pgsql/src/backend/optimizer/prep prepunion.c