On Sat, 29 Jan 2000, Tatsuo Ishii wrote:
> Date: Sat, 29 Jan 2000 20:32:43 +0900
> From: Tatsuo Ishii <t-ishii@sra.co.jp>
> To: oleg@sai.msu.su
> Cc: pgsql-hackers@postgreSQL.org
> Subject: Re: [HACKERS] Does initdb -e is working ? (Latest dev. snapshot)
>
> > Probably I miss something
> > I tried latest snapshot and notice some changes in configure.
> > Everything went smoothly on my Linux 2.2.14, glic 2.1.2 system.
> >
> > One problem: I tried initdb -e koi8 and it doesn't works -
>
> Because someone has changed -e to -E.
OK. this is good if we have now similar option,
I suggest Peter should reflect this change in initdb --help
Usage: initdb [options] datadir
Options: [-D, --pgdata] <datadir> Location for this database -W, --pwprompt Prompt for a password for
thenew superuser's -e, --encoding <encoding> Set the default multibyte encoding for new databases ^^^
>
> > I found -e for initdb , -E for createdb options for specifying encoding a
> > little bit confused - why not just use one of them !
>
> So now both initdb and createdb use -E as you expect. I think this is
> a good thing.
>
> > Is't possible to change encoding of database except dump/destroydb/createdb
> > cycle ? Is't worth to have pg_encoding to do this ?
>
> update pg_database set encoding = pg_char_to_encoding('KOI8');
>
> should work for you. However I'm a little bit worried about the
> syscache staffs. It would be safer to shutdown postmaster then issue
> the update command from standalone postgres.
Thanks, it works fine.
Regards, Oleg
> --
> Tatsuo Ishii
>
>
> ************
>
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83