On Wed, 6 Sep 2000, vijayendra mohan agrawal wrote: > 2. createdb -E option can be used, but it seems it needs a re-compilation > which will make "pg_encoding" in your pgsql/bin directory. configure > with --enable-multibyte option and re-install postgreSQL... it should serve > the purpose. What if you just want to use single byte encodings such as Windows-CP1251? Which configuration option should you use? > 3. execute "createdb --help" for more details. --encoding=ENCODING should be > given for creating db with encoding, here "ENCODING" is the type of encoding > you want... > > Hope this helps... > > Thanks and regards, Thanks! and I have read the README.mb file. > Vijay Max Pyziur > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of [EMAIL PROTECTED] > Sent: Thursday, August 31, 2000 2:33 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: [ADMIN] 7.0.2 questions on encoding and compilation > > > Currently, I'm using the the 7.0.2 rpms from the postgresql.org > on a RH6.2 install. > > I have a few questions on it and the use of the -E flag. > > 1 - can 7.0.2 be optimized for i686 architecture or is > it only possible to compile for i386 architecture? > > 2 - Can createdb -E someencoding be used "straight out of the box" > with Postgresql 7.0.2 or does support need to be compiled into > the function? > > 3 - What are the list of arguments which can be taken with the > command createdb -E ? > > > > Thanks! > > > > > Max Pyziur BRAMA - Gateway Ukraine > [EMAIL PROTECTED] http://www.brama.com/ > >
