Skip to content

G
Gpdb

Greenplum / Gpdb

通知 7
Star 1
Fork 0
G
Gpdb

体验新版 GitCode，发现更多精彩内容 >>

提交 d07454f5 编写于 作者: P Peter Eisentraut
浏览文件
操作

Markup additions and spell check. (covers Admin Guide)

上级 84956e71
展开全部 隐藏空白更改
内联 并排
Showing with 548 addition and 537 deletion
doc/src/sgml/backup.sgml
浏览文件 @ d07454f5
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.12 2001/08/25 18:52:41 tgl Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.13 2001/09/09 23:52:12 petere Exp $ -->
<chapter id="backup">
<title>Backup and Restore</title>
......@@ -236,10 +236,10 @@ cat <replaceable class="parameter">filename</replaceable>.* | psql <replaceable
<formalpara>
<title>Use the custom dump format (V7.1).</title>
<para>
If PostgreSQL was built on a system with the zlib compression library
If PostgreSQL was built on a system with the <application>zlib</> compression library
installed, the custom dump format will compress data as it writes it
to the output file. For large databases, this will produce similar dump
sizes to using gzip, but has the added advantage that the tables can be
sizes to using <command>gzip</command>, but has the added advantage that the tables can be
restored selectively. The following command dumps a database using the
custom dump format:
......
doc/src/sgml/charset.sgml
浏览文件 @ d07454f5
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.8 2001/05/03 21:38:44 momjian Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.9 2001/09/09 23:52:12 petere Exp $ -->
<chapter id="charset">
<title>Localization</>
......@@ -53,7 +53,7 @@
<firstterm>Locale</> support refers to an application respecting
cultural preferences regarding alphabets, sorting, number
formatting, etc. <productname>PostgreSQL</> uses the standard ISO
C and POSIX-like locale facilities provided by the server operating
C and <acronym>POSIX</acronym>-like locale facilities provided by the server operating
system. For additional information refer to the documentation of your
system.
</para>
......@@ -103,27 +103,27 @@ export LANG=sv_SE
<tgroup cols="2">
<tbody>
<row>
<entry>LC_COLLATE</>
<entry><envar>LC_COLLATE</></>
<entry>String sort order</>
</row>
<row>
<entry>LC_CTYPE</>
<entry><envar>LC_CTYPE</></>
<entry>Character classification (What is a letter? The upper-case equivalent?)</>
</row>
<row>
<entry>LC_MESSAGES</>
<entry><envar>LC_MESSAGES</></>
<entry>Language of messages</>
</row>
<row>
<entry>LC_MONETARY</>
<entry><envar>LC_MONETARY</></>
<entry>Formatting of currency amounts</>
</row>
<row>
<entry>LC_NUMERIC</>
<entry><envar>LC_NUMERIC</></>
<entry>Formatting of numbers</>
</row>
<row>
<entry>LC_TIME</>
<entry><envar>LC_TIME</></>
<entry>Formatting of dates and times</>
</row>
</tbody>
......@@ -204,7 +204,7 @@ export LANG=sv_SE
<para>
If locale support doesn't work in spite of the explanation above,
check that the locale support in your operating system is okay.
check that the locale support in your operating system is correctly configured.
To check whether a given locale is installed and functional you
can use <application>Perl</>, for example. Perl has also support
for locales and if a locale is broken <command>perl -v</> will
......@@ -226,9 +226,9 @@ perl: warning: Falling back to the standard locale ("C").
<para>
Check that your locale files are in the right location. Possible
locations include: <filename>/usr/lib/locale</filename> (Linux,
Solaris), <filename>/usr/share/locale</filename> (Linux),
<filename>/usr/lib/nls/loc</filename> (DUX 4.0). Check the locale
locations include: <filename>/usr/lib/locale</filename> (<systemitem class="osname">Linux</>,
<systemitem class="osname">Solaris</>), <filename>/usr/share/locale</filename> (<systemitem class="osname">Linux</>),
<filename>/usr/lib/nls/loc</filename> (<systemitem class="osname">DUX 4.0</>). Check the locale
man page of your system if you are not sure.
</para>
......@@ -258,8 +258,8 @@ perl: warning: Falling back to the standard locale ("C").
<para>
Multibyte (<acronym>MB</acronym>) support is intended to allow
<productname>Postgres</productname> to handle
multiple-byte character sets such as EUC (Extended Unix Code), Unicode and
Mule internal code. With <acronym>MB</acronym> enabled you can use multi-byte
multiple-byte character sets such as <acronym>EUC</> (Extended Unix Code), Unicode and
Mule internal code. With <acronym>MB</acronym> enabled you can use multibyte
character sets in regular expressions (regexp), LIKE, and some
other functions. The default
encoding system is selected while initializing your
......@@ -304,63 +304,63 @@ perl: warning: Falling back to the standard locale ("C").
</thead>
<tbody>
<row>
<entry>SQL_ASCII</entry>
<entry>ASCII</entry>
<entry><literal>SQL_ASCII</literal></entry>
<entry><acronym>ASCII</acronym></entry>
</row>
<row>
<entry>EUC_JP</entry>
<entry>Japanese EUC</entry>
<entry><literal>EUC_JP</literal></entry>
<entry>Japanese <acronym>EUC</></entry>
</row>
<row>
<entry>EUC_CN</entry>
<entry>Chinese EUC</entry>
<entry><literal>EUC_CN</literal></entry>
<entry>Chinese <acronym>EUC</></entry>
</row>
<row>
<entry>EUC_KR</entry>
<entry>Korean EUC</entry>
<entry><literal>EUC_KR</literal></entry>
<entry>Korean <acronym>EUC</></entry>
</row>
<row>
<entry>EUC_TW</entry>
<entry>Taiwan EUC</entry>
<entry><literal>EUC_TW</literal></entry>
<entry>Taiwan <acronym>EUC</acronym></entry>
</row>
<row>
<entry>UNICODE</entry>
<entry>Unicode(UTF-8)</entry>
<entry><literal>UNICODE</literal></entry>
<entry>Unicode (<acronym>UTF</acronym>-8)</entry>
</row>
<row>
<entry>MULE_INTERNAL</entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry>Mule internal</entry>
</row>
<row>
<entry>LATIN1</entry>
<entry><literal>LATIN1</literal></entry>
<entry>ISO 8859-1 English and some European languages</entry>
</row>
<row>
<entry>LATIN2</entry>
<entry><literal>LATIN2</literal></entry>
<entry>ISO 8859-2 English and some European languages</entry>
</row>
<row>
<entry>LATIN3</entry>
<entry><literal>LATIN3</literal></entry>
<entry>ISO 8859-3 English and some European languages</entry>
</row>
<row>
<entry>LATIN4</entry>
<entry><literal>LATIN4</literal></entry>
<entry>ISO 8859-4 English and some European languages</entry>
</row>
<row>
<entry>LATIN5</entry>
<entry><literal>LATIN5</literal></entry>
<entry>ISO 8859-5 English and some European languages</entry>
</row>
<row>
<entry>KOI8</entry>
<entry>KOI8-R(U)</entry>
<entry><literal>KOI8</literal></entry>
<entry><acronym>KOI</acronym>8-R(U)</entry>
</row>
<row>
<entry>WIN</entry>
<entry><literal>WIN</literal></entry>
<entry>Windows CP1251</entry>
</row>
<row>
<entry>ALT</entry>
<entry><literal>ALT</literal></entry>
<entry>Windows CP866</entry>
</row>
</tbody>
......@@ -395,7 +395,7 @@ perl: warning: Falling back to the standard locale ("C").
% initdb -E EUC_JP
</programlisting>
sets the default encoding to EUC_JP (Extended Unix Code for Japanese).
sets the default encoding to <literal>EUC_JP</literal> (Extended Unix Code for Japanese).
Note that you can use "--encoding" instead of "-E" if you prefer
to type longer option strings.
If no -E or --encoding option is given, the encoding
......@@ -409,7 +409,7 @@ perl: warning: Falling back to the standard locale ("C").
% createdb -E EUC_KR korean
</programlisting>
will create a database named "korean" with EUC_KR encoding.
will create a database named <database>korean</database> with <literal>EUC_KR</literal> encoding.
Another way to accomplish this is to use a SQL command:
<programlisting>
......@@ -419,7 +419,7 @@ CREATE DATABASE korean WITH ENCODING = 'EUC_KR';
The encoding for a database is represented as an
<firstterm>encoding column</firstterm> in the
<literal>pg_database</literal> system catalog.
You can see that by using -l or \l of psql
You can see that by using <option>-l</option> or <command>\l</command> of <command>psql</command>
command.
<programlisting>
......@@ -462,26 +462,26 @@ $ psql -l
</thead>
<tbody>
<row>
<entry>EUC_JP</entry>
<entry>EUC_JP, SJIS</entry>
<entry><literal>EUC_JP</literal></entry>
<entry><literal>EUC_JP</literal>, <literal>SJIS</literal></entry>
</row>
<row>
<entry>EUC_TW</entry>
<entry>EUC_TW, BIG5</entry>
<entry><literal>EUC_TW</literal></entry>
<entry><literal>EUC_TW</literal>, <literal>BIG5</literal></entry>
</row>
<row>
<entry>LATIN2</entry>
<entry>LATIN2, WIN1250</entry>
<entry><literal>LATIN2</literal></entry>
<entry><literal>LATIN2</literal>, <literal>WIN1250</literal></entry>
</row>
<row>
<entry>LATIN5</entry>
<entry>LATIN5, WIN, ALT</entry>
<entry><literal>LATIN5</literal></entry>
<entry><literal>LATIN5</literal>, <literal>WIN</literal>, <literal>ALT</literal></entry>
</row>
<row>
<entry>MULE_INTERNAL</entry>
<entry>EUC_JP, SJIS, EUC_KR, EUC_CN,
EUC_TW, BIG5, LATIN1 to LATIN5,
WIN, ALT, WIN1250</entry>
<entry><literal>MULE_INTERNAL</literal></entry>
<entry><literal>EUC_JP</literal>, <literal>SJIS</literal>, <literal>EUC_KR</literal>, <literal>EUC_CN</literal>,
<literal>EUC_TW</literal>, <literal>BIG5</literal>, <literal>LATIN1</literal> to <literal>LATIN5</literal>,
<literal>WIN</literal>, <literal>ALT</literal>, <literal>WIN1250</literal></entry>
</row>
</tbody>
</tgroup>
......@@ -501,7 +501,7 @@ $ psql -l
<application>psql</application>.
<command>\encoding</command> allows you to change frontend
encoding on the fly. For
example, to change the encoding to SJIS, type:
example, to change the encoding to <literal>SJIS</literal>, type:
<programlisting>
\encoding SJIS
......@@ -511,9 +511,9 @@ $ psql -l
<listitem>
<para>
Using libpq functions.
Using <application>libpq</> functions.
<command>\encoding</command> actually calls
PQsetClientEncoding() for its purpose.
<function>PQsetClientEncoding()</function> for its purpose.
<programlisting>
int PQsetClientEncoding(PGconn *<replaceable>conn</replaceable>, const char *<replaceable>encoding</replaceable>)
......@@ -530,7 +530,7 @@ int PQclientEncoding(const PGconn *<replaceable>conn</replaceable>)
</programlisting>
Note that it returns the "encoding id," not the encoding symbol string
such as "EUC_JP." To convert an encoding id to an encoding symbol, you
such as <literal>EUC_JP</literal>. To convert an encoding id to an encoding symbol, you
can use:
<programlisting>
......@@ -591,8 +591,8 @@ RESET CLIENT_ENCODING;
encodings has been supported since PostgreSQL 7.1.
Because this requires huge conversion tables, it's not enabled by default.
To enable this feature, run configure with the
--enable-unicode-conversion option. Note that this requires
the --enable-multibyte option also.
<option>--enable-unicode-conversion</option> option. Note that this requires
the <option>--enable-multibyte</option> option also.
</para>
</sect2>
......@@ -600,9 +600,9 @@ RESET CLIENT_ENCODING;
<title>What happens if the translation is not possible?</title>
<para>
Suppose you choose EUC_JP for the backend, LATIN1 for the frontend,
then some Japanese characters could not be translated into LATIN1. In
this case, a letter that cannot be represented in the LATIN1 character set
Suppose you choose <literal>EUC_JP</literal> for the backend, <literal>LATIN1</literal> for the frontend,
then some Japanese characters could not be translated into <literal>LATIN1</literal>. In
this case, a letter that cannot be represented in the <literal>LATIN1</literal> character set
would be transformed as:
<programlisting>
......@@ -623,7 +623,7 @@ RESET CLIENT_ENCODING;
<para>
<ulink url="ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/cjk.inf">
ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/cjk.inf</ulink>
Detailed explanations of EUC_JP, EUC_CN, EUC_KR, EUC_TW
Detailed explanations of <literal>EUC_JP</literal>, <literal>EUC_CN</literal>, <literal>EUC_KR</literal>, <literal>EUC_TW</literal>
appear in section 3.2.
</para>
</listitem>
......@@ -631,14 +631,14 @@ RESET CLIENT_ENCODING;
<listitem>
<para>
Unicode: <ulink url="http://www.unicode.org/">http://www.unicode.org/</ulink>
The homepage of UNICODE.
The homepage of Unicode.
</para>
</listitem>
<listitem>
<para>
<literal>RFC 2044</literal>
UTF-8 is defined here.
<literal>UTF</literal>-8 is defined here.
</para>
</listitem>
</itemizedlist>
......@@ -763,7 +763,8 @@ Sorry for my Eglish and C code, I'm not native :-)
<listitem>
<para>
Success depends on proper system locales. This has been tested
with RH6.0 and Slackware 3.6, with cs_CZ.iso8859-2 locale.
with <systemitem class="osname">Red Hat 6.0</> and <systemitem
class="osname">Slackware 3.6</>, with <literal>cs_CZ.iso8859-2</literal> locale.
</para>
</listitem>
......@@ -777,7 +778,7 @@ Sorry for my Eglish and C code, I'm not native :-)
<listitem>
<para>
WIN1250 encoding is useable only for M$W ODBC clients. The
WIN1250 encoding is usable only for Windows ODBC clients. The
characters are recoded on the fly, to be displayed and stored
back properly.
</para>
......@@ -864,7 +865,7 @@ LC_TIME=cs_CZ.ISO8859-2
<step>
<para>
Install ODBC driver for PgSQL on your M$ Windows machine.
Install ODBC driver for <productname>PostgreSQL</productname> on your Windows machine.
</para>
</step>
......@@ -953,7 +954,7 @@ HostCharset <replaceable>host_spec</> <replaceable>host_charset</>
cannot use different encodings on the same host at the same
time. It is also inconvenient when you boot your client hosts into
multiple operating systems. Nevertheless, when these restrictions are
not limiting and you do not need multi-byte characters than it is a
not limiting and you do not need multibyte characters than it is a
simple and effective solution.
</para>
</sect1>
......
doc/src/sgml/client-auth.sgml
浏览文件 @ d07454f5
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.18 2001/09/06 03:23:38 momjian Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.19 2001/09/09 23:52:12 petere Exp $ -->
<chapter id="client-authentication">
<title>Client Authentication</title>
......@@ -39,8 +39,8 @@
the server's machine, it makes sense to assign database user names
that match their Unix user ids. However, a server that accepts remote
connections may have many users who have no local account, and in such
cases there need be no connection between database usernames and Unix
usernames.
cases there need be no connection between database user names and Unix
user names.
</para>
<sect1 id="pg-hba.conf">
......@@ -52,8 +52,8 @@
<para>
Client authentication is controlled by the file
<filename>pg_hba.conf</filename> in the $PGDATA directory, e.g.,
<filename>/usr/local/pgsql/data/pg_hba.conf</filename>. (HBA stands
<filename>pg_hba.conf</filename> in the data directory, e.g.,
<filename>/usr/local/pgsql/data/pg_hba.conf</filename>. (<acronym>HBA</> stands
for host-based authentication.) A default <filename>pg_hba.conf</filename>
file is installed when the
data area is initialized by <application>initdb</application>.
......@@ -156,7 +156,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
<variablelist>
<varlistentry>
<term>trust</>
<term><literal>trust</></term>
<listitem>
<para>
The connection is allowed unconditionally. This method allows
......@@ -167,7 +167,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
</varlistentry>
<varlistentry>
<term>reject</>
<term><literal>reject</></term>
<listitem>
<para>
The connection is rejected unconditionally. This is mostly
......@@ -177,7 +177,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
</varlistentry>
<varlistentry>
<term>password</>
<term><literal>password</></term>
<listitem>
<para>
The client is required to supply a password with the connection
......@@ -201,7 +201,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
</varlistentry>
<varlistentry>
<term>md5</>
<term><literal>md5</></term>
<listitem>
<para>
Like the <literal>password</literal> method, but the password
......@@ -215,7 +215,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
</varlistentry>
<varlistentry>
<term>crypt</>
<term><literal>crypt</></term>
<listitem>
<para>
Like the <literal>md5</literal> method but uses older crypt
......@@ -225,7 +225,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
</varlistentry>
<varlistentry>
<term>krb4</>
<term><literal>krb4</></term>
<listitem>
<para>
Kerberos V4 is used to authenticate the user. This is only
......@@ -235,7 +235,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
</varlistentry>
<varlistentry>
<term>krb5</term>
<term><literal>krb5</></term>
<listitem>
<para>
Kerberos V5 is used to authenticate the user. This is only
......@@ -245,7 +245,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
</varlistentry>
<varlistentry>
<term>ident</term>
<term><literal>ident</></term>
<listitem>
<para>
The identity of the user as determined on login to the
......@@ -258,15 +258,16 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
server; ident authentication should never be used for remote hosts
whose administrators are not trustworthy.)
On operating systems
supporting SO_PEERCRED requests for Unix domain sockets,
supporting <symbol>SO_PEERCRED</> requests for Unix domain sockets,
ident authentication is possible for local connections;
the system is then asked for the connecting user's identity.
</para>
<para>
On systems without SO_PEERCRED requests, ident authentication
On systems without <symbol>SO_PEERCRED</> requests, ident authentication
is only available for TCP/IP connections. As a workaround,
it is possible to
specify the localhost address 127.0.0.1 and make connections
specify the <systemitem class="systemname">localhost</> address
<systemitem class="systemname">127.0.0.1</> and make connections
to this address.
</para>
<para>
......@@ -280,7 +281,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
</varlistentry>
<varlistentry>
<term>pam</term>
<term><literal>pam</></term>
<listitem>
<para>
This authentication type operates similar to
......@@ -289,11 +290,11 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
authentication mechanism. The <replaceable>authentication
option</replaceable> following the <literal>pam</> keyword
specifies the service name that will be passed to PAM. The
default service name is <firstterm>postgresql</firstterm>.
For more information about PAM, please read <ulink
url="http://www.kernel.org/pub/linux/libs/pam/">Linux-PAM
Page</ulink> and <ulink
url="http://www.sun.com/software/solaris/pam/">Solaris-PAM
default service name is <literal>postgresql</literal>.
For more information about PAM, please read the <ulink
url="http://www.kernel.org/pub/linux/libs/pam/"><productname>Linux-PAM</productname>
Page</ulink> and/or the <ulink
url="http://www.sun.com/software/solaris/pam/"><systemitem class="osname">Solaris</> PAM
Page</ulink>.
</para>
</listitem>
......@@ -316,19 +317,19 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable
</varlistentry>
</variablelist>
The first record that matches a connection attempt's client IP address
and requested database name is used to do the authentication step.
There is no <quote>fall-through</> or <quote>backup</>: if
one record is chosen and the
authentication fails, the following records are not considered. If
no record matches, the access will be denied.
The first record that matches the client IP address and requested
database name of a connection attempt is used to do the
authentication step. There is no <quote>fall-through</> or
<quote>backup</>: if one record is chosen and the authentication
fails, the following records are not considered. If no record
matches, the access will be denied.
</para>
<para>
The <filename>pg_hba.conf</filename> file is loaded only on startup
and when the <application>postmaster</> receives a SIGHUP signal. If
and when the <application>postmaster</> receives a <systemitem>SIGHUP</systemitem> signal. If
you edit the file on an active system, you will need to issue a
SIGHUP to the <application>postmaster</> using <application>kill</>
<systemitem>SIGHUP</systemitem> to the <application>postmaster</> using <application>kill</>
to make it re-read the file.
</para>
......@@ -511,7 +512,7 @@ host all 192.168.0.0 255.255.0.0 ident omicron
<prompt>kadmin% </><userinput>ank -randkey postgres/server.my.domain.org</>
<prompt>kadmin% </><userinput>ktadd -k krb5.keytab postgres/server.my.domain.org</>
</screen>
Read the <productname>Kerberos</> documentation for defails.
Read the <productname>Kerberos</> documentation for details.
</para>
<para>
......@@ -528,7 +529,7 @@ host all 192.168.0.0 255.255.0.0 ident omicron
<listitem>
<para>
The <productname>Postgres</> service is assumed to be have two
components, the service name and a hostname, canonicalized as
components, the service name and a host name, canonicalized as
in Version 4 (i.e., with all domain suffixes removed).
</para>
</listitem>
......@@ -561,8 +562,8 @@ host all 192.168.0.0 255.255.0.0 ident omicron
</para>
<para>
If you use mod_auth_krb and mod_perl on your Apache web server,
you can use AuthType KerberosV5SaveCredentials with a mod_perl
If you use <application>mod_auth_krb</application> and <application>mod_perl</application> on your <productname>Apache</productname> web server,
you can use <literal>AuthType KerberosV5SaveCredentials</literal> with a <application>mod_perl</application>
script. This gives secure database access over the web, no extra
passwords required.
</para>
......@@ -610,7 +611,7 @@ host all 192.168.0.0 255.255.0.0 ident omicron
</para>
<para>
On systems supporting SO_PEERCRED requests for Unix-domain sockets,
On systems supporting <symbol>SO_PEERCRED</symbol> requests for Unix-domain sockets,
ident authentication can also be applied to local connections. In this
case, no security risk is added by using ident authentication; indeed
it is a preferable choice for such a system.
......@@ -654,12 +655,12 @@ host all 192.168.0.0 255.255.0.0 ident omicron
linkend="example-pg-hba.conf"> is shown in <xref
linkend="example-pg-ident.conf">. In this example setup, anyone
logged in to a machine on the 192.168 network that does not have
the Unix user name bryanh, ann, or robert would not be granted access.
Unix user robert would only be allowed access when he tries to
connect as Postgres user <quote>bob</quote>, not as <quote>robert</quote>
or anyone else. <quote>ann</quote> would only be allowed to connect as
<quote>ann</>. User bryanh would be allowed to connect as either
<quote>bryanh</> himself or as <quote>guest1</>.
the Unix user name <systemitem>bryanh</>, <systemitem>ann</>, or <systemitem>robert</> would not be granted access.
Unix user <systemitem>robert</> would only be allowed access when he tries to
connect as Postgres user <systemitem>bob</>, not as <systemitem>robert</>
or anyone else. <systemitem>ann</> would only be allowed to connect as
<systemitem>ann</>. User <systemitem>bryanh</> would be allowed to connect as either
<systemitem>bryanh</> himself or as <systemitem>guest1</>.
</para>
<example id="example-pg-ident.conf">
......@@ -726,7 +727,7 @@ FATAL 1: Database "testdb" does not exist in the system catalog.
</para>
<para>
Note that the postmaster's stderr log may contain more information
Note that the server log may contain more information
about an authentication failure than is reported to the client.
If you are confused about the reason for a failure, check the log.
</para>
......
doc/src/sgml/install-win32.sgml
浏览文件 @ d07454f5
......@@ -22,7 +22,7 @@
Windows. The makefiles included in the source distribution are
written for <productname>Microsoft Visual C++</productname> and will
probably not work with other systems. It should be possible to
compile the libaries manually in other cases.
compile the libraries manually in other cases.
</para>
<tip>
......@@ -99,7 +99,7 @@
</para>
<para>
If you plan to do development using libpq on this machine, you will
If you plan to do development using <application>libpq</application> on this machine, you will
have to add the <filename>src\include</filename> and
<filename>src\interfaces\libpq</filename> subdirectories of the
source tree to the include path in your compilers settings.
......
doc/src/sgml/installation.sgml
浏览文件 @ d07454f5
此差异已折叠。
doc/src/sgml/maintenance.sgml
浏览文件 @ d07454f5
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.2 2001/08/27 23:42:34 tgl Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.3 2001/09/09 23:52:12 petere Exp $
-->
<chapter id="maintenance">
......@@ -94,7 +94,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.2 2001/08/27 23:42:34
In normal <productname>PostgreSQL</productname> operation, an UPDATE or
DELETE of a row does not immediately remove the old <firstterm>tuple</>
(version of the row). This approach is necessary to gain the benefits
of multi-version concurrency control (see the User's Guide): the tuple
of multiversion concurrency control (see the User's Guide): the tuple
must not be deleted while
it is still potentially visible to other transactions. But eventually,
an outdated or deleted tuple is no longer of interest to any transaction.
......@@ -106,7 +106,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.2 2001/08/27 23:42:34
<para>
Clearly, a table that receives frequent updates or deletes will need
to be vacuumed more often than tables that are seldom updated. It may
be useful to set up periodic cron tasks that vacuum only selected tables,
be useful to set up periodic <application>cron</> tasks that vacuum only selected tables,
skipping tables that are known not to change often. This is only likely
to be helpful if you have both large heavily-updated tables and large
seldom-updated tables --- the extra cost of vacuuming a small table
......@@ -170,7 +170,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.2 2001/08/27 23:42:34
statistics updates if the statistical distribution of the data is not
changing much. A simple rule of thumb is to think about how much
the minimum and maximum values of the columns in the table change.
For example, a timestamp column that contains the time of row update
For example, a <type>timestamp</type> column that contains the time of row update
will have a constantly-increasing maximum value as rows are added and
updated; such a column will probably need more frequent statistics
updates than, say, a column containing URLs for pages accessed on a
......@@ -233,12 +233,12 @@ $Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.2 2001/08/27 23:42:34
<para>
Prior to <productname>PostgreSQL</productname> 7.2, the only defense
against XID wraparound was to re-initdb at least every 4 billion
against XID wraparound was to re-<command>initdb</> at least every 4 billion
transactions. This of course was not very satisfactory for high-traffic
sites, so a better solution has been devised. The new approach allows an
installation to remain up indefinitely, without initdb or any sort of
installation to remain up indefinitely, without <command>initdb</> or any sort of
restart. The price is this maintenance requirement:
<emphasis>every table in the database must be VACUUMed at least once every
<emphasis>every table in the database must be vacuumed at least once every
billion transactions</emphasis>.
</para>
......@@ -342,7 +342,7 @@ VACUUM
user-created databases that are to be marked <literal>datallowconn</> =
<literal>false</> in <filename>pg_database</>, since there isn't any
convenient way to vacuum a database that you can't connect to. Note
that VACUUM's automatic warning message about unvacuumed databases will
that <command>VACUUM</command>'s automatic warning message about unvacuumed databases will
ignore <filename>pg_database</> entries with <literal>datallowconn</> =
<literal>false</>, so as to avoid giving false warnings about these
databases; therefore it's up to you to ensure that such databases are
......
doc/src/sgml/manage-ag.sgml
浏览文件 @ d07454f5
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/manage-ag.sgml,v 2.13 2001/03/29 18:25:10 petere Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/manage-ag.sgml,v 2.14 2001/09/09 23:52:12 petere Exp $
-->
<chapter id="managing-databases">
......@@ -85,11 +85,11 @@ CREATE DATABASE <replaceable>name</>
createdb <replaceable class="parameter">dbname</replaceable>
</synopsis>
<filename>createdb</> does no magic. It connects to the template1
<command>createdb</> does no magic. It connects to the template1
database and executes the <command>CREATE DATABASE</> command,
exactly as described above. It uses <application>psql</> program
internally. The reference page on createdb contains the invocation
details. In particular, createdb without any arguments will create
internally. The reference page on <command>createdb</> contains the invocation
details. In particular, <command>createdb</> without any arguments will create
a database with the current user name, which may or may not be what
you want.
</para>
......@@ -132,7 +132,7 @@ export PGDATA2
setenv PGDATA2 /home/postgres/data
</programlisting>
</informalexample>
in csh or tcsh. You have to make sure that this environment
in <application>csh</> or <application>tcsh</>. You have to make sure that this environment
variable is always defined in the server environment, otherwise
you won't be able to access that database. Therefore you probably
want to set it in some sort of shell start-up file or server
......
doc/src/sgml/regress.sgml
浏览文件 @ d07454f5
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/regress.sgml,v 1.18 2001/08/06 22:53:26 tgl Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/regress.sgml,v 1.19 2001/09/09 23:52:12 petere Exp $ -->
<chapter id="regress">
<title id="regress-title">Regression Tests</title>
......@@ -102,7 +102,7 @@
<prompt>$ </prompt><userinput>gmake installcheck</userinput>
</screen>
The tests will expect to contact the server at the local host and the
default port number, unless directed otherwise by PGHOST and PGPORT
default port number, unless directed otherwise by <envar>PGHOST</envar> and <envar>PGPORT</envar>
environment variables.
</para>
......@@ -178,7 +178,7 @@
<title>Date and time differences</title>
<para>
Some of the queries in the <quote>timestamp</quote> test will
Some of the queries in the <filename>timestamp</filename> test will
fail if you run the test on the day of a daylight-savings time
changeover, or the day before or after one. These queries assume
that the intervals between midnight yesterday, midnight today and
......@@ -189,21 +189,21 @@
<para>
Most of the date and time results are dependent on the time zone
environment. The reference files are generated for time zone
PST8PDT (Berkeley, California) and there will be apparent
<literal>PST8PDT</literal> (Berkeley, California) and there will be apparent
failures if the tests are not run with that time zone setting.
The regression test driver sets environment variable
<envar>PGTZ</envar> to <literal>PST8PDT</literal>, which normally
ensures proper results. However, your system must provide library
support for the PST8PDT time zone, or the time zone-dependent
support for the <literal>PST8PDT</literal> time zone, or the time zone-dependent
tests will fail. To verify that your machine does have this
support, type the following:
<screen>
<prompt>$ </prompt><userinput>env TZ=PST8PDT date</userinput>
</screen>
The command above should have returned the current system time in
the PST8PDT time zone. If the PST8PDT database is not available,
the <literal>PST8PDT</literal> time zone. If the <literal>PST8PDT</literal> database is not available,
then your system may have returned the time in GMT. If the
PST8PDT time zone is not available, you can set the time zone
<literal>PST8PDT</literal> time zone is not available, you can set the time zone
rules explicitly:
<programlisting>
PGTZ='PST8PDT7,M04.01.0,M10.05.03'; export PGTZ
......@@ -220,7 +220,7 @@ PGTZ='PST8PDT7,M04.01.0,M10.05.03'; export PGTZ
<para>
Some systems using older time zone libraries fail to apply
daylight-savings corrections to dates before 1970, causing
pre-1970 PDT times to be displayed in PST instead. This will
pre-1970 <acronym>PDT</acronym> times to be displayed in <acronym>PST</acronym> instead. This will
result in localized differences in the test results.
</para>
</sect2>
......@@ -300,7 +300,7 @@ ORDER BY to that particular query and thereby eliminate the bogus
</para>
<para>
You might wonder why we don't ORDER all the regress test SELECTs to
You might wonder why we don't order all the regress test queries explicitly to
get rid of this issue once and for all. The reason is that that would
make the regression tests less useful, not more, since they'd tend
to exercise query plan types that produce ordered results to the
......@@ -352,7 +352,7 @@ testname/platformpattern=comparisonfilename
</synopsis>
The test name is just the name of the particular regression test
module. The platform pattern is a pattern in the style of
expr(1) (that is, a regular expression with an implicit
<citerefentry><refentrytitle>expr</><manvolnum>1</></citerefentry> (that is, a regular expression with an implicit
<literal>^</literal> anchor
at the start). It is matched against the platform name as printed
by <filename>config.guess</filename> followed by
......@@ -365,19 +365,19 @@ testname/platformpattern=comparisonfilename
<para>
For example: some systems using older time zone libraries fail to apply
daylight-savings corrections to dates before 1970, causing
pre-1970 PDT times to be displayed in PST instead. This causes a
pre-1970 <acronym>PDT</acronym> times to be displayed in <acronym>PST</acronym> instead. This causes a
few differences in the <filename>horology</> regression test.
Therefore, we provide a variant comparison file,
<filename>horology-no-DST-before-1970.out</filename>, which includes
the results to be expected on these systems. To silence the bogus
<quote>failure</quote> message on HPPA platforms, resultmap
<quote>failure</quote> message on <systemitem>HPPA</systemitem> platforms, <filename>resultmap</filename>
includes
<programlisting>
horology/hppa=horology-no-DST-before-1970
</programlisting>
which will trigger on any machine for which config.guess's output
which will trigger on any machine for which the output of <command>config.guess</command>
begins with <quote><literal>hppa</literal></quote>. Other lines
in resultmap select the variant comparison file for other
in <filename>resultmap</> select the variant comparison file for other
platforms where it's appropriate.
</para>
......
doc/src/sgml/release.sgml
浏览文件 @ d07454f5
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.98 2001/08/14 23:38:20 momjian Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.99 2001/09/09 23:52:12 petere Exp $
-->
<appendix id="release">
......@@ -239,7 +239,7 @@ outer join syntax.
<listitem>
<para>
The previous C function manager did not
handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The new
handle NULLs properly, nor did it support 64-bit <acronym>CPU</acronym>'s (Alpha). The new
function manager does. You can continue using your old custom
functions, but you may want to rewrite them in the future to use the new
function manager call interface.
......@@ -723,12 +723,12 @@ ecpg changes (Michael)
<varlistentry>
<term>
Updated psql
Updated <application>psql</application>
</term>
<listitem>
<para>
<application>psql</application>, our interactive terminal monitor, has been
updated with a variety of new features. See the psql manual page for details.
updated with a variety of new features. See the <application>psql</application> manual page for details.
</para>
</listitem>
</varlistentry>
......@@ -783,7 +783,7 @@ ecpg changes (Michael)
<listitem>
<para>
The date/time types <type>datetime</type> and
<type>timespan</type> have been superceded by the
<type>timespan</type> have been superseded by the
SQL92-defined types <type>timestamp</type> and
<type>interval</type>. Although there has been some effort to
ease the transition by allowing
......@@ -1176,7 +1176,7 @@ New multibyte encodings
<para>
This is basically a cleanup release for 6.5.2. We have added a new
pgaccess that was missing in 6.5.2, and installed an NT-specific fix.
<application>PgAccess</> that was missing in 6.5.2, and installed an NT-specific fix.
</para>
......@@ -1394,7 +1394,7 @@ Add Win1250 (Czech) support (Pavel Behal)
<listitem>
<para>
<application>pg_dump</application> takes advantage of the new
MVCC features to give a consistant database dump/backup while
MVCC features to give a consistent database dump/backup while
the database stays online and available for queries.
</para>
</listitem>
......@@ -1457,7 +1457,7 @@ Add Win1250 (Czech) support (Pavel Behal)
<listitem>
<para>
We continue to expand our port list, this time including
WinNT/ix86 and NetBSD/arm32.
<systemitem class="osname">Windows NT</>/<systemitem>ix86</> and <systemitem class="osname">NetBSD</>/<systemitem>arm32</>.
</para>
</listitem>
</varlistentry>
......@@ -1482,7 +1482,7 @@ Add Win1250 (Czech) support (Pavel Behal)
<para>
New and updated material is present throughout the
documentation. New <acronym>FAQ</acronym>s have been
contributed for SGI and AIX platforms.
contributed for <systemitem class="osname">SGI</> and <systemitem class="osname">AIX</> platforms.
The <citetitle>Tutorial</citetitle> has introductory information
on <acronym>SQL</acronym> from Stefan Simkovics.
For the <citetitle>User's Guide</citetitle>, there are
......@@ -1547,7 +1547,7 @@ Add Win1250 (Czech) support (Pavel Behal)
<para>
Keep the above in mind if you are using
<filename>contrib/refint.*</filename> triggers for
referential integrity. Additional technics are required now. One way is
referential integrity. Additional techniques are required now. One way is
to use <command>LOCK parent_table IN SHARE ROW EXCLUSIVE MODE</command>
command if a transaction is going to update/delete a primary key and
use <command>LOCK parent_table IN SHARE MODE</command> command if a
......@@ -1557,7 +1557,7 @@ Add Win1250 (Czech) support (Pavel Behal)
<para>
Note that if you run a transaction in SERIALIZABLE mode then you must
execute the <command>LOCK</command> commands above before execution of any
DML statement
<acronym>DML</acronym> statement
(<command>SELECT/INSERT/DELETE/UPDATE/FETCH/COPY_TO</command>) in the
transaction.
</para>
......@@ -1901,8 +1901,8 @@ for the <citetitle>Programmer's Guide</citetitle>.
</listitem>
<listitem>
<para>
Jan also contributed a second procedural language, PL/pgSQL, to go with the
original PL/pgTCL procedural language he contributed last release.
Jan also contributed a second procedural language, <application>PL/pgSQL</application>, to go with the
original <application>PL/pgTCL</application> procedural language he contributed last release.
</para>
</listitem>
......@@ -2194,7 +2194,7 @@ new Makefile.shlib for shared library configuration(Tom)
-->
<para>
This is a bugfix release for 6.3.x.
This is a bug-fix release for 6.3.x.
Refer to the release notes for version 6.3 for a more complete summary of new features.
</para>
<para>
......@@ -2218,7 +2218,7 @@ Correctly handles function calls on the left side of BETWEEN and LIKE clauses.
</para>
<para>
A dump/restore is NOT required for those running 6.3 or 6.3.1. A
'make distclean', 'make', and 'make install' is all that is required.
<literal>make distclean</>, <literal>make</>, and <literal>make install</> is all that is required.
This last step should be performed while the postmaster is not running.
You should re-link any custom applications that use <productname>Postgres</productname> libraries.
</para>
......@@ -2306,7 +2306,7 @@ Improvements to the configuration autodetection for installation.
</para>
<para>
A dump/restore is NOT required for those running 6.3. A
'make distclean', 'make', and 'make install' is all that is required.
<literal>make distclean</>, <literal>make</>, and <literal>make install</> is all that is required.
This last step should be performed while the postmaster is not running.
You should re-link any custom applications that use <productname>Postgres</productname> libraries.
</para>
......@@ -2435,18 +2435,18 @@ Better identify tcl and tk libs and includes(Bruce)
use them in the target list.
</para>
<para>
Second, 6.3 uses unix domain sockets rather than TCP/IP by default. To
Second, 6.3 uses Unix domain sockets rather than TCP/IP by default. To
enable connections from other machines, you have to use the new
postmaster -i option, and of course edit pg_hba.conf. Also, for this
reason, the format of pg_hba.conf has changed.
postmaster -i option, and of course edit <filename>pg_hba.conf</filename>. Also, for this
reason, the format of <filename>pg_hba.conf</filename> has changed.
</para>
<para>
Third, char() fields will now allow faster access than varchar() or
text. Specifically, the text and varchar() have a penalty for access to
any columns after the first column of this type. char() used to also
Third, <type>char()</type> fields will now allow faster access than <type>varchar()</type> or
<type>text</type>. Specifically, the <type>text</> and <type>varchar()</type> have a penalty for access to
any columns after the first column of this type. <type>char()</type> used to also
have this access penalty, but it no longer does. This may suggest that
you redesign some of your tables, especially if you have short character
columns that you have defined as varchar() or text. This and other
columns that you have defined as <type>varchar()</type> or <type>text</type>. This and other
changes make 6.3 even faster than earlier releases.
</para>
<para>
......@@ -2455,7 +2455,7 @@ Better identify tcl and tk libs and includes(Bruce)
See the <citetitle>Administrator's Guide</citetitle> for more
information. There is a new table, pg_shadow, which is used to store
user information and user passwords, and it by default only SELECT-able
by the postgres super-user. pg_user is now a view of pg_shadow, and is
by the <systemitem>postgres</systemitem> super-user. pg_user is now a view of pg_shadow, and is
SELECT-able by PUBLIC. You should keep using pg_user in your
application without changes.
</para>
......@@ -2467,20 +2467,20 @@ Better identify tcl and tk libs and includes(Bruce)
</para>
<para>
We also have real deadlock detection code. No more sixty-second
timeouts. And the new locking code implements a FIFO better, so there
timeouts. And the new locking code implements a <acronym>FIFO</acronym> better, so there
should be less resource starvation during heavy use.
</para>
<para>
Many complaints have been made about inadequate documenation in previous
Many complaints have been made about inadequate documentation in previous
releases. Thomas has put much effort into many new manuals for this
release. Check out the doc/ directory.
</para>
<para>
For performance reasons, time travel is gone, but can be implemented
using triggers (see pgsql/contrib/spi/README). Please check out the new
using triggers (see <filename>pgsql/contrib/spi/README</filename>). Please check out the new
\d command for types, operators, etc. Also, views have their own
permissions now, not based on the underlying tables, so permissions on
them have to be set separately. Check /pgsql/interfaces for some new
them have to be set separately. Check <filename>/pgsql/interfaces</filename> for some new
ways to talk to <productname>Postgres</productname>.
</para>
<para>
......@@ -2735,7 +2735,7 @@ upon updating the executables.
</para>
<para>
Another way to avoid dump/reload is to use the following SQL command
from psql to update the existing system table:
from <command>psql</command> to update the existing system table:
<programlisting>
update pg_aggregate set aggfinalfn = 'cash_div_flt8'
......@@ -2800,7 +2800,7 @@ This migration requires a complete dump of the 6.1 database and a
restore of the database in 6.2.
</para>
<para>
Note that the pg_dump and pg_dumpall utility from 6.2 should be used
Note that the <command>pg_dump</command> and <command>pg_dumpall</command> utility from 6.2 should be used
to dump the 6.1 database.
</para>
</sect2>
......@@ -3014,9 +3014,9 @@ pg_dumpall now returns proper status, portability fix(Bruce)
</para>
<para>
Three new data types (datetime, timespan, and circle) have been added to
Three new data types (<type>datetime</type>, <type>timespan</type>, and <type>circle</type>) have been added to
the native set of <productname>Postgres</productname> types. Points, boxes, paths, and polygons
have had their output formats made consistant across the data types.
have had their output formats made consistent across the data types.
The polygon output in misc.out has only been spot-checked for correctness
relative to the original regression output.
</para>
......@@ -3043,7 +3043,7 @@ optimizer which uses <firstterm>genetic</firstterm>
<para>
The float8 regression test fails on at least some platforms. This is due
to differences in implementations of pow() and exp() and the signaling
to differences in implementations of <function>pow()</function> and <function>exp()</function> and the signaling
mechanisms used for overflow and underflow conditions.
</para>
......@@ -3379,21 +3379,21 @@ releases.
<para>
Here is a new migration file for 1.02.1. It includes the 'copy' change
and a script to convert old ascii files.
and a script to convert old <acronym>ASCII</acronym> files.
</para>
<note>
<para>
The following notes are for the benefit of users who want to migrate
databases from postgres95 1.01 and 1.02 to postgres95 1.02.1.
databases from <productname>Postgres95</> 1.01 and 1.02 to <productname>Postgres95</> 1.02.1.
</para>
<para>
If you are starting afresh with postgres95 1.02.1 and do not need
If you are starting afresh with <productname>Postgres95</> 1.02.1 and do not need
to migrate old databases, you do not need to read any further.
</para>
</note>
<para>
In order to upgrade older postgres95 version 1.01 or 1.02 databases to
In order to upgrade older <productname>Postgres95</> version 1.01 or 1.02 databases to
version 1.02.1, the following steps are required:
</para>
<procedure>
......@@ -3407,9 +3407,9 @@ Start up a new 1.02.1 postmaster
Add the new built-in functions and operators of 1.02.1 to 1.01 or 1.02
databases. This is done by running the new 1.02.1 server against
your own 1.01 or 1.02 database and applying the queries attached at
the end of thie file. This can be done easily through psql. If your
1.01 or 1.02 database is named "testdb" and you have cut the commands
from the end of this file and saved them in addfunc.sql:
the end of the file. This can be done easily through <command>psql</>. If your
1.01 or 1.02 database is named <literal>testdb</literal> and you have cut the commands
from the end of this file and saved them in <filename>addfunc.sql</filename>:
<programlisting>
% psql testdb -f addfunc.sql
</programlisting>
......@@ -3426,9 +3426,9 @@ not a cause for concern.
<title>Dump/Reload Procedure</title>
<para>
If you are trying to reload a pg_dump or text-mode 'copy tablename to
stdout' generated with a previous version, you will need to run the
attached sed script on the ASCII file before loading it into the
If you are trying to reload a pg_dump or text-mode, <literal>copy tablename to
stdout</literal> generated with a previous version, you will need to run the
attached <command>sed</command> script on the ASCII file before loading it into the
database. The old format used '.' as end-of-data, while '\.' is now the
end-of-data marker. Also, empty strings are now loaded in as '' rather
than NULL. See the copy manual page for full details.
......@@ -3539,21 +3539,21 @@ Contributors (appologies to any missed)
<para>
The following notes are for the benefit of users who want to migrate
databases from postgres95 1.0 to postgres95 1.01.
databases from <productname>Postgres95</> 1.0 to <productname>Postgres95</> 1.01.
</para>
<para>
If you are starting afresh with postgres95 1.01 and do not need
If you are starting afresh with <productname>Postgres95</> 1.01 and do not need
to migrate old databases, you do not need to read any further.
</para>
<para>
In order to postgres95 version 1.01 with databases created with
postgres95 version 1.0, the following steps are required:
In order to <productname>Postgres95</> version 1.01 with databases created with
<productname>Postgres95</> version 1.0, the following steps are required:
</para>
<procedure>
<step>
<para>
Set the definition of NAMEDATALEN in src/Makefile.global to 16
and OIDNAMELEN to 20.
Set the definition of <symbol>NAMEDATALEN</symbol> in <filename>src/Makefile.global</filename> to 16
and <symbol>OIDNAMELEN</symbol> to 20.
</para>
</step>
<step>
......@@ -3563,8 +3563,8 @@ Decide whether you want to use Host based authentication.
<substeps>
<step>
<para>
If you do, you must create a file name "pg_hba" in your top-level data
directory (typically the value of your $PGDATA). src/libpq/pg_hba
If you do, you must create a file name <literal>pg_hba</literal> in your top-level data
directory (typically the value of your <envar>$PGDATA</envar>). <filename>src/libpq/pg_hba</filename>
shows an example syntax.
</para>
</step>
......@@ -3575,7 +3575,7 @@ If you do not want host-based authentication, you can comment out
<programlisting>
HBA = 1
</programlisting>
in src/Makefile.global
in <filename>src/Makefile.global</filename>
</para>
<para>
Note that host-based authentication is turned on by default, and if
......@@ -3588,24 +3588,24 @@ If you do not want host-based authentication, you can comment out
<step>
<para>
Compile and install 1.01, but DO NOT do the initdb step.
Compile and install 1.01, but DO NOT do the <command>initdb</command> step.
</para>
</step>
<step>
<para>
Before doing anything else, terminate your 1.0 postmaster, and
backup your existing $PGDATA directory.
backup your existing <envar>$PGDATA</envar> directory.
</para>
</step>
<step>
<para>
Set your PGDATA environment variable to your 1.0 databases, but set up
Set your <envar>PGDATA</envar> environment variable to your 1.0 databases, but set up
path up so that 1.01 binaries are being used.
</para>
</step>
<step>
<para>
Modify the file $PGDATA/PG_VERSION from 5.0 to 5.1
Modify the file <filename><envar>$PGDATA</envar>/PG_VERSION</filename> from 5.0 to 5.1
</para>
</step>
<step>
......@@ -3618,8 +3618,8 @@ Start up a new 1.01 postmaster
Add the new built-in functions and operators of 1.01 to 1.0
databases. This is done by running the new 1.01 server against
your own 1.0 database and applying the queries attached and saving
in the file 1.0_to_1.01.sql. This can be done easily through psql.
If your 1.0 database is name "testdb":
in the file 1.0_to_1.01.sql. This can be done easily through <command>psql</command>.
If your 1.0 database is name <literal>testdb</literal>:
<programlisting>
% psql testdb -f 1.0_to_1.01.sql
......@@ -4049,7 +4049,7 @@ Initial release.
04:21 Dual Pentium Pro 180, 224MB, UW-SCSI, Linux 2.0.36, gcc 2.7.2.3 -O2 -m486
</programlisting>
For the linux system above, using UW-SCSI disks rather than (older) IDE
For the <systemitem class="osname">Linux</systemitem> system above, using <acronym>UW-SCSI</acronym> disks rather than (older) <acronym>IDE</acronym>
disks leads to a 50% improvement in speed on the regression test.
</para>
</sect2>
......
doc/src/sgml/runtime.sgml
浏览文件 @ d07454f5
此差异已折叠。
doc/src/sgml/user-manag.sgml
浏览文件 @ d07454f5
......@@ -39,7 +39,7 @@ CREATE USER <replaceable>name</replaceable>
<command>initdb</command>) it will have the same name as the
operating system user that initialized the area (and is presumably
being used as the user that runs the server). Customarily, this user
will be called <quote>postgres</quote>. In order to create more
will be called <systemitem>postgres</systemitem>. In order to create more
users you have to first connect as this initial user.
</para>
......@@ -132,7 +132,7 @@ ALTER GROUP <replaceable>name</replaceable> DROP USER <replaceable>uname1</repla
<para>
When a database object is created, it is assigned an owner. The
owner is the user that executed the creation statement. There is
currenty no polished interface for changing the owner of a database
currently no polished interface for changing the owner of a database
object. By default, only an owner (or a superuser) can do anything
with the object. In order to allow other users to use it,
<firstterm>privileges</firstterm> must be granted.
......@@ -169,7 +169,7 @@ GRANT SELECT ON accounts TO GROUP staff;
REVOKE ALL ON accounts FROM PUBLIC;
</programlisting>
The set of privileges held by the table owner is always implicit
and is never revokable.
and cannot be revoked.
</para>
</sect1>
......@@ -179,7 +179,7 @@ REVOKE ALL ON accounts FROM PUBLIC;
<para>
Functions and triggers allow users to insert code into the backend
server that other users may execute without knowing it. Hence, both
mechanisms permit users to <firstterm>trojan horse</firstterm>
mechanisms permit users to <firstterm>Trojan horse</firstterm>
others with relative impunity. The only real protection is tight
control over who can define functions (e.g., write to relations
with SQL fields) and triggers. Audit trails and alerters on the
......
doc/src/sgml/wal.sgml
浏览文件 @ d07454f5
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.8 2001/08/25 18:52:41 tgl Exp $ -->
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.9 2001/09/09 23:52:12 petere Exp $ -->
<chapter id="wal">
<title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
......@@ -38,7 +38,7 @@
The first obvious benefit of using <acronym>WAL</acronym> is a
significantly reduced number of disk writes, since only the log
file needs to be flushed to disk at the time of transaction
commit; in multi-user environments, commits of many transactions
commit; in multiuser environments, commits of many transactions
may be accomplished with a single <function>fsync()</function> of
the log file. Furthermore, the log file is written sequentially,
and so the cost of syncing the log is much less than the cost of
......@@ -287,7 +287,7 @@
record to the log with <function>LogInsert</function> but before
performing a <function>LogFlush</function>. This delay allows other
backends to add their commit records to the log so as to have all
of them flushed with a single log sync. No sleep will occur if fsync
of them flushed with a single log sync. No sleep will occur if <varname>fsync</varname>
is not enabled or if fewer than <varname>COMMIT_SIBLINGS</varname>
other backends are not currently in active transactions; this avoids
sleeping when it's unlikely that any other backend will commit soon.
......
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或