We had a dicussion about this already, but I think I came up with a
solution that works for everyone.

[proposal]

* If you configure with --enable-multibyte then you build a server and
clients that are multibyte enabled (as defined by the MULTIBYTE symbol).
If you don't use multibyte functionality then nothing will change, so this
would be the preferred option for package maintainers.

* If you configure with --enable-multibyte=XXX then XXX will be initdb's
default encoding, but XXX won't be used anywhere else. This option is for
those who insist on it; the preferred way to go about this would be the
respective option for initdb itself.

I'd leave the --with-mb option in there but hidden and make the new option
the published interface. Any protests?

-- 
Peter Eisentraut                  Sernanders vaeg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden


Thu, 13 Jan 2000 12:30:40 +0100 (MET)
Peter Eisentraut <e99re41@DoCS.UU.SE>
--enable-multibyte
Peter,

> * If you configure with --enable-multibyte then you build a server and
> clients that are multibyte enabled (as defined by the MULTIBYTE symbol).
> If you don't use multibyte functionality then nothing will change, so this
> would be the preferred option for package maintainers.

This actually would mean that the default encoding is set to
SQL_ASCII, I guess.  Since the encoding column in pg_database must be
filled with some value, we need to pick up a default value for it
anyway. Any encoding could be a candidate for the default, probably
SQL_ASCII is a good choice, IMHO. 
--
Tatsuo Ishii

Fri, 14 Jan 2000 10:57:26 +0900
Tatsuo Ishii <t-ishii@sra.co.jp>
Re: [HACKERS] --enable-multibyte