From: Tom Lane Date: Fri, 28 Jul 2006 15:33:28 +0000 (+0000) Subject: Make it clearer that not every Postgres character set can be used as a X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=e7c059950f5e6e69ba004a95daff4dd9231a6c55;p=users%2Fbernd%2Fpostgres.git Make it clearer that not every Postgres character set can be used as a server-side character set. --- diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index 12a772d7be..d3e864f10f 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -304,14 +304,13 @@ initdb --locale=sv_SE allows you to store text in a variety of character sets, including single-byte character sets such as the ISO 8859 series and multiple-byte character sets such as EUC (Extended Unix - Code), UTF-8, and Mule internal code. All character sets can be - used transparently throughout the server. (If you use extension - functions from other sources, it depends on whether they wrote - their code correctly.) The default character set is selected while + Code), UTF-8, and Mule internal code. All supported character sets + can be used transparently by clients, but a few are not supported + for use within the server (that is, as a server-side encoding). + The default character set is selected while initializing your PostgreSQL database cluster using initdb. It can be overridden when you - create a database using createdb or by using the - SQL command CREATE DATABASE. So you can have multiple + create a database, so you can have multiple databases each with a different character set. @@ -320,17 +319,18 @@ initdb --locale=sv_SE shows the character sets available - for use in the server. + for use in PostgreSQL. Server Character Sets - + Name Description Language + Server?