pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
encoding issue with postgres 8.0 2+ messages / 2 participants [nested] [flat]
* encoding issue with postgres 8.0 @ 2005-08-23 11:54 Kailash Vyas <kailash.vyas@gmail.com> 0 siblings, 1 reply; 2+ messages in thread From: Kailash Vyas @ 2005-08-23 11:54 UTC (permalink / raw) To: pgsql-admin; +Cc: pankaj@interlink-marketing.net hi i am migrating from postgres 7.3.9 to 8.0.3 I am facing a issue with encoding. By default when i create new database it creates as UNICODE In the earlier version the encoding was SQL_ASCII so i am passing this variable while initializing the db directory /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data -E SQL_ASCII but i get this warning when I run it. The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale en_GB.UTF-8. initdb: warning: encoding mismatch The encoding you selected (SQL_ASCII) and the encoding that the selected locale uses (UTF-8) are not known to match. This may lead to misbehavior in various character string processing functions. To fix this situation, rerun initdb and either do not specify an encoding explicitly, or choose a matching combination. what is the matching locale that i should be using in this case? thanks, kailash ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: encoding issue with postgres 8.0 @ 2005-08-23 14:20 Tom Lane <tgl@sss.pgh.pa.us> parent: Kailash Vyas <kailash.vyas@gmail.com> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2005-08-23 14:20 UTC (permalink / raw) To: Kailash Vyas <kailash.vyas@gmail.com>; +Cc: pgsql-admin; pankaj@interlink-marketing.net Kailash Vyas <kailash.vyas@gmail.com> writes: > The database cluster will be initialized with locale en_GB.UTF-8. > initdb: warning: encoding mismatch > The encoding you selected (SQL_ASCII) and the encoding that the selected > locale uses (UTF-8) are not known to match. This may lead to > misbehavior in various character string processing functions. To fix > this situation, rerun initdb and either do not specify an encoding > explicitly, or choose a matching combination. > what is the matching locale that i should be using in this case? If you want to use SQL_ASCII (ie, have no enforcement of encoding validity) the only really safe locale is "C". If you were using another combination with your old database and not having trouble, you may decide to ignore the warning and keep using that combination --- it'll work just as well or badly as before. But with what you have here, if you ever accidentally put any non-UTF8 data into the database, you'll likely get odd behavior. regards, tom lane ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2005-08-23 14:20 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2005-08-23 11:54 encoding issue with postgres 8.0 Kailash Vyas <kailash.vyas@gmail.com> 2005-08-23 14:20 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox