| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Does initdb -e is working ? (Latest dev. snapshot) |
| Date: | 2000-01-29 16:58:31 |
| Message-ID: | Pine.LNX.4.21.0001291248530.364-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2000-01-29, Oleg Bartunov mentioned:
> One problem: I tried initdb -e koi8 and it doesn't works -
> createdb -E koi8 works as expected:
> I found -e for initdb , -E for createdb options for specifying encoding a
> little bit confused - why not just use one of them !
That's exactly why initdb uses -E as well now. But I see now it doesn't
reject invalid args because it interprets them as data directory. Will
fix.
Next time: initdb -? or initdb --help.
> Is't possible to change encoding of database except dump/destroydb/createdb
> cycle ? Is't worth to have pg_encoding to do this ?
pg_encoding is just a tools that maps encoding names to codes and vice
versa.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-01-29 16:59:00 | Re: [HACKERS] END/ABORT |
| Previous Message | The Hermit Hacker | 2000-01-29 16:58:15 | Re: [HACKERS] Copyright |