| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Multibyte in autoconf |
| Date: | 1999-12-09 01:04:01 |
| Message-ID: | 384F0001.91E17222@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> On 1999-12-08, Tatsuo Ishii mentioned:
>
> > 1) initdb with no encoding augument (suppose that SQL_ASCII is set as
> > the default encoding in template1)
> >
> > 2) a user creates a database with no encoding augument. he thought
> > that the default encoding is EUC_JP.
>
> Why would the user think that? Can't he check if he's not sure? Call his
> db admin? Or did the db admin mess up the initdb?
>
As a Japanese,I don't want to specify an encoding for every initdb.
There are few selections except --with-mb=EUC_JP in Japan.
Isn't it preferable that PostgreSQL doesn't need an excellent db
admin ?
I do initdb frequently in current tree.
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-12-09 01:31:20 | Re: [HACKERS] Multibyte in autoconf |
| Previous Message | Peter Eisentraut | 1999-12-09 00:18:37 | More initdb follies |