From 88b74dcddf08a14e2c17144c073d13f0f619b985 Mon Sep 17 00:00:00 2001 From: Tatsuo Ishii Date: Wed, 24 Jul 2002 05:51:56 +0000 Subject: [PATCH] Add pg_conversion system catalog. Update description for multibyte support. --- doc/src/sgml/catalogs.sgml | 86 +++++++++++++++++++++++++++++++++++++- doc/src/sgml/charset.sgml | 70 ++++++++++++++++--------------- 2 files changed, 121 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index ccb316e3c4..1ec90fd5ae 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -1,6 +1,6 @@ @@ -81,6 +81,11 @@ check constraints, unique / primary key constraints, foreign key constraints + + pg_conversion + encoding conversion information + + pg_database databases within this database cluster @@ -995,6 +1000,85 @@ + + pg_conversion + + + This system catalog stores encoding conversion information. See + CREATE CONVERSION for more information. + + + + pg_conversion Columns + + + + + Name + Type + References + Description + + + + + + conname + name + + Conversion name (unique within a namespace) + + + + connamespace + oid + pg_namespace.oid + + The OID of the namespace that contains this conversion + + + + + conowner + int4 + pg_shadow.usesysid + Owner (creator) of the namespace + + + + conforencoding + int4 + + Source(for) encoding ID + + + + contoencoding + int4 + + Destination(to) encoding ID + + + + conproc + regproc + pg_proc.oid + Conversion procedure + + + + condefault + boolean + + true if this is the default conversion + + + + +
+ + + pg_database diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index a19940ce9a..1561b5b61f 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -1,4 +1,4 @@ - + Localization</> @@ -326,7 +326,7 @@ perl: warning: Falling back to the standard locale ("C"). <para> Tatsuo Ishii (<email>ishii@postgresql.org</email>), - last updated 2000-03-22. + last updated 2002-07-24. Check <ulink url="http://www.sra.co.jp/people/t-ishii/PostgreSQL/">Tatsuo's web site</ulink> for more information. @@ -346,21 +346,19 @@ perl: warning: Falling back to the standard locale ("C"). overridden when you create a database using <application>createdb</application> or by using the SQL command <command>CREATE DATABASE</>. So you can have multiple databases each with - a different encoding system. + a different encoding system. Note that <acronym>MB</acronym> can + handle single byte characters sets such as ISO-8859-1. </para> + <para> + Multibyte support is enabled by default since PostgreSQL version 7.3. + </para> + <sect2> - <title>Enabling Multibyte Support + Supported character set encodings - Run configure with the multibyte option: - - -./configure --enable-multibyte=encoding_system - - - where encoding_system can be one of the - values in the following table: + Following encoding can be used as database encoding. Character Set Encodings @@ -508,23 +506,8 @@ perl: warning: Falling back to the standard locale ("C"). LATIN8, and LATIN10. + - - Here is an example of configuring - PostgreSQL to use a Japanese encoding by - default: - - -$ ./configure --enable-multibyte=EUC_JP - - - - - If the encoding system is omitted (./configure --enable-multibyte), - SQL_ASCII is assumed. - - - Setting the Encoding @@ -539,8 +522,8 @@ $ initdb -E EUC_JP sets the default encoding to EUC_JP (Extended Unix Code for Japanese). Note that you can use instead of if you prefer to type longer option strings. - If no option is given, the encoding - specified at configure time is used. + If no option is + given, SQL_ASCII is used. @@ -583,14 +566,17 @@ $ psql -l - Automatic encoding translation between server and + <title>Automatic encoding conversion between server and client PostgreSQL supports an automatic - encoding translation between server - and client for some encodings. The available combinations are - listed in . + encoding conversion between server and client for some + encodings. The conversion info is stored in pg_converson system + catalog. You can create a new conversion by using CREATE + CONVERSION. PostgreSQL comes with some predefined + conversions. They are listed in .
@@ -887,6 +873,18 @@ RESET CLIENT_ENCODING; be overridden using any of the other methods mentioned above.) + + + + Using client_encoding variable. + + If client_encoding variable in postgresql.conf is set, that + client encoding is automatically selected when a connection to the + server is made. (This can subsequently be overridden using any of the + other methods mentioned above.) + + + @@ -909,6 +907,10 @@ RESET CLIENT_ENCODING; The Unicode conversion functionality is automatically enabled if is specified. + + For 7.3, nor + is needed. +