On Thursday 22 January 2009 10:51:41 Kent Tong wrote: > Reg Me Please wrote: > > Weel, you have two locales: one on the client and one the server. > > The former is needed for "translations" to the server whenver the two > > don't > > match. > > The latter is chosen at the CREATE DATABASE <dbname> ENCODING <encoding>. > > I am referring to the locale on the client that determines the text prompts > it > outputs. > > ----- > -- > Kent Tong > Wicket tutorials freely available at http://www.agileskills2.org/EWDW > Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA > -- > View this message in context: > http://www.nabble.com/how-to-specify-the-locale-that-psql-uses-tp21599904p2 >1601001.html Sent from the PostgreSQL - general mailing list archive at > Nabble.com.
In general, refer to "8.13.2. Encoding Handling" and "Chapter 22. Localization" on v8.3.5 documentation. Then you could use either the "\encoding" or the "SET client_encoding TO ..." into psql, the "PGCLIENTENCODING" environment variable or the "client_encoding" main configuration argument. Moreover you can check from psql and pl/pgsql the current client encoding with SELECT * FROM pg_client_encoding(); I hope any of these will help. -- Fahrbahn ist ein graues Band weisse Streifen, grüner Rand -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
