mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-03-01 19:45:33 +08:00
Remove tabs from SGML files to help tag alingment and improve
detection of tabs are added in the future.
This commit is contained in:
Bruce Momjian
parent
7ea758b0b1
commit
4ab7ea5ace
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/docguide.sgml,v 1.70 2007/02/01 00:28:16 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/docguide.sgml,v 1.71 2007/02/16 03:50:28 momjian Exp $ -->
|
||||
|
||||
<appendix id="docguide">
|
||||
<title>Documentation</title>
|
||||
@ -227,7 +227,7 @@
|
||||
<para>
|
||||
It's possible that the ports do not update the main catalog file
|
||||
in <filename>/usr/local/share/sgml/catalog.ports</filename> or order
|
||||
isn't proper . Be sure to have the following lines in begining of file:
|
||||
isn't proper . Be sure to have the following lines in begining of file:
|
||||
<programlisting>
|
||||
CATALOG "openjade/catalog"
|
||||
CATALOG "iso8879/catalog"
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.359 2007/02/16 03:39:44 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.360 2007/02/16 03:50:29 momjian Exp $ -->
|
||||
|
||||
<chapter id="functions">
|
||||
<title>Functions and Operators</title>
|
||||
@ -4804,15 +4804,15 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
|
||||
An ISO week date (as distinct from a Gregorian date) can be specified to <function>to_timestamp</function> and <function>to_date</function> in one of two ways:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Year, week and weekday, for example <literal>to_date('2006-42-4', 'IYYY-IW-ID')</literal> returns the date <literal>2006-10-19</literal>. If you omit the weekday it is assumed to be 1 (Monday).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Year and day of year, for example <literal>to_date('2006-291', 'IYYY-IDDD')</literal> also returns <literal>2006-10-19</literal>.
|
||||
</para>
|
||||
</listitem>
|
||||
<para>
|
||||
Year, week and weekday, for example <literal>to_date('2006-42-4', 'IYYY-IW-ID')</literal> returns the date <literal>2006-10-19</literal>. If you omit the weekday it is assumed to be 1 (Monday).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Year and day of year, for example <literal>to_date('2006-291', 'IYYY-IDDD')</literal> also returns <literal>2006-10-19</literal>.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/geqo.sgml,v 1.38 2006/09/16 00:30:14 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/geqo.sgml,v 1.39 2007/02/16 03:50:29 momjian Exp $ -->
|
||||
|
||||
<chapter id="geqo">
|
||||
<chapterinfo>
|
||||
@ -50,7 +50,7 @@
|
||||
<productname>PostgreSQL</productname>) to process individual joins
|
||||
and a diversity of <firstterm>indexes</firstterm> (e.g.,
|
||||
B-tree, hash, GiST and GIN in <productname>PostgreSQL</productname>) as
|
||||
access paths for relations.
|
||||
access paths for relations.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/gin.sgml,v 2.10 2007/02/01 19:10:24 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/gin.sgml,v 2.11 2007/02/16 03:50:29 momjian Exp $ -->
|
||||
|
||||
<chapter id="GIN">
|
||||
<title>GIN Indexes</title>
|
||||
@ -100,12 +100,12 @@
|
||||
to consult <literal>n</> to determine the data type of
|
||||
<literal>query</> and the key values that need to be extracted.
|
||||
The number of returned keys must be stored into <literal>*nkeys</>.
|
||||
If number of keys is equal to zero then <function>extractQuery</>
|
||||
should store 0 or -1 into <literal>*nkeys</>. 0 means that any
|
||||
row matches the <literal>query</> and sequence scan should be
|
||||
produced. -1 means nothing can satisfy <literal>query</>.
|
||||
Choice of value should be based on semantics meaning of operation with
|
||||
given strategy number.
|
||||
If number of keys is equal to zero then <function>extractQuery</>
|
||||
should store 0 or -1 into <literal>*nkeys</>. 0 means that any
|
||||
row matches the <literal>query</> and sequence scan should be
|
||||
produced. -1 means nothing can satisfy <literal>query</>.
|
||||
Choice of value should be based on semantics meaning of operation with
|
||||
given strategy number.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.229 2007/02/16 02:59:40 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.230 2007/02/16 03:50:29 momjian Exp $ -->
|
||||
|
||||
<chapter id="libpq">
|
||||
<title><application>libpq</application> - C Library</title>
|
||||
@ -334,9 +334,9 @@ PGconn *PQsetdbLogin(const char *pghost,
|
||||
</para>
|
||||
<para>
|
||||
If the <parameter>dbName</parameter> contains an <symbol>=</symbol> sign, it
|
||||
is taken as a <parameter>conninfo</parameter> string in exactly the same way as
|
||||
if it had been passed to <function>PQconnectdb</function>, and the remaining
|
||||
parameters are then applied as above.
|
||||
is taken as a <parameter>conninfo</parameter> string in exactly the same way as
|
||||
if it had been passed to <function>PQconnectdb</function>, and the remaining
|
||||
parameters are then applied as above.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@ -4486,8 +4486,8 @@ ldap://ldap.mycompany.com/dc=mycompany,dc=com?uniqueMember?one?(cn=mydatabase)
|
||||
do not reveal secret keys to the application. Instead, applications
|
||||
delegate all cryptography operations which require the secret key to
|
||||
the hardware token.
|
||||
</para>
|
||||
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If the file <filename>~/.postgresql/root.crt</> is present in the user's
|
||||
home directory,
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.67 2007/02/08 15:32:11 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.68 2007/02/16 03:50:29 momjian Exp $ -->
|
||||
|
||||
<chapter id="mvcc">
|
||||
<title>Concurrency Control</title>
|
||||
@ -754,7 +754,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<colspec colnum="8" colwidth="1*">
|
||||
<colspec colnum="9" colwidth="1*">
|
||||
<thead>
|
||||
<row>
|
||||
<row>
|
||||
<entry>Modes</entry>
|
||||
<entry>AS</entry>
|
||||
<entry>RS</entry>
|
||||
@ -764,10 +764,10 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<entry>SRE</entry>
|
||||
<entry>E</entry>
|
||||
<entry>AE</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>AS</entry>
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">Y</entry>
|
||||
@ -777,8 +777,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">N</entry>
|
||||
</row>
|
||||
<row>
|
||||
</row>
|
||||
<row>
|
||||
<entry>RS</entry>
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">Y</entry>
|
||||
@ -788,8 +788,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
</row>
|
||||
<row>
|
||||
</row>
|
||||
<row>
|
||||
<entry>RE</entry>
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">Y</entry>
|
||||
@ -799,8 +799,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
</row>
|
||||
<row>
|
||||
</row>
|
||||
<row>
|
||||
<entry>SUE</entry>
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">Y</entry>
|
||||
@ -810,8 +810,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
</row>
|
||||
<row>
|
||||
</row>
|
||||
<row>
|
||||
<entry>S</entry>
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">Y</entry>
|
||||
@ -821,8 +821,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
</row>
|
||||
<row>
|
||||
</row>
|
||||
<row>
|
||||
<entry>SRE</entry>
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">Y</entry>
|
||||
@ -832,8 +832,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
</row>
|
||||
<row>
|
||||
</row>
|
||||
<row>
|
||||
<entry>E</entry>
|
||||
<entry align="center">Y</entry>
|
||||
<entry align="center">N</entry>
|
||||
@ -843,8 +843,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
</row>
|
||||
<row>
|
||||
</row>
|
||||
<row>
|
||||
<entry>AE</entry>
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
@ -854,10 +854,10 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
<entry align="center">N</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="locking-rows">
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.63 2007/02/01 19:10:24 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.64 2007/02/16 03:50:29 momjian Exp $ -->
|
||||
|
||||
<chapter id="plperl">
|
||||
<title>PL/Perl - Perl Procedural Language</title>
|
||||
@ -649,19 +649,19 @@ $$ LANGUAGE plperl;
|
||||
|
||||
<note>
|
||||
<para>
|
||||
For security reasons, to stop a leak of privileged operations from
|
||||
For security reasons, to stop a leak of privileged operations from
|
||||
<application>PL/PerlU</> to <application>PL/Perl</>, these two languages
|
||||
have to run in separate instances of the Perl interpreter. If your
|
||||
Perl installation has been appropriately compiled, this is not a problem.
|
||||
However, not all installations are compiled with the requisite flags.
|
||||
If <productname>PostgreSQL</> detects that this is the case then it will
|
||||
not start a second interpreter, but instead create an error. In
|
||||
consequence, in such an installation, you cannot use both
|
||||
<application>PL/PerlU</> and <application>PL/Perl</> in the same backend
|
||||
process. The remedy for this is to obtain a Perl installation created
|
||||
with the appropriate flags, namely either <literal>usemultiplicity</> or
|
||||
both <literal>usethreads</> and <literal>useithreads</>.
|
||||
For more details,see the <literal>perlembed</> manual page.
|
||||
have to run in separate instances of the Perl interpreter. If your
|
||||
Perl installation has been appropriately compiled, this is not a problem.
|
||||
However, not all installations are compiled with the requisite flags.
|
||||
If <productname>PostgreSQL</> detects that this is the case then it will
|
||||
not start a second interpreter, but instead create an error. In
|
||||
consequence, in such an installation, you cannot use both
|
||||
<application>PL/PerlU</> and <application>PL/Perl</> in the same backend
|
||||
process. The remedy for this is to obtain a Perl installation created
|
||||
with the appropriate flags, namely either <literal>usemultiplicity</> or
|
||||
both <literal>usethreads</> and <literal>useithreads</>.
|
||||
For more details,see the <literal>perlembed</> manual page.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue
Block a user