| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | peter_e(at)gmx(dot)net, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Multibyte in autoconf |
| Date: | 1999-12-08 08:33:36 |
| Message-ID: | 26011.944642016@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> If no --pgencoding, you get default (non-multibyte) coding even
>> if you compiled with --enable-mb.
> Not agreed. I think it would be better to give an error if no default
> encoding is not sepecified if configured with --enable-mb.
OK, I could live with that too. I think Peter's main point is that
there's no good reason to select a particular encoding at configure
time, even just as a "default". It'll be less confusing if initdb time
is the *only* time where you specify the particular MULTIBYTE encoding
you want.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 1999-12-08 09:17:05 | Re: [HACKERS] FreeBSD problem under heavy load |
| Previous Message | Tatsuo Ishii | 1999-12-08 08:26:14 | FreeBSD problem under heavy load |