Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
88b74dcd
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
88b74dcd
编写于
7月 24, 2002
作者:
T
Tatsuo Ishii
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Add pg_conversion system catalog. Update description for multibyte support.
上级
b4b3c63b
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
121 addition
and
35 deletion
+121
-35
doc/src/sgml/catalogs.sgml
doc/src/sgml/catalogs.sgml
+85
-1
doc/src/sgml/charset.sgml
doc/src/sgml/charset.sgml
+36
-34
未找到文件。
doc/src/sgml/catalogs.sgml
浏览文件 @
88b74dcd
<!--
Documentation of the system catalogs, directed toward PostgreSQL developers
$Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.4
6 2002/07/22 20:23:19 petere
Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.4
7 2002/07/24 05:51:55 ishii
Exp $
-->
<chapter id="catalogs">
...
...
@@ -81,6 +81,11 @@
<entry>check constraints, unique / primary key constraints, foreign key constraints</entry>
</row>
<row>
<entry>pg_conversion</entry>
<entry>encoding conversion information</entry>
</row>
<row>
<entry>pg_database</entry>
<entry>databases within this database cluster</entry>
...
...
@@ -995,6 +1000,85 @@
</sect1>
<sect1 id="catalog-pg-conversion">
<title>pg_conversion</title>
<para>
This system catalog stores encoding conversion information. See
<command>CREATE CONVERSION</command> for more information.
</para>
<table>
<title>pg_conversion Columns</title>
<tgroup cols=4>
<thead>
<row>
<entry>Name</entry>
<entry>Type</entry>
<entry>References</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>conname</entry>
<entry><type>name</type></entry>
<entry></entry>
<entry>Conversion name (unique within a namespace)</entry>
</row>
<row>
<entry>connamespace</entry>
<entry><type>oid</type></entry>
<entry>pg_namespace.oid</entry>
<entry>
The OID of the namespace that contains this conversion
</entry>
</row>
<row>
<entry>conowner</entry>
<entry><type>int4</type></entry>
<entry>pg_shadow.usesysid</entry>
<entry>Owner (creator) of the namespace</entry>
</row>
<row>
<entry>conforencoding</entry>
<entry><type>int4</type></entry>
<entry></entry>
<entry>Source(for) encoding ID</entry>
</row>
<row>
<entry>contoencoding</entry>
<entry><type>int4</type></entry>
<entry></entry>
<entry>Destination(to) encoding ID</entry>
</row>
<row>
<entry>conproc</entry>
<entry><type>regproc</type></entry>
<entry>pg_proc.oid</entry>
<entry>Conversion procedure</entry>
</row>
<row>
<entry>condefault</entry>
<entry><type>boolean</type></entry>
<entry></entry>
<entry>true if this is the default conversion</entry>
</row>
</tbody>
</tgroup>
</table>
</sect1>
<sect1 id="catalog-pg-database">
<title>pg_database</title>
...
...
doc/src/sgml/charset.sgml
浏览文件 @
88b74dcd
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.2
4 2002/04/03 05:39:27 petere
Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.2
5 2002/07/24 05:51:56 ishii
Exp $ -->
<chapter id="charset">
<title>Localization</>
...
...
@@ -326,7 +326,7 @@ perl: warning: Falling back to the standard locale ("C").
<para>
Tatsuo Ishii (<email>ishii@postgresql.org</email>),
last updated 200
0-03-22
.
last updated 200
2-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>
<sect2>
<title>Enabling Multibyte Support</title>
<para>
Run configure with the multibyte option:
Multibyte support is enabled by default since PostgreSQL version 7.3.
</para>
<synopsis>
./configure --enable-multibyte<optional>=<replaceable>encoding_system</replaceable></optional>
</synopsis>
<sect2>
<title>Supported character set encodings</title>
where <replaceable>encoding_system</replaceable> can be one of the
values in the following table:
<para>
Following encoding can be used as database encoding.
<table tocentry="1">
<title>Character Set Encodings</title>
...
...
@@ -508,23 +506,8 @@ perl: warning: Falling back to the standard locale ("C").
<literal>LATIN8</>, and <literal>LATIN10</>.
</para>
</important>
</sect2>
<para>
Here is an example of configuring
<productname>PostgreSQL</productname> to use a Japanese encoding by
default:
<screen>
$ <userinput>./configure --enable-multibyte=EUC_JP</userinput>
</screen>
</para>
<para>
If the encoding system is omitted (<literal>./configure --enable-multibyte</literal>),
<literal>SQL_ASCII</> is assumed.
</para>
</sect2>
<sect2>
<title>Setting the Encoding</title>
...
...
@@ -539,8 +522,8 @@ $ <userinput>initdb -E EUC_JP</>
sets the default encoding to <literal>EUC_JP</literal> (Extended Unix Code for Japanese).
Note that you can use <option>--encoding</option> instead of <option>-E</option> if you prefer
to type longer option strings.
If no <option>-E</> or <option>--encoding</option> option is
given, the encoding
specified at configure time
is used.
If no <option>-E</> or <option>--encoding</option> option is
given, SQL_ASCII
is used.
</para>
<para>
...
...
@@ -583,14 +566,17 @@ $ <userinput>psql -l</userinput>
</sect2>
<sect2>
<title>Automatic encoding
translat
ion between server and
<title>Automatic encoding
convers
ion between server and
client</title>
<para>
<productname>PostgreSQL</productname> supports an automatic
encoding translation between server
and client for some encodings. The available combinations are
listed in <xref linkend="multibyte-translation-table">.
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 <command>CREATE
CONVERSION</command>. PostgreSQL comes with some predefined
conversions. They are listed in <xref
linkend="multibyte-translation-table">.
</para>
<table tocentry="1" id="multibyte-translation-table">
...
...
@@ -887,6 +873,18 @@ RESET CLIENT_ENCODING;
be overridden using any of the other methods mentioned above.)
</para>
</listitem>
<listitem>
<para>
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.)
</para>
</listitem>
</itemizedlist>
</para>
</sect2>
...
...
@@ -909,6 +907,10 @@ RESET CLIENT_ENCODING;
The Unicode conversion functionality is automatically enabled
if <option>--enable-multibyte</option> is specified.
</para>
<para>
For 7.3, <option>--enable-unicode-conversion</option> nor
<option>--enable-multibyte</option> is needed.
</para>
</sect2>
<sect2>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录