[Trad] [svn:pgfr] r1297 - in traduc/trunk/postgresql: . ref
admin at listes.postgresql.fr
admin at listes.postgresql.fr
Jeu 16 Avr 18:18:35 CEST 2009
Author: gleu
Date: 2009-04-16 18:18:33 +0200 (Thu, 16 Apr 2009)
New Revision: 1297
Modified:
traduc/trunk/postgresql/advanced.xml
traduc/trunk/postgresql/array.xml
traduc/trunk/postgresql/auto-explain.xml
traduc/trunk/postgresql/backup.xml
traduc/trunk/postgresql/btree-gin.xml
traduc/trunk/postgresql/catalogs.xml
traduc/trunk/postgresql/charset.xml
traduc/trunk/postgresql/citext.xml
traduc/trunk/postgresql/client-auth.xml
traduc/trunk/postgresql/config.xml
traduc/trunk/postgresql/datatype.xml
traduc/trunk/postgresql/dblink.xml
traduc/trunk/postgresql/ddl.xml
traduc/trunk/postgresql/errcodes.xml
traduc/trunk/postgresql/extend.xml
traduc/trunk/postgresql/filelist.xml
traduc/trunk/postgresql/func.xml
traduc/trunk/postgresql/fuzzystrmatch.xml
traduc/trunk/postgresql/gin.xml
traduc/trunk/postgresql/gist.xml
traduc/trunk/postgresql/indexam.xml
traduc/trunk/postgresql/indices.xml
traduc/trunk/postgresql/install-win32.xml
traduc/trunk/postgresql/installation.xml
traduc/trunk/postgresql/intagg.xml
traduc/trunk/postgresql/intarray.xml
traduc/trunk/postgresql/libpq.xml
traduc/trunk/postgresql/lobj.xml
traduc/trunk/postgresql/maintenance.xml
traduc/trunk/postgresql/monitoring.xml
traduc/trunk/postgresql/mvcc.xml
traduc/trunk/postgresql/pageinspect.xml
traduc/trunk/postgresql/pgbench.xml
traduc/trunk/postgresql/pgfreespacemap.xml
traduc/trunk/postgresql/pgstandby.xml
traduc/trunk/postgresql/pgstatstatements.xml
traduc/trunk/postgresql/plperl.xml
traduc/trunk/postgresql/plpgsql.xml
traduc/trunk/postgresql/plpython.xml
traduc/trunk/postgresql/pltcl.xml
traduc/trunk/postgresql/queries.xml
traduc/trunk/postgresql/ref/allfiles.xml
traduc/trunk/postgresql/ref/alter_database.xml
traduc/trunk/postgresql/ref/alter_domain.xml
traduc/trunk/postgresql/ref/alter_foreign_data_wrapper.xml
traduc/trunk/postgresql/ref/alter_function.xml
traduc/trunk/postgresql/ref/alter_opfamily.xml
traduc/trunk/postgresql/ref/alter_role.xml
traduc/trunk/postgresql/ref/alter_sequence.xml
traduc/trunk/postgresql/ref/alter_server.xml
traduc/trunk/postgresql/ref/alter_table.xml
traduc/trunk/postgresql/ref/alter_user_mapping.xml
traduc/trunk/postgresql/ref/alter_view.xml
traduc/trunk/postgresql/ref/clusterdb.xml
traduc/trunk/postgresql/ref/copy.xml
traduc/trunk/postgresql/ref/create_cast.xml
traduc/trunk/postgresql/ref/create_database.xml
traduc/trunk/postgresql/ref/create_domain.xml
traduc/trunk/postgresql/ref/create_foreign_data_wrapper.xml
traduc/trunk/postgresql/ref/create_function.xml
traduc/trunk/postgresql/ref/create_index.xml
traduc/trunk/postgresql/ref/create_opclass.xml
traduc/trunk/postgresql/ref/create_server.xml
traduc/trunk/postgresql/ref/create_table.xml
traduc/trunk/postgresql/ref/create_table_as.xml
traduc/trunk/postgresql/ref/create_trigger.xml
traduc/trunk/postgresql/ref/create_type.xml
traduc/trunk/postgresql/ref/create_user_mapping.xml
traduc/trunk/postgresql/ref/createdb.xml
traduc/trunk/postgresql/ref/createlang.xml
traduc/trunk/postgresql/ref/createuser.xml
traduc/trunk/postgresql/ref/declare.xml
traduc/trunk/postgresql/ref/delete.xml
traduc/trunk/postgresql/ref/drop_foreign_data_wrapper.xml
traduc/trunk/postgresql/ref/drop_function.xml
traduc/trunk/postgresql/ref/drop_server.xml
traduc/trunk/postgresql/ref/drop_user_mapping.xml
traduc/trunk/postgresql/ref/dropdb.xml
traduc/trunk/postgresql/ref/droplang.xml
traduc/trunk/postgresql/ref/dropuser.xml
traduc/trunk/postgresql/ref/grant.xml
traduc/trunk/postgresql/ref/initdb.xml
traduc/trunk/postgresql/ref/insert.xml
traduc/trunk/postgresql/ref/lock.xml
traduc/trunk/postgresql/ref/pg_config-ref.xml
traduc/trunk/postgresql/ref/pg_dump.xml
traduc/trunk/postgresql/ref/pg_dumpall.xml
traduc/trunk/postgresql/ref/pg_restore.xml
traduc/trunk/postgresql/ref/prepare.xml
traduc/trunk/postgresql/ref/psql-ref.xml
traduc/trunk/postgresql/ref/reindexdb.xml
traduc/trunk/postgresql/ref/revoke.xml
traduc/trunk/postgresql/ref/select.xml
traduc/trunk/postgresql/ref/set.xml
traduc/trunk/postgresql/ref/set_role.xml
traduc/trunk/postgresql/ref/truncate.xml
traduc/trunk/postgresql/ref/update.xml
traduc/trunk/postgresql/ref/vacuum.xml
traduc/trunk/postgresql/ref/vacuumdb.xml
traduc/trunk/postgresql/ref/values.xml
traduc/trunk/postgresql/release.xml
traduc/trunk/postgresql/runtime.xml
traduc/trunk/postgresql/sources.xml
traduc/trunk/postgresql/spi.xml
traduc/trunk/postgresql/storage.xml
traduc/trunk/postgresql/syntax.xml
traduc/trunk/postgresql/textsearch.xml
traduc/trunk/postgresql/trigger.xml
traduc/trunk/postgresql/typeconv.xml
traduc/trunk/postgresql/vacuumlo.xml
traduc/trunk/postgresql/wal.xml
traduc/trunk/postgresql/xaggr.xml
traduc/trunk/postgresql/xfunc.xml
traduc/trunk/postgresql/xindex.xml
Log:
Correction des balises pour permettre la g?\195?\169n?\195?\169ration du manuel de la 8.4 beta.
Modified: traduc/trunk/postgresql/advanced.xml
===================================================================
--- traduc/trunk/postgresql/advanced.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/advanced.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -361,7 +361,7 @@
</indexterm>
<para>
- A <firstterm>window function</> performs a calculation across a set of
+ A <firstterm>window function</firstterm> performs a calculation across a set of
table rows that are somehow related to the current row. This is comparable
to the type of calculation that can be done with an aggregate function.
But unlike regular aggregate functions, use of a window function does not
@@ -396,33 +396,33 @@
</screen>
The first three output columns come directly from the table
- <structname>empsalary</>, and there is one output row for each row in the
+ <structname>empsalary</structname>, and there is one output row for each row in the
table. The fourth column represents an average taken across all the table
- rows that have the same <structfield>depname</> value as the current row.
- (This actually is the same function as the regular <function>avg</>
- aggregate function, but the <literal>OVER</> clause causes it to be
+ rows that have the same <structfield>depname</structfield> value as the current row.
+ (This actually is the same function as the regular <function>avg</function>
+ aggregate function, but the <literal>OVER</literal> clause causes it to be
treated as a window function and computed across an appropriate set of
rows.)
</para>
<para>
- A window function call always contains an <literal>OVER</> clause
+ A window function call always contains an <literal>OVER</literal> clause
following the window function's name and argument(s). This is what
syntactically distinguishes it from a regular function or aggregate
- function. The <literal>OVER</> clause determines exactly how the
+ function. The <literal>OVER</literal> clause determines exactly how the
rows of the query are split up for processing by the window function.
- The <literal>PARTITION BY</> list within <literal>OVER</> specifies
+ The <literal>PARTITION BY</literal> list within <literal>OVER</literal> specifies
dividing the rows into groups, or partitions, that share the same
- values of the <literal>PARTITION BY</> expression(s). For each row,
+ values of the <literal>PARTITION BY</literal> expression(s). For each row,
the window function is computed across the rows that fall into the
same partition as the current row.
</para>
<para>
- Although <function>avg</> will produce the same result no matter
+ Although <function>avg</function> will produce the same result no matter
what order it processes the partition's rows in, this is not true of all
window functions. When needed, you can control that order using
- <literal>ORDER BY</> within <literal>OVER</>. Here is an example:
+ <literal>ORDER BY</literal> within <literal>OVER</literal>. Here is an example:
<programlisting>
SELECT depname, empno, salary, rank() OVER (PARTITION BY depname ORDER BY salary DESC) FROM empsalary;
@@ -444,48 +444,50 @@
(10 rows)
</screen>
- As shown here, the <function>rank</> function produces a numerical rank
- within the current row's partition for each distinct <literal>ORDER BY</>
- value, in the order defined by the <literal>ORDER BY</> clause.
- <function>rank</> needs no explicit parameter, because its behavior
- is entirely determined by the <literal>OVER</> clause.
+ As shown here, the <function>rank</function> function produces a numerical rank
+ within the current row's partition for each distinct <literal>ORDER
+ BY</literal>
+ value, in the order defined by the <literal>ORDER BY</literal> clause.
+ <function>rank</function> needs no explicit parameter, because its behavior
+ is entirely determined by the <literal>OVER</literal> clause.
</para>
<para>
The rows considered by a window function are those of the <quote>virtual
- table</> produced by the query's <literal>FROM</> clause as filtered by its
- <literal>WHERE</>, <literal>GROUP BY</>, and <literal>HAVING</> clauses
+ table</quote> produced by the query's <literal>FROM</literal> clause as filtered by its
+ <literal>WHERE</literal>, <literal>GROUP BY</literal>, and
+ <literal>HAVING</literal> clauses
if any. For example, a row removed because it does not meet the
- <literal>WHERE</> condition is not seen by any window function.
+ <literal>WHERE</literal> condition is not seen by any window function.
A query can contain multiple window functions that slice up the data
- in different ways by means of different <literal>OVER</> clauses, but
+ in different ways by means of different <literal>OVER</literal> clauses, but
they all act on the same collection of rows defined by this virtual table.
</para>
<para>
- We already saw that <literal>ORDER BY</> can be omitted if the ordering
+ We already saw that <literal>ORDER BY</literal> can be omitted if the ordering
of rows is not important. It is also possible to omit <literal>PARTITION
- BY</>, in which case there is just one partition containing all the rows.
+ BY</literal>, in which case there is just one partition containing all the rows.
</para>
<para>
There is another important concept associated with window functions:
for each row, there is a set of rows within its partition called its
- <firstterm>window frame</>. Many (but not all) window functions act only
+ <firstterm>window frame</firstterm>. Many (but not all) window functions act only
on the rows of the window frame, rather than of the whole partition.
- By default, if <literal>ORDER BY</> is supplied then the frame consists of
+ By default, if <literal>ORDER BY</literal> is supplied then the frame consists of
all rows from the start of the partition up through the current row, plus
any following rows that are equal to the current row according to the
- <literal>ORDER BY</> clause. When <literal>ORDER BY</> is omitted the
+ <literal>ORDER BY</literal> clause. When <literal>ORDER BY</literal> is omitted the
default frame consists of all rows in the partition.
<footnote>
<para>
There are options to define the window frame in other ways, but
this tutorial does not cover them. See
- <xref linkend="syntax-window-functions"> for details.
+ <xref linkend="syntax-window-functions"/> for details.
</para>
</footnote>
- Here is an example using <function>sum</>:
+ Here is an example using <function>sum</function>:
</para>
<programlisting>
@@ -509,11 +511,12 @@
</screen>
<para>
- Above, since there is no <literal>ORDER BY</> in the <literal>OVER</>
+ Above, since there is no <literal>ORDER BY</literal> in the
+ <literal>OVER</literal>
clause, the window frame is the same as the partition, which for lack of
- <literal>PARTITION BY</> is the whole table; in other words each sum is
+ <literal>PARTITION BY</literal> is the whole table; in other words each sum is
taken over the whole table and so we get the same result for each output
- row. But if we add an <literal>ORDER BY</> clause, we get very different
+ row. But if we add an <literal>ORDER BY</literal> clause, we get very different
results:
</para>
@@ -545,8 +548,9 @@
<para>
Window functions are permitted only in the <literal>SELECT</literal> list
- and the <literal>ORDER BY</> clause of the query. They are forbidden
- elsewhere, such as in <literal>GROUP BY</>, <literal>HAVING</>
+ and the <literal>ORDER BY</literal> clause of the query. They are forbidden
+ elsewhere, such as in <literal>GROUP BY</literal>,
+<literal>HAVING</literal>
and <literal>WHERE</literal> clauses. This is because they logically
execute after the processing of those clauses. Also, window functions
execute after regular aggregate functions. This means it is valid to
@@ -569,15 +573,16 @@
</programlisting>
The above query only shows the rows from the inner query having
- <literal>rank</> less than <literal>3</>.
+ <literal>rank</literal> less than <literal>3</literal>.
</para>
<para>
When a query involves multiple window functions, it is possible to write
- out each one with a separate <literal>OVER</> clause, but this is
+ out each one with a separate <literal>OVER</literal> clause, but this is
duplicative and error-prone if the same windowing behavior is wanted
for several functions. Instead, each windowing behavior can be named
- in a <literal>WINDOW</> clause and then referenced in <literal>OVER</>.
+ in a <literal>WINDOW</literal> clause and then referenced in
+ <literal>OVER</literal>.
For example:
<programlisting>
@@ -589,9 +594,9 @@
<para>
More details about window functions can be found in
- <xref linkend="syntax-window-functions">,
- <xref linkend="queries-window">, and the
- <xref linkend="sql-select" endterm="sql-select-title"> reference page.
+ <xref linkend="syntax-window-functions"/>,
+ <xref linkend="queries-window"/>, and the
+ <xref linkend="sql-select" endterm="sql-select-title"/> reference page.
</para>
</sect1>
Modified: traduc/trunk/postgresql/array.xml
===================================================================
--- traduc/trunk/postgresql/array.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/array.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -266,7 +266,8 @@
(1 row)</programlisting>
To avoid confusion with the non-slice case, it's best to use slice syntax
- for all dimensions, e.g., <literal>[1:2][1:1]</>, not <literal>[2][1:1]</>.
+ for all dimensions, e.g., <literal>[1:2][1:1]</literal>, not
+ <literal>[2][1:1]</literal>.
</para>
<para>
@@ -530,7 +531,7 @@
</para>
<para>
- Alternatively, the <function>generate_subscripts</> function can be used.
+ Alternatively, the <function>generate_subscripts</function> function can be used.
For example:
<programlisting>
@@ -541,7 +542,7 @@
WHERE pay_by_quarter[s] = 10000;
</programlisting>
- This function is described in <xref linkend="functions-srf-subscripts">.
+ This function is described in <xref linkend="functions-srf-subscripts"/>.
</para>
<tip>
Modified: traduc/trunk/postgresql/auto-explain.xml
===================================================================
--- traduc/trunk/postgresql/auto-explain.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/auto-explain.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -10,7 +10,7 @@
<para>
The <filename>auto_explain</filename> module provides a means for
logging execution plans of slow statements automatically, without
- having to run <xref linkend="sql-explain" endterm="sql-explain-title">
+ having to run <xref linkend="sql-explain" endterm="sql-explain-title"/>
by hand. This is especially helpful for tracking down un-optimized queries
in large applications.
</para>
@@ -24,9 +24,9 @@
</programlisting>
(You must be superuser to do that.) More typical usage is to preload
- it into all sessions by including <literal>auto_explain</> in
- <xref linkend="guc-shared-preload-libraries"> in
- <filename>postgresql.conf</>. Then you can track unexpectedly slow queries
+ it into all sessions by including <literal>auto_explain</literal> in
+ <xref linkend="guc-shared-preload-libraries"/> in
+ <filename>postgresql.conf</filename>. Then you can track unexpectedly slow queries
no matter when they happen. Of course there is a price in overhead for
that.
</para>
@@ -47,7 +47,7 @@
<varname>auto_explain.log_min_duration</varname> (<type>integer</type>)
</term>
<indexterm>
- <primary><varname>auto_explain.log_min_duration</> configuration parameter</primary>
+ <primary><varname>auto_explain.log_min_duration</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -66,12 +66,13 @@
<varname>auto_explain.log_analyze</varname> (<type>boolean</type>)
</term>
<indexterm>
- <primary><varname>auto_explain.log_analyze</> configuration parameter</primary>
+ <primary><varname>auto_explain.log_analyze</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
- <varname>auto_explain.log_analyze</varname> causes <command>EXPLAIN ANALYZE</>
- output, rather than just <command>EXPLAIN</> output, to be printed
+ <varname>auto_explain.log_analyze</varname> causes <command>EXPLAIN
+ ANALYZE</command>
+ output, rather than just <command>EXPLAIN</command> output, to be printed
when an execution plan is logged. This parameter is off by default.
Only superusers can change this setting.
</para>
@@ -90,12 +91,13 @@
<varname>auto_explain.log_verbose</varname> (<type>boolean</type>)
</term>
<indexterm>
- <primary><varname>auto_explain.log_verbose</> configuration parameter</primary>
+ <primary><varname>auto_explain.log_verbose</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
- <varname>auto_explain.log_verbose</varname> causes <command>EXPLAIN VERBOSE</>
- output, rather than just <command>EXPLAIN</> output, to be printed
+ <varname>auto_explain.log_verbose</varname> causes <command>EXPLAIN
+ VERBOSE</command>
+ output, rather than just <command>EXPLAIN</command> output, to be printed
when an execution plan is logged. This parameter is off by default.
Only superusers can change this setting.
</para>
@@ -107,7 +109,7 @@
<varname>auto_explain.log_nested_statements</varname> (<type>boolean</type>)
</term>
<indexterm>
- <primary><varname>auto_explain.log_nested_statements</> configuration parameter</primary>
+ <primary><varname>auto_explain.log_nested_statements</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -121,9 +123,10 @@
</variablelist>
<para>
- In order to set these parameters in your <filename>postgresql.conf</> file,
- you will need to add <literal>auto_explain</> to
- <xref linkend="guc-custom-variable-classes">. Typical usage might be:
+ In order to set these parameters in your
+ <filename>postgresql.conf</filename> file,
+ you will need to add <literal>auto_explain</literal> to
+ <xref linkend="guc-custom-variable-classes"/>. Typical usage might be:
</para>
<programlisting>
Modified: traduc/trunk/postgresql/backup.xml
===================================================================
--- traduc/trunk/postgresql/backup.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/backup.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -411,10 +411,10 @@
If simultaneous snapshots are not possible, one option is to shut down
the database server long enough to establish all the frozen snapshots.
Another option is perform a continuous archiving base backup (<xref
- linkend="backup-base-backup">) because such backups are immune to file
+ linkend="backup-base-backup"/>) because such backups are immune to file
system changes during the backup. This requires enabling continuous
archiving just during the backup process; restore is done using
- continuous archive recovery (<xref linkend="backup-pitr-recovery">).
+ continuous archive recovery (<xref linkend="backup-pitr-recovery"/>).
</para>
<para>
@@ -812,17 +812,17 @@
sont archivés, c'est terminé. Le fichier identifié par le résultat de
<function>pg_stop_backup</function> est le dernier segment that is required
to form a complete set of backup files.
- <function>pg_stop_backup</> does not return until the last segment has
+ <function>pg_stop_backup</function> does not return until the last segment has
been archived.
Archiving of these files happens automatically since you have
- already configured <varname>archive_command</>. In most cases this
+ already configured <varname>archive_command</varname>. In most cases this
happens quickly, but you are advised to monitor your archive
system to ensure there are no delays.
If the archive process has fallen behind
because of failures of the archive command, it will keep retrying
until the archive succeeds and the backup is complete.
If you wish to place a time limit on the execution of
- <function>pg_stop_backup</>, set an appropriate
+ <function>pg_stop_backup</function>, set an appropriate
<varname>statement_timeout</varname> value.
</para>
</listitem>
@@ -1083,7 +1083,7 @@
renvoyer autre chose que zéro dans ce cas. Ce n'est pas une condition
d'erreur. Not all of the requested files will be WAL segment
files; you should also expect requests for files with a suffix of
- <literal>.backup</> or <literal>.history</>. Il faut également
+ <literal>.backup</literal> or <literal>.history</literal>. Il faut également
garder à l'esprit que le nom de base du chemin <literal>%p</literal>
diffère de <literal>%f</literal> ; il ne sont pas interchangeables.
</para>
@@ -1415,17 +1415,18 @@
</para>
<para>
- If archive storage size is a concern, use <application>pg_compresslog</>,
+ If archive storage size is a concern, use
+ <application>pg_compresslog</application>,
<ulink url="http://pglesslog.projects.postgresql.org"></ulink>, to
- remove unnecessary <xref linkend="guc-full-page-writes"> and trailing
+ remove unnecessary <xref linkend="guc-full-page-writes"/> and trailing
space from the WAL files. You can then use
<application>gzip</application> to further compress the output of
- <application>pg_compresslog</>:
+ <application>pg_compresslog</application>:
<programlisting>
archive_command = 'pg_compresslog %p - | gzip > /var/lib/pgsql/archive/%f'
</programlisting>
- You will then need to use <application>gunzip</> and
- <application>pg_decompresslog</> during recovery:
+ You will then need to use <application>gunzip</application> and
+ <application>pg_decompresslog</application> during recovery:
<programlisting>
restore_command = 'gunzip < /mnt/server/archivedir/%f | pg_decompresslog - %p'
</programlisting>
@@ -1745,8 +1746,8 @@
si le fichier est indisponible.
Dans le cas du serveur de secours, il est normal que le fichier suivant
n'existe pas. Il ne reste donc
- qu'à attendre son arrivée. For files ending in <literal>.backup</> or
- <literal>.history</> there is no need to wait, and a non-zero return
+ qu'à attendre son arrivée. For files ending in <literal>.backup</literal> or
+ <literal>.history</literal> there is no need to wait, and a non-zero return
code must be returned. Une <varname>restore_command</varname>
d'attente peut être obtenue par l'écriture d'un script personnalisé
qui boucle sur un test d'apparition du prochain fichier WAL. Il faut
@@ -2174,7 +2175,7 @@
In practice you probably want to test your client applications on the
new version before switching over completely. This is another reason
for setting up concurrent installations of old and new versions. When
- testing a <productname>PostgreSQL</> major upgrade, consider the
+ testing a <productname>PostgreSQL</productname> major upgrade, consider the
following categories of possible changes:
</para>
@@ -2204,7 +2205,7 @@
<term>Library API</term>
<listitem>
<para>
- Typically libraries like <application>libpq</> only add new
+ Typically libraries like <application>libpq</application> only add new
functionality, again unless mentioned in the release notes.
</para>
</listitem>
Modified: traduc/trunk/postgresql/btree-gin.xml
===================================================================
--- traduc/trunk/postgresql/btree-gin.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/btree-gin.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -8,15 +8,16 @@
</indexterm>
<para>
- <filename>btree_gin</> provides sample GIN operator classes that
+ <filename>btree_gin</filename> provides sample GIN operator classes that
implement B-Tree equivalent behavior for the data types
- <type>int2</>, <type>int4</>, <type>int8</>, <type>float4</>,
- <type>float8</>, <type>timestamp with time zone</>,
- <type>timestamp without time zone</>, <type>time with time zone</>,
- <type>time without time zone</>, <type>date</>, <type>interval</>,
- <type>oid</>, <type>money</>, <type>"char"</>,
- <type>varchar</>, <type>text</>, <type>bytea</>, <type>bit</>,
- <type>varbit</>, <type>macaddr</>, <type>inet</>, and <type>cidr</>.
+ <type>int2</type>, <type>int4</type>, <type>int8</type>, <type>float4</type>,
+ <type>float8</type>, <type>timestamp with time zone</type>,
+ <type>timestamp without time zone</type>, <type>time with time zone</type>,
+ <type>time without time zone</type>, <type>date</type>, <type>interval</type>,
+ <type>oid</type>, <type>money</type>, <type>"char"</type>,
+ <type>varchar</type>, <type>text</type>, <type>bytea</type>, <type>bit</type>,
+ <type>varbit</type>, <type>macaddr</type>, <type>inet</type>, and
+ <type>cidr</type>.
</para>
<para>
Modified: traduc/trunk/postgresql/catalogs.xml
===================================================================
--- traduc/trunk/postgresql/catalogs.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/catalogs.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1411,9 +1411,10 @@
<entry></entry>
<entry>
Indicates how the cast is performed.
- <literal>f</> means that the function specified in the <structfield>castfunc</> field is used.
- <literal>i</> means that the input/output functions are used.
- <literal>b</> means that the types are binary-coercible, thus no conversion is required
+ <literal>f</literal> means that the function specified in the
+ <structfield>castfunc</structfield> field is used.
+ <literal>i</literal> means that the input/output functions are used.
+ <literal>b</literal> means that the types are binary-coercible, thus no conversion is required
</entry>
</row>
</tbody>
@@ -1666,7 +1667,7 @@
<entry><type>int2</type></entry>
<entry></entry>
<entry>
- Nombre de contraintes de vérification (<literal>CHECK</>) sur la table ; voir le
+ Nombre de contraintes de vérification (<literal>CHECK</literal>) sur la table ; voir le
catalogue <link linkend="catalog-pg-constraint"><structname>pg_constraint</structname></link>.
</entry>
</row>
@@ -1870,11 +1871,11 @@
<entry><type>char</type></entry>
<entry></entry>
<entry>Code de l'action de mise à jour de la clé étrangère:
- <literal>a</> = no action,
- <literal>r</> = restrict,
- <literal>c</> = cascade,
- <literal>n</> = set null,
- <literal>d</> = set default
+ <literal>a</literal> = no action,
+ <literal>r</literal> = restrict,
+ <literal>c</literal> = cascade,
+ <literal>n</literal> = set null,
+ <literal>d</literal> = set default
</entry>
</row>
@@ -1883,11 +1884,11 @@
<entry><type>char</type></entry>
<entry></entry>
<entry>Code de l'action de suppression de clé étrangère:
- <literal>a</> = no action,
- <literal>r</> = restrict,
- <literal>c</> = cascade,
- <literal>n</> = set null,
- <literal>d</> = set default
+ <literal>a</literal> = no action,
+ <literal>r</literal> = restrict,
+ <literal>c</literal> = cascade,
+ <literal>n</literal> = set null,
+ <literal>d</literal> = set default
</entry>
</row>
@@ -1896,9 +1897,9 @@
<entry><type>char</type></entry>
<entry></entry>
<entry>Type de concordance de la clé étrangère:
- <literal>f</> = full,
- <literal>p</> = partial,
- <literal>u</> = simple (unspecified)
+ <literal>f</literal> = full,
+ <literal>p</literal> = partial,
+ <literal>u</literal> = simple (unspecified)
</entry>
</row>
@@ -2597,7 +2598,7 @@
</para>
<table>
- <title><structname>pg_foreign_data_wrapper</> Columns</title>
+ <title><structname>pg_foreign_data_wrapper</structname> Columns</title>
<tgroup cols="4">
<thead>
@@ -2643,8 +2644,8 @@
<entry></entry>
<entry>
Access privileges; see
- <xref linkend="sql-grant" endterm="sql-grant-title"> and
- <xref linkend="sql-revoke" endterm="sql-revoke-title">
+ <xref linkend="sql-grant" endterm="sql-grant-title"/> and
+ <xref linkend="sql-revoke" endterm="sql-revoke-title"/>
for details
</entry>
</row>
@@ -2654,7 +2655,7 @@
<entry><type>text[]</type></entry>
<entry></entry>
<entry>
- Foreign-data wrapper specific options, as <quote>keyword=value</> strings
+ Foreign-data wrapper specific options, as <quote>keyword=value</quote> strings
</entry>
</row>
</tbody>
@@ -2678,7 +2679,7 @@
</para>
<table>
- <title><structname>pg_foreign_server</> Columns</title>
+ <title><structname>pg_foreign_server</structname> Columns</title>
<tgroup cols="4">
<thead>
@@ -2732,8 +2733,8 @@
<entry></entry>
<entry>
Access privileges; see
- <xref linkend="sql-grant" endterm="sql-grant-title"> and
- <xref linkend="sql-revoke" endterm="sql-revoke-title">
+ <xref linkend="sql-grant" endterm="sql-grant-title"/> and
+ <xref linkend="sql-revoke" endterm="sql-revoke-title"/>
for details
</entry>
</row>
@@ -2743,7 +2744,7 @@
<entry><type>text[]</type></entry>
<entry></entry>
<entry>
- Foreign server specific options, as <quote>keyword=value</> strings.
+ Foreign server specific options, as <quote>keyword=value</quote> strings.
</entry>
</row>
</tbody>
@@ -3991,8 +3992,8 @@
<literal>i</literal> pour les arguments <literal>IN</literal>,
<literal>o</literal> pour les arguments <literal>OUT</literal>,
<literal>b</literal> pour les arguments <literal>INOUT</literal>,
- <literal>v</literal> for <literal>VARIADIC</> arguments,
- <literal>t</literal> for <literal>TABLE</>.
+ <literal>v</literal> for <literal>VARIADIC</literal> arguments,
+ <literal>t</literal> for <literal>TABLE</literal>.
Si tous les arguments sont des arguments <literal>IN</literal>, ce
champ est NULL.
Les indices correspondent aux positions de
@@ -4022,9 +4023,9 @@
<entry>
Expression trees (in <function>nodeToString()</function> representation)
for default values. This is a list with
- <structfield>pronargdefaults</> elements, corresponding to the last
- <replaceable>N</> <emphasis>input</> arguments (i.e., the last
- <replaceable>N</> <structfield>proargtypes</> positions).
+ <structfield>pronargdefaults</structfield> elements, corresponding to the last
+ <replaceable>N</replaceable> <emphasis>input</emphasis> arguments (i.e., the last
+ <replaceable>N</replaceable> <structfield>proargtypes</structfield> positions).
If none of the arguments have defaults, this field will be null
</entry>
</row>
@@ -4285,7 +4286,7 @@
<entry></entry>
<entry>
For a table column, this is the column number (the
- <structfield>objid</> and <structfield>classid</> refer to the
+ <structfield>objid</structfield> and <structfield>classid</structfield> refer to the
table itself). For all other object types, this column is zero
</entry>
</row>
@@ -5384,8 +5385,8 @@
<entry>
<structfield>typcategory</structfield> is an arbitrary classification
of data types that is used by the parser to determine which implicit
- casts should be <quote>preferred</>.
- See <xref linkend="catalog-typcategory-table">
+ casts should be <quote>preferred</quote>.
+ See <xref linkend="catalog-typcategory-table"/>
</entry>
</row>
@@ -5685,14 +5686,14 @@
</table>
<para>
- <xref linkend="catalog-typcategory-table"> lists the system-defined values
- of <structfield>typcategory</>. Any future additions to this list will
+ <xref linkend="catalog-typcategory-table"/> lists the system-defined values
+ of <structfield>typcategory</structfield>. Any future additions to this list will
also be upper-case ASCII letters. All other ASCII characters are reserved
for user-defined categories.
</para>
<table id="catalog-typcategory-table">
- <title><structfield>typcategory</> Codes</title>
+ <title><structfield>typcategory</structfield> Codes</title>
<tgroup cols="2">
<thead>
@@ -5757,7 +5758,7 @@
</row>
<row>
<entry><literal>X</literal></entry>
- <entry><type>unknown</> type</entry>
+ <entry><type>unknown</type> type</entry>
</row>
</tbody>
</tgroup>
@@ -5782,7 +5783,7 @@
</para>
<table>
- <title><structname>pg_user_mapping</> Columns</title>
+ <title><structname>pg_user_mapping</structname> Columns</title>
<tgroup cols="4">
<thead>
@@ -5816,7 +5817,7 @@
<entry><type>text[]</type></entry>
<entry></entry>
<entry>
- User mapping specific options, as <quote>keyword=value</> strings.
+ User mapping specific options, as <quote>keyword=value</quote> strings.
</entry>
</row>
</tbody>
@@ -6343,7 +6344,7 @@
L'OID de l'objet dans son catalogue système ou NULL si l'objet n'est
pas un objet général de la base de données
For advisory locks it is used to distinguish the two key
- spaces (<literal>1</> for an int8 key, <literal>2</> for two
+ spaces (<literal>1</literal> for an int8 key, <literal>2</literal> for two
int4 keys).
</entry>
</row>
@@ -6881,8 +6882,8 @@
<para>
La vue <structname>pg_settings</structname> fournit un accès aux paramètres
d'exécution du serveur. C'est essentiellement une interface alternative aux
- commandes <xref linkend="sql-show" endterm="sql-show-title">
- et <xref linkend="sql-set" endterm="sql-set-title">. Elle fournit
+ commandes <xref linkend="sql-show" endterm="sql-show-title"/>
+ et <xref linkend="sql-set" endterm="sql-set-title"/>. Elle fournit
aussi un accès à certaines informations des paramètres qui ne sont pas directement
accessibles avec <command>SHOW</command>, telles que les valeurs minimales et maximales.
</para>
@@ -6940,7 +6941,8 @@
<row>
<entry><structfield>vartype</structfield></entry>
<entry><type>text</type></entry>
- <entry>Type du paramètre (<literal>bool</literal>, <literal>enum</>,
+ <entry>Type du paramètre (<literal>bool</literal>,
+ <literal>enum</literal>,
<literal>integer</literal>,
<literal>real</literal> ou <literal>string</literal>)
</entry>
@@ -7222,7 +7224,7 @@
<entry></entry>
<entry>Liste de valeurs habituelles de la colonne. (NULL si
aucune valeur ne semble identique aux autres.)
- For some datatypes such as <type>tsvector</>, this is a list of
+ For some datatypes such as <type>tsvector</type>, this is a list of
the most common element values rather than values of the type itself.
</entry>
</row>
@@ -7235,9 +7237,9 @@
c'est-à-dire le nombre d'occurrences de chacune divisé par le nombre
total de lignes. (NULL lorsque
<structfield>most_common_vals</structfield> l'est.)
- For some datatypes such as <type>tsvector</>, it can also store some
+ For some datatypes such as <type>tsvector</type>, it can also store some
additional information, making it longer than the
- <structfield>most_common_vals</> array.
+ <structfield>most_common_vals</structfield> array.
</entry>
</row>
@@ -7573,7 +7575,7 @@
</para>
<table>
- <title><structname>pg_user_mappings</> Columns</title>
+ <title><structname>pg_user_mappings</structname> Columns</title>
<tgroup cols="3">
<thead>
@@ -7630,7 +7632,7 @@
<entry><type>text[]</type></entry>
<entry></entry>
<entry>
- User mapping specific options, as <quote>keyword=value</>
+ User mapping specific options, as <quote>keyword=value</quote>
strings, if the current user is the owner of the foreign
server, else null.
</entry>
@@ -7654,7 +7656,7 @@
</para>
<table>
- <title><structname>pg_views</> Columns</title>
+ <title><structname>pg_views</structname> Columns</title>
<tgroup cols="4">
<colspec colnum="1" colwidth="0.7*"/>
Modified: traduc/trunk/postgresql/charset.xml
===================================================================
--- traduc/trunk/postgresql/charset.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/charset.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -76,8 +76,8 @@
disponibles et leurs noms dépendent de l'éditeur du système d'exploitation
et de ce qui est installé. Sur la plupart des systèmes Unix, la commande
<literal>locale -a</literal> fournit la liste des locales disponibles.
- Windows uses more verbose names, such as <literal>German_Germany</>
- or <literal>Swedish_Sweden.1252</>.
+ Windows uses more verbose names, such as <literal>German_Germany</literal>
+ or <literal>Swedish_Sweden.1252</literal>.
</para>
<para>
@@ -334,7 +334,7 @@
<para>
Il existe, cependant une importante restriction : le jeu de caractère
de la base de données doit être compatible avec les variables
- d'environnement <envar>LC_CTYPE</envar> et <envar>LC_COLLATE</> de la base
+ d'environnement <envar>LC_CTYPE</envar> et <envar>LC_COLLATE</envar> de la base
de données. Pour les locales <literal>C</literal> ou <literal>POSIX</literal>, tous
les jeux de caractères sont autorisés, mais pour les locales,
il n'y a qu'un seul jeux de caractères qui fonctionne correctement.
@@ -490,7 +490,7 @@
<entry>Cyrillic (Russian)</entry>
<entry>Yes</entry>
<entry>1</entry>
- <entry><literal>KOI8</></entry>
+ <entry><literal>KOI8</literal></entry>
</row>
<row>
<entry><literal>KOI8U</literal></entry>
Modified: traduc/trunk/postgresql/citext.xml
===================================================================
--- traduc/trunk/postgresql/citext.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/citext.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -8,10 +8,10 @@
</indexterm>
<para>
- The <filename>citext</> module provides a case-insensitive
- character string type, <type>citext</>. Essentially, it internally calls
- <function>lower</> when comparing values. Otherwise, it behaves almost
- exactly like <type>text</>.
+ The <filename>citext</filename> module provides a case-insensitive
+ character string type, <type>citext</type>. Essentially, it internally calls
+ <function>lower</function> when comparing values. Otherwise, it behaves almost
+ exactly like <type>text</type>.
</para>
<sect2>
@@ -19,7 +19,8 @@
<para>
The standard approach to doing case-insensitive matches
- in <productname>PostgreSQL</> has been to use the <function>lower</>
+ in <productname>PostgreSQL</productname> has been to use the
+ <function>lower</function>
function when comparing values, for example
<programlisting>
@@ -35,19 +36,19 @@
<listitem>
<para>
It makes your SQL statements verbose, and you always have to remember to
- use <function>lower</> on both the column and the query value.
+ use <function>lower</function> on both the column and the query value.
</para>
</listitem>
<listitem>
<para>
It won't use an index, unless you create a functional index using
- <function>lower</>.
+ <function>lower</function>.
</para>
</listitem>
<listitem>
<para>
- If you declare a column as <literal>UNIQUE</> or <literal>PRIMARY
- KEY</>, the implicitly generated index is case-sensitive. So it's
+ If you declare a column as <literal>UNIQUE</literal> or <literal>PRIMARY
+ KEY</literal>, the implicitly generated index is case-sensitive. So it's
useless for case-insensitive searches, and it won't enforce
uniqueness case-insensitively.
</para>
@@ -55,13 +56,13 @@
</itemizedlist>
<para>
- The <type>citext</> data type allows you to eliminate calls
- to <function>lower</> in SQL queries, and allows a primary key to
- be case-insensitive. <type>citext</> is locale-aware, just
- like <type>text</>, which means that the comparison of uppercase and
+ The <type>citext</type> data type allows you to eliminate calls
+ to <function>lower</function> in SQL queries, and allows a primary key to
+ be case-insensitive. <type>citext</type> is locale-aware, just
+ like <type>text</type>, which means that the comparison of uppercase and
lowercase characters is dependent on the rules of
- the <literal>LC_CTYPE</> locale setting. Again, this behavior is
- identical to the use of <function>lower</> in queries. But because it's
+ the <literal>LC_CTYPE</literal> locale setting. Again, this behavior is
+ identical to the use of <function>lower</function> in queries. But because it's
done transparently by the datatype, you don't have to remember to do
anything special in your queries.
</para>
@@ -89,9 +90,9 @@
SELECT * FROM users WHERE nick = 'Larry';
</programlisting>
- The <command>SELECT</> statement will return one tuple, even though
- the <structfield>nick</> column was set to <quote>larry</> and the query
- was for <quote>Larry</>.
+ The <command>SELECT</command> statement will return one tuple, even though
+ the <structfield>nick</structfield> column was set to <quote>larry</quote> and the query
+ was for <quote>Larry</quote>.
</para>
</sect2>
@@ -99,64 +100,65 @@
<title>String Comparison Behavior</title>
<para>
In order to emulate a case-insensitive collation as closely as possible,
- there are <type>citext</>-specific versions of a number of the comparison
+ there are <type>citext</type>-specific versions of a number of the comparison
operators and functions. So, for example, the regular expression
- operators <literal>~</> and <literal>~*</> exhibit the same behavior when
- applied to <type>citext</>: they both compare case-insensitively.
+ operators <literal>~</literal> and <literal>~*</literal> exhibit the same behavior when
+ applied to <type>citext</type>: they both compare case-insensitively.
The same is true
- for <literal>!~</> and <literal>!~*</>, as well as for the
- <literal>LIKE</> operators <literal>~~</> and <literal>~~*</>, and
- <literal>!~~</> and <literal>!~~*</>. If you'd like to match
- case-sensitively, you can always cast to <type>text</> before comparing.
+ for <literal>!~</literal> and <literal>!~*</literal>, as well as for the
+ <literal>LIKE</literal> operators <literal>~~</literal> and
+ <literal>~~*</literal>, and
+ <literal>!~~</literal> and <literal>!~~*</literal>. If you'd like to match
+ case-sensitively, you can always cast to <type>text</type> before comparing.
</para>
<para>
Similarly, all of the following functions perform matching
- case-insensitively if their arguments are <type>citext</>:
+ case-insensitively if their arguments are <type>citext</type>:
</para>
<itemizedlist>
<listitem>
<para>
- <function>regexp_replace()</>
+ <function>regexp_replace()</function>
</para>
</listitem>
<listitem>
<para>
- <function>regexp_split_to_array()</>
+ <function>regexp_split_to_array()</function>
</para>
</listitem>
<listitem>
<para>
- <function>regexp_split_to_table()</>
+ <function>regexp_split_to_table()</function>
</para>
</listitem>
<listitem>
<para>
- <function>replace()</>
+ <function>replace()</function>
</para>
</listitem>
<listitem>
<para>
- <function>split_part()</>
+ <function>split_part()</function>
</para>
</listitem>
<listitem>
<para>
- <function>strpos()</>
+ <function>strpos()</function>
</para>
</listitem>
<listitem>
<para>
- <function>translate()</>
+ <function>translate()</function>
</para>
</listitem>
</itemizedlist>
<para>
For the regexp functions, if you want to match case-sensitively, you can
- specify the <quote>c</> flag to force a case-sensitive match. Otherwise,
- you must cast to <type>text</> before using one of these functions if
+ specify the <quote>c</quote> flag to force a case-sensitive match. Otherwise,
+ you must cast to <type>text</type> before using one of these functions if
you want case-sensitive behavior.
</para>
@@ -168,13 +170,13 @@
<itemizedlist>
<listitem>
<para>
- <type>citext</>'s behavior depends on
- the <literal>LC_CTYPE</> setting of your database. How it compares
+ <type>citext</type>'s behavior depends on
+ the <literal>LC_CTYPE</literal> setting of your database. How it compares
values is therefore determined when
- <application>initdb</> is run to create the cluster. It is not truly
+ <application>initdb</application> is run to create the cluster. It is not truly
case-insensitive in the terms defined by the Unicode standard.
Effectively, what this means is that, as long as you're happy with your
- collation, you should be happy with <type>citext</>'s comparisons. But
+ collation, you should be happy with <type>citext</type>'s comparisons. But
if you have data in different languages stored in your database, users
of one language may find their query results are not as expected if the
collation is for another language.
@@ -183,24 +185,25 @@
<listitem>
<para>
- <type>citext</> is not as efficient as <type>text</> because the
+ <type>citext</type> is not as efficient as <type>text</type> because the
operator functions and the btree comparison functions must make copies
of the data and convert it to lower case for comparisons. It is,
- however, slightly more efficient than using <function>lower</> to get
+ however, slightly more efficient than using <function>lower</function> to get
case-insensitive matching.
</para>
</listitem>
<listitem>
<para>
- <type>citext</> doesn't help much if you need data to compare
+ <type>citext</type> doesn't help much if you need data to compare
case-sensitively in some contexts and case-insensitively in other
- contexts. The standard answer is to use the <type>text</> type and
- manually use the <function>lower</> function when you need to compare
+ contexts. The standard answer is to use the <type>text</type> type and
+ manually use the <function>lower</function> function when you need to compare
case-insensitively; this works all right if case-insensitive comparison
is needed only infrequently. If you need case-insensitive most of
the time and case-sensitive infrequently, consider storing the data
- as <type>citext</> and explicitly casting the column to <type>text</>
+ as <type>citext</type> and explicitly casting the column to
+ <type>text</type>
when you want case-sensitive comparison. In either situation, you
will need two indexes if you want both types of searches to be fast.
</para>
@@ -216,7 +219,7 @@
</para>
<para>
- Inspired by the original <type>citext</> module by Donald Fraser.
+ Inspired by the original <type>citext</type> module by Donald Fraser.
</para>
</sect2>
Modified: traduc/trunk/postgresql/client-auth.xml
===================================================================
--- traduc/trunk/postgresql/client-auth.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/client-auth.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -382,11 +382,11 @@
</varlistentry>
<varlistentry>
- <term><literal>cert</></term>
+ <term><literal>cert</literal></term>
<listitem>
<para>
Authenticate using SSL client certificates. See
- <xref linkend="auth-cert"> for details.
+ <xref linkend="auth-cert"/> for details.
</para>
</listitem>
</varlistentry>
@@ -573,30 +573,31 @@
<para>
Ident maps are defined in the ident map file, which by default is named
- <filename>pg_ident.conf</><indexterm><primary>pg_ident.conf</primary></indexterm>
+ <filename>pg_ident.conf</filename><indexterm><primary>pg_ident.conf</primary></indexterm>
and is stored in the
cluster's data directory. (It is possible to place the map file
- elsewhere, however; see the <xref linkend="guc-ident-file">
+ elsewhere, however; see the <xref linkend="guc-ident-file"/>
configuration parameter.)
The ident map file contains lines of the general form:
<synopsis>
-<replaceable>map-name</> <replaceable>system-username</> <replaceable>database-username</>
+<replaceable>map-name</replaceable> <replaceable>system-username</replaceable> <replaceable>database-username</replaceable>
</synopsis>
Comments and whitespace are handled in the same way as in
- <filename>pg_hba.conf</>. The
- <replaceable>map-name</> is an arbitrary name that will be used to
+ <filename>pg_hba.conf</filename>. The
+ <replaceable>map-name</replaceable> is an arbitrary name that will be used to
refer to this mapping in <filename>pg_hba.conf</filename>. The other
two fields specify which operating system user is allowed to connect
- as which database user. The same <replaceable>map-name</> can be
+ as which database user. The same <replaceable>map-name</replaceable> can be
used repeatedly to specify more user-mappings within a single map.
There is no restriction regarding how many database users a given
operating system user can correspond to, nor vice versa.
</para>
<para>
- If the <replaceable>system-username</> field starts with a slash (<literal>/</>),
+ If the <replaceable>system-username</replaceable> field starts with a slash
+ (<literal>/</literal>),
the contents of the field is treated as a regular expression. This regular
expression supports a single capture, which can be back-referenced as
- <literal>\1</> (backslash-one). This allows the mapping of different syntax
+ <literal>\1</literal> (backslash-one). This allows the mapping of different syntax
names with a single line.
<programlisting>
mymap /(.*)@mydomain.com \1
@@ -612,28 +613,28 @@
<systemitem>SIGHUP</systemitem><indexterm><primary>SIGHUP</primary></indexterm>
signal. If you edit the file on an
active system, you will need to signal the server
- (using <literal>pg_ctl reload</> or <literal>kill -HUP</>) to make it
+ (using <literal>pg_ctl reload</literal> or <literal>kill -HUP</literal>) to make it
re-read the file.
</para>
<para>
A <filename>pg_ident.conf</filename> file that could be used in
- conjunction with the <filename>pg_hba.conf</> file in <xref
- linkend="example-pg-hba.conf"> is shown in <xref
- linkend="example-pg-ident.conf">. In this example setup, anyone
+ conjunction with the <filename>pg_hba.conf</filename> file in <xref
+ 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 <literal>bryanh</>, <literal>ann</>, or
- <literal>robert</> would not be granted access. Unix user
- <literal>robert</> would only be allowed access when he tries to
- connect as <productname>PostgreSQL</> user <literal>bob</>, not
- as <literal>robert</> or anyone else. <literal>ann</> would
- only be allowed to connect as <literal>ann</>. User
- <literal>bryanh</> would be allowed to connect as either
- <literal>bryanh</> himself or as <literal>guest1</>.
+ Unix user name <literal>bryanh</literal>, <literal>ann</literal>, or
+ <literal>robert</literal> would not be granted access. Unix user
+ <literal>robert</literal> would only be allowed access when he tries to
+ connect as <productname>PostgreSQL</productname> user <literal>bob</literal>, not
+ as <literal>robert</literal> or anyone else. <literal>ann</literal> would
+ only be allowed to connect as <literal>ann</literal>. User
+ <literal>bryanh</literal> would be allowed to connect as either
+ <literal>bryanh</literal> himself or as <literal>guest1</literal>.
</para>
<example id="example-pg-ident.conf">
- <title>An example <filename>pg_ident.conf</> file</title>
+ <title>An example <filename>pg_ident.conf</filename> file</title>
<programlisting>
# MAPNAME IDENT-USERNAME PG-USERNAME
@@ -732,8 +733,8 @@
S'il existe un risque d'attaque par <quote>interception (sniffing)</quote>
des mots de passe, il est préférable d'utiliser <literal>md5</literal>.
L'utilisation de <literal>password</literal>, en clair, est toujours à
- éviter quand c'est possible. <literal>md5</> cannot be used with <xref
- linkend="guc-db-user-namespace">.
+ éviter quand c'est possible. <literal>md5</literal> cannot be used with <xref
+ linkend="guc-db-user-namespace"/>.
</para>
<para>
@@ -791,7 +792,7 @@
<listitem>
<para>
Allows for mapping between system and database usernames. See
- <xref linkend="auth-username-maps"> for details.
+ <xref linkend="auth-username-maps"/> for details.
</para>
</listitem>
</varlistentry>
@@ -801,7 +802,7 @@
<listitem>
<para>
Include the realm name from the authenticated user principal. This is useful
- in combination with Username maps (See <xref linkend="auth-username-maps">
+ in combination with Username maps (See <xref linkend="auth-username-maps"/>
for details), especially with regular expressions, to map users from
multiple realms.
</para>
@@ -855,7 +856,7 @@
<listitem>
<para>
Allows for mapping between system and database usernames. See
- <xref linkend="auth-username-maps"> for details.
+ <xref linkend="auth-username-maps"/> for details.
</para>
</listitem>
</varlistentry>
@@ -865,7 +866,7 @@
<listitem>
<para>
Include the realm name from the authenticated user principal. This is useful
- in combination with Username maps (See <xref linkend="auth-username-maps">
+ in combination with Username maps (See <xref linkend="auth-username-maps"/>
for details), especially with regular expressions, to map users from
multiple realms.
</para>
@@ -960,7 +961,7 @@
Par défaut, le domaine du client n'est pas vérifié par
<productname>PostgreSQL</productname>. Si l'authentification inter-domaine
(<foreignphrase>cross-realm</foreignphrase>) est activée, on utilise le
- paramètre krb_realm in <filename>pg_hba.conf</>.
+ paramètre krb_realm in <filename>pg_hba.conf</filename>.
</para>
<para>
@@ -1010,7 +1011,7 @@
<listitem>
<para>
Allows for mapping between system and database usernames. See
- <xref linkend="auth-username-maps"> for details.
+ <xref linkend="auth-username-maps"/> for details.
</para>
</listitem>
</varlistentry>
@@ -1020,7 +1021,7 @@
<listitem>
<para>
Include the realm name from the authenticated user principal. This is useful
- in combination with Username maps (See <xref linkend="auth-username-maps">
+ in combination with Username maps (See <xref linkend="auth-username-maps"/>
for details), especially with regular expressions, to map users from
multiple realms.
</para>
@@ -1042,9 +1043,9 @@
<listitem>
<para>
Sets the host name part of the service principal.
- This, combined with <varname>krb_srvname</>, is used to generate
+ This, combined with <varname>krb_srvname</varname>, is used to generate
the complete service principal, that is
- <varname>krb_srvname</><literal>/</><varname>krb_server_hostname</><literal>@</>REALM.
+ <varname>krb_srvname</varname><literal>/</literal><varname>krb_server_hostname</varname><literal>@</literal>REALM.
If not set, the default is the server host name.
</para>
</listitem>
@@ -1076,7 +1077,7 @@
<listitem>
<para>
Allows for mapping between system and database usernames. See
- <xref linkend="auth-username-maps"> for details.
+ <xref linkend="auth-username-maps"/> for details.
</para>
</listitem>
</varlistentry>
@@ -1181,9 +1182,10 @@
<para>
The server will bind to the distinguished name constructed as
- <replaceable>prefix</> <replaceable>username</> <replaceable>suffix</>.
+ <replaceable>prefix</replaceable> <replaceable>username</replaceable>
+ <replaceable>suffix</replaceable>.
before the bind. Typically, the prefix parameter is used to specify
- <replaceable>cn=</>, or <replaceable>DOMAIN\</> in an Active
+ <replaceable>cn=</replaceable>, or <replaceable>DOMAIN\</replaceable> in an Active
Directory environment, and suffix is used to specify the remaining part
of the DN in a non-Active Directory environment.
</para>
Modified: traduc/trunk/postgresql/config.xml
===================================================================
--- traduc/trunk/postgresql/config.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/config.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -39,7 +39,8 @@
Certains paramètres indiquent une valeur de taille mémoire ou de durée.
Ils ont chacun une unité implicite, soit Ko, soit blocs (typiquement
8 Ko), soit millisecondes, soit secondes, soit minutes. Default units
- can be found by referencing <structname>pg_settings</>.<structfield>unit</>.
+ can be found by referencing
+ <structname>pg_settings</structname>.<structfield>unit</structfield>.
Pour simplifier la saisie, une unité différente peut être indiquée
de façon explicite. Les unités mémoire valides sont <literal>kB</literal>
(kilo-octets), <literal>MB</literal> (Méga-octets) et
@@ -52,10 +53,10 @@
</para>
<para>
- Parameters of type <quote>enum</> are specified in the same way as string
+ Parameters of type <quote>enum</quote> are specified in the same way as string
parameters, but are restricted to a limited set of values. The allowed
- values can be found
- from <structname>pg_settings</>.<structfield>enumvals</>.
+ values can be found from
+ <structname>pg_settings</structname>.<structfield>enumvals</structfield>.
Enum parameter values are case-insensitive.
</para>
@@ -600,7 +601,7 @@
Active les connexions <acronym>SSL</acronym>. Lire la
<xref linkend="ssl-tcp"/> avant de l'utiliser. Désactivé par défaut.
Ce paramètre ne peut être configuré qu'au lancement du serveur.
- <acronym>SSL</> communication is only possible with TCP/IP connections.
+ <acronym>SSL</acronym> communication is only possible with TCP/IP connections.
</para>
</listitem>
</varlistentry>
@@ -651,7 +652,7 @@
serveur Kerberos. Voir la <xref linkend="kerberos-auth"/> et la
la <xref linkend="gssapi-auth"/> pour les
détails. Ce paramètre ne peut être configuré in the
- <filename>postgresql.conf</> file et au lancement
+ <filename>postgresql.conf</filename> file et au lancement
du serveur.
</para>
</listitem>
@@ -666,7 +667,7 @@
<para>
Configure le nom du service Kerberos. Voir la <xref linkend="kerberos-auth"/>
pour les détails. Ce paramètre ne peut être configuré in the
- <filename>postgresql.conf</> file ou au lancement
+ <filename>postgresql.conf</filename> file ou au lancement
du serveur.
</para>
</listitem>
@@ -682,7 +683,7 @@
Indique si les noms des utilisateurs Kerberos et GSSAPI doivent être traités en
respectant la casse. Désactivé par défaut (insensible à la casse, valeur
<literal>off</literal>), ce paramètre ne peut être configuré
- in the <filename>postgresql.conf</> file et qu'au
+ in the <filename>postgresql.conf</filename> file et qu'au
lancement du serveur.
</para>
</listitem>
@@ -713,14 +714,14 @@
</para>
<para>
- <varname>db_user_namespace</> causes the client's and
+ <varname>db_user_namespace</varname> causes the client's and
server's user name representation to differ.
Authentication checks are always done with the server's user name
so authentication methods must be configured for the
server's user name, not the client's. Because
- <literal>md5</> uses the user name as salt on both the
- client and server, <literal>md5</> cannot be used with
- <varname>db_user_namespace</>.
+ <literal>md5</literal> uses the user name as salt on both the
+ client and server, <literal>md5</literal> cannot be used with
+ <varname>db_user_namespace</varname>.
</para>
<para>
@@ -1107,7 +1108,7 @@
<para>
When using cost-based vacuuming, appropriate values for
- <varname>vacuum_cost_delay</> are usually quite small, perhaps
+ <varname>vacuum_cost_delay</varname> are usually quite small, perhaps
10 or 20 milliseconds. Adjusting vacuum's resource consumption
is best done by changing the other vacuum cost parameters.
</para>
@@ -1312,14 +1313,14 @@
<varlistentry id="guc-effective-io-concurrency" xreflabel="effective_io_concurrency">
<term><varname>effective_io_concurrency</varname> (<type>integer</type>)</term>
<indexterm>
- <primary><varname>effective_io_concurrency</> configuration parameter</primary>
+ <primary><varname>effective_io_concurrency</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
Sets the number of concurrent disk I/O operations that
- <productname>PostgreSQL</> expects can be executed
+ <productname>PostgreSQL</productname> expects can be executed
simultaneously. Raising this value will increase the number of I/O
- operations that any individual <productname>PostgreSQL</> session
+ operations that any individual <productname>PostgreSQL</productname> session
attempts to initiate in parallel. The allowed range is 1 to 1000,
or zero to disable issuance of asynchronous I/O requests.
</para>
@@ -1342,7 +1343,8 @@
</para>
<para>
- Asynchronous I/O depends on an effective <function>posix_fadvise</>
+ Asynchronous I/O depends on an effective
+ <function>posix_fadvise</function>
function, which some operating systems lack. If the function is not
present then setting this parameter to anything but zero will result
in an error. On some operating systems the function is present but
@@ -2326,17 +2328,17 @@
<para>
Controls the query planner's use of table constraints to
optimize queries.
- The allowed values of <varname>constraint_exclusion</> are
- <literal>on</> (examine constraints for all tables),
- <literal>off</> (never examine constraints), and
- <literal>partition</> (examine constraints only for inheritance child
- tables and <literal>UNION ALL</> subqueries).
- <literal>partition</> is the default setting.
+ The allowed values of <varname>constraint_exclusion</varname> are
+ <literal>on</literal> (examine constraints for all tables),
+ <literal>off</literal> (never examine constraints), and
+ <literal>partition</literal> (examine constraints only for inheritance child
+ tables and <literal>UNION ALL</literal> subqueries).
+ <literal>partition</literal> is the default setting.
</para>
<para>
When this parameter allows it for a particular table, the planner
- compares query conditions with the table's <literal>CHECK</>
+ compares query conditions with the table's <literal>CHECK</literal>
constraints, and omits scanning tables for which the conditions
contradict the constraints. For example:
@@ -2353,7 +2355,6 @@
</para>
<para>
- <para>
Currently, constraint exclusion is enabled by default
only for cases that are often used to implement table partitioning.
Turning it on for all tables imposes extra planning overhead that is
@@ -2363,7 +2364,7 @@
</para>
<para>
- Refer to <xref linkend="ddl-partitioning-constraint-exclusion"> for
+ Refer to <xref linkend="ddl-partitioning-constraint-exclusion"/> for
more information on using constraint exclusion and partitioning.
</para>
</listitem>
@@ -2372,13 +2373,13 @@
<varlistentry id="guc-cursor-tuple-fraction" xreflabel="cursor_tuple_fraction">
<term><varname>cursor_tuple_fraction</varname> (<type>floating point</type>)</term>
<indexterm>
- <primary><varname>cursor_tuple_fraction</> configuration parameter</primary>
+ <primary><varname>cursor_tuple_fraction</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
Sets the planner's estimate of the fraction of a cursor's rows that
will be retrieved. The default is 0.1. Smaller values of this
- setting bias the planner towards using <quote>fast start</> plans
+ setting bias the planner towards using <quote>fast start</quote> plans
for cursors, which will retrieve the first few rows quickly while
perhaps taking a long time to fetch all rows. Larger values
put more emphasis on the total estimated time. At the maximum
@@ -2582,7 +2583,8 @@
le nom du fichier CSV est <literal>server_log.1093827753.csv</literal>.
</para>
<para>
- This parameter can only be set in the <filename>postgresql.conf</>
+ This parameter can only be set in the
+ <filename>postgresql.conf</filename>
file or on the server command line.
</para>
</listitem>
@@ -2994,11 +2996,11 @@
Ces paramètres activent plusieurs sorties de débogage.
When set, they print the resulting parse tree, the query rewriter
output, or the execution plan for each executed query.
- These messages are emitted at <literal>LOG</> message level, so by
+ These messages are emitted at <literal>LOG</literal> message level, so by
default they will appear in the server log but will not be sent to the
client. You can change that by adjusting
- <xref linkend="guc-client-min-messages"> and/or
- <xref linkend="guc-log-min-messages">.
+ <xref linkend="guc-client-min-messages"/> and/or
+ <xref linkend="guc-log-min-messages"/>.
Ces paramètres sont désactivés par défaut.
</para>
</listitem>
@@ -3007,7 +3009,7 @@
<varlistentry>
<term><varname>debug_pretty_print</varname> (<type>boolean</type>)</term>
<indexterm>
- <primary><varname>debug_pretty_print</> configuration parameter</primary>
+ <primary><varname>debug_pretty_print</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -3015,7 +3017,7 @@
produced by <varname>debug_print_parse</varname>,
<varname>debug_print_rewritten</varname>, or
<varname>debug_print_plan</varname>. This results in more readable
- but much longer output than the <quote>compact</> format used when
+ but much longer output than the <quote>compact</quote> format used when
it is off. It is on by default.
</para>
</listitem>
@@ -3534,13 +3536,13 @@
<varlistentry id="guc-track-activity-query-size" xreflabel="track_activity_query_size">
<term><varname>track_activity_query_size</varname> (<type>integer</type>)</term>
<indexterm>
- <primary><varname>track_activity_query_size</> configuration parameter</primary>
+ <primary><varname>track_activity_query_size</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
Specifies the number of bytes reserved to track the currently
executing command for each active session, for the
- <structname>pg_stat_activity</>.<structfield>current_query</> field.
+ <structname>pg_stat_activity</structname>.<structfield>current_query</structfield> field.
The default value is 1024. This parameter can only be set at server
start.
</para>
@@ -3565,7 +3567,7 @@
<varlistentry id="guc-track-functions" xreflabel="track_functions">
<term><varname>track_functions</varname> (<type>enum</type>)</term>
<indexterm>
- <primary><varname>track_functions</> configuration parameter</primary>
+ <primary><varname>track_functions</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -3578,7 +3580,8 @@
<note>
<para>
- SQL-language functions that are simple enough to be <quote>inlined</>
+ SQL-language functions that are simple enough to be
+ <quote>inlined</quote>
into the calling query will not be tracked, regardless of this
setting.
</para>
@@ -3605,7 +3608,7 @@
<varlistentry id="guc-stats-temp-directory" xreflabel="stats_temp_directory">
<term><varname>stats_temp_directory</varname> (<type>string</type>)</term>
<indexterm>
- <primary><varname>stats_temp_directory</> configuration parameter</primary>
+ <primary><varname>stats_temp_directory</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -3614,7 +3617,8 @@
is <filename>pg_stat_tmp</filename>. Pointing this at a RAM based
filesystem will decrease physical I/O requirements and can lead to
improved performance.
- This parameter can only be set in the <filename>postgresql.conf</>
+ This parameter can only be set in the
+ <filename>postgresql.conf</filename>
file or on the server command line.
</para>
</listitem>
@@ -4188,20 +4192,20 @@
<varlistentry id="guc-vacuum-freeze-table-age" xreflabel="vacuum_freeze_table_age">
<term><varname>vacuum_freeze_table_age</varname> (<type>integer</type>)</term>
<indexterm>
- <primary><varname>vacuum_freeze_table_age</> configuration parameter</primary>
+ <primary><varname>vacuum_freeze_table_age</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
- <command>VACUUM</> performs a whole-table scan if the table's
- <structname>pg_class</>.<structfield>relfrozenxid</> field has reached
+ <command>VACUUM</command> performs a whole-table scan if the table's
+ <structname>pg_class</structname>.<structfield>relfrozenxid</structfield> field has reached
the age specified by this setting. The default is 150 million
transactions. Although users can set this value anywhere from zero to
- one billion, <command>VACUUM</> will silently limit the effective value
- to 95% of <xref linkend="guc-autovacuum-freeze-max-age">, so that a
- periodical manual <command>VACUUM</> has a chance to run before an
+ one billion, <command>VACUUM</command> will silently limit the effective value
+ to 95% of <xref linkend="guc-autovacuum-freeze-max-age"/>, so that a
+ periodical manual <command>VACUUM</command> has a chance to run before an
anti-wraparound autovacuum is launched for the table. For more
information see
- <xref linkend="vacuum-for-wraparound">.
+ <xref linkend="vacuum-for-wraparound"/>.
</para>
</listitem>
</varlistentry>
@@ -4325,29 +4329,29 @@
<varlistentry id="guc-intervalstyle" xreflabel="IntervalStyle">
<term><varname>IntervalStyle</varname> (<type>enum</type>)</term>
<indexterm>
- <primary><varname>IntervalStyle</> configuration parameter</primary>
+ <primary><varname>IntervalStyle</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
Sets the display format for interval values.
- The value <literal>sql_standard</> will produce
+ The value <literal>sql_standard</literal> will produce
output matching <acronym>SQL</acronym> standard interval literals.
- The value <literal>postgres</> (which is the default) will produce
- output matching <productname>PostgreSQL</> releases prior to 8.4
- when the <xref linkend="guc-datestyle">
- parameter was set to <literal>ISO</>.
- The value <literal>postgres_verbose</> will produce output
- matching <productname>PostgreSQL</> releases prior to 8.4
- when the <varname>DateStyle</>
- parameter was set to non-<literal>ISO</> output.
- The value <literal>iso_8601</> will produce output matching the time
- interval <quote>format with designators</> defined in section
+ The value <literal>postgres</literal> (which is the default) will produce
+ output matching <productname>PostgreSQL</productname> releases prior to 8.4
+ when the <xref linkend="guc-datestyle"/>
+ parameter was set to <literal>ISO</literal>.
+ The value <literal>postgres_verbose</literal> will produce output
+ matching <productname>PostgreSQL</productname> releases prior to 8.4
+ when the <varname>DateStyle</varname>
+ parameter was set to non-<literal>ISO</literal> output.
+ The value <literal>iso_8601</literal> will produce output matching the time
+ interval <quote>format with designators</quote> defined in section
4.4.3.2 of ISO 8601.
</para>
<para>
- The <varname>IntervalStyle</> parameter also affects the
+ The <varname>IntervalStyle</varname> parameter also affects the
interpretation of ambiguous interval input. See
- <xref linkend="datatype-interval-input"> for more information.
+ <xref linkend="datatype-interval-input"/> for more information.
</para>
</listitem>
</varlistentry>
@@ -5184,15 +5188,16 @@
<varlistentry id="guc-segment-size" xreflabel="segment_size">
<term><varname>segment_size</varname> (<type>integer</type>)</term>
<indexterm>
- <primary><varname>segment_size</> configuration parameter</primary>
+ <primary><varname>segment_size</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
Reports the number of blocks (pages) that can be stored within a file
- segment. It is determined by the value of <literal>RELSEG_SIZE</>
+ segment. It is determined by the value of
+ <literal>RELSEG_SIZE</literal>
when building the server. The maximum size of a segment file in bytes
- is equal to <varname>segment_size</> multiplied by
- <varname>block_size</>; by default this is 1GB.
+ is equal to <varname>segment_size</varname> multiplied by
+ <varname>block_size</varname>; by default this is 1GB.
</para>
</listitem>
</varlistentry>
@@ -5244,12 +5249,12 @@
<varlistentry id="guc-wal-block-size" xreflabel="wal_block_size">
<term><varname>wal_block_size</varname> (<type>integer</type>)</term>
<indexterm>
- <primary><varname>wal_block_size</> configuration parameter</primary>
+ <primary><varname>wal_block_size</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
Reports the size of a WAL disk block. It is determined by the value
- of <literal>XLOG_BLCKSZ</> when building the server. The default value
+ of <literal>XLOG_BLCKSZ</literal> when building the server. The default value
is 8192 bytes.
</para>
</listitem>
@@ -5258,14 +5263,15 @@
<varlistentry id="guc-wal-segment-size" xreflabel="wal_segment_size">
<term><varname>wal_segment_size</varname> (<type>integer</type>)</term>
<indexterm>
- <primary><varname>wal_segment_size</> configuration parameter</primary>
+ <primary><varname>wal_segment_size</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
Reports the number of blocks (pages) in a WAL segment file.
The total size of a WAL segment file in bytes is equal to
- <varname>wal_segment_size</> multiplied by <varname>wal_block_size</>;
- by default this is 16MB. See <xref linkend="wal-configuration"> for
+ <varname>wal_segment_size</varname> multiplied by
+ <varname>wal_block_size</varname>;
+ by default this is 16MB. See <xref linkend="wal-configuration"/> for
more information.
</para>
</listitem>
@@ -5473,7 +5479,7 @@
<varlistentry>
<term><varname>trace_locks</varname> (<type>boolean</type>)</term>
<indexterm>
- <primary><varname>trace_locks</> configuration parameter</primary>
+ <primary><varname>trace_locks</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -5522,7 +5528,7 @@
<varlistentry>
<term><varname>trace_lwlocks</varname> (<type>boolean</type>)</term>
<indexterm>
- <primary><varname>trace_lwlocks</> configuration parameter</primary>
+ <primary><varname>trace_lwlocks</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -5541,7 +5547,7 @@
<varlistentry>
<term><varname>trace_userlocks</varname> (<type>boolean</type>)</term>
<indexterm>
- <primary><varname>trace_userlocks</> configuration parameter</primary>
+ <primary><varname>trace_userlocks</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -5563,7 +5569,7 @@
<varlistentry>
<term><varname>trace_lock_oidmin</varname> (<type>integer</type>)</term>
<indexterm>
- <primary><varname>trace_lock_oidmin</> configuration parameter</primary>
+ <primary><varname>trace_lock_oidmin</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -5581,7 +5587,7 @@
<varlistentry>
<term><varname>trace_lock_table</varname> (<type>integer</type>)</term>
<indexterm>
- <primary><varname>trace_lock_table</> configuration parameter</primary>
+ <primary><varname>trace_lock_table</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -5598,7 +5604,7 @@
<varlistentry>
<term><varname>debug_deadlocks</varname> (<type>boolean</type>)</term>
<indexterm>
- <primary><varname>debug_deadlocks</> configuration parameter</primary>
+ <primary><varname>debug_deadlocks</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -5616,7 +5622,7 @@
<varlistentry>
<term><varname>log_btree_build_stats</varname> (<type>boolean</type>)</term>
<indexterm>
- <primary><varname>log_btree_build_stats</> configuration parameter</primary>
+ <primary><varname>log_btree_build_stats</varname> configuration parameter</primary>
</indexterm>
<listitem>
<para>
Modified: traduc/trunk/postgresql/datatype.xml
===================================================================
--- traduc/trunk/postgresql/datatype.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/datatype.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1530,9 +1530,9 @@
-->
<note>
<para>
- When <type>timestamp</> values are stored as eight-byte integers
+ When <type>timestamp</type> values are stored as eight-byte integers
(currently the default), microsecond precision is available over
- the full range of values. When <type>timestamp</> values are
+ the full range of values. When <type>timestamp</type> values are
stored as double precision floating-point numbers instead (a
deprecated compile-time option), the effective limit of precision
might be less than 6. <type>timestamp</type> values are stored as
@@ -1580,7 +1580,7 @@
Input falling outside the specified set of fields is silently discarded.
Note that if both <replaceable>fields</replaceable> and
<replaceable>precision</replaceable> are specified, the
- <replaceable>fields</replaceable> must include <literal>SECOND</>,
+ <replaceable>fields</replaceable> must include <literal>SECOND</literal>,
since the precision applies only to the seconds.
</para>
@@ -2240,7 +2240,7 @@
arbitraires, particulièrement en respect des règles de changement
d'heure (heure d'été/heure d'hiver).
<productname>PostgreSQL</productname> uses the widely-used
- <literal>zoneinfo</> time zone database for information about
+ <literal>zoneinfo</literal> time zone database for information about
historical time zone rules. For times in the future, the assumption
is that the latest known rules for a given time zone will
continue to be observed indefinitely far into the future.
@@ -2450,52 +2450,55 @@
verbose syntax:
<synopsis>
-<optional>@</> <replaceable>quantity</> <replaceable>unit</> <optional><replaceable>quantity</> <replaceable>unit</>...</> <optional><replaceable>direction</></optional>
+<optional>@</optional> <replaceable>quantity</replaceable>
+<replaceable>unit</replaceable> <optional><replaceable>quantity</replaceable>
+<replaceable>unit</replaceable>...</optional>
+<optional><replaceable>direction</replaceable></optional>
</synopsis>
- where <replaceable>quantity</> is a number (possibly signed);
- <replaceable>unit</> is <literal>microsecond</literal>,
+ where <replaceable>quantity</replaceable> is a number (possibly signed);
+ <replaceable>unit</replaceable> is <literal>microsecond</literal>,
<literal>millisecond</literal>, <literal>second</literal>,
<literal>minute</literal>, <literal>hour</literal>, <literal>day</literal>,
<literal>week</literal>, <literal>month</literal>, <literal>year</literal>,
<literal>decade</literal>, <literal>century</literal>, <literal>millennium</literal>,
or abbreviations or plurals of these units;
- <replaceable>direction</> can be <literal>ago</literal> or
- empty. The at sign (<literal>@</>) is optional noise. The amounts
+ <replaceable>direction</replaceable> can be <literal>ago</literal> or
+ empty. The at sign (<literal>@</literal>) is optional noise. The amounts
of different units are implicitly added up with appropriate
sign accounting. <literal>ago</literal> negates all the fields.
This syntax is also used for interval output, if
- <xref linkend="guc-intervalstyle"> is set to
- <literal>postgres_verbose</>.
+ <xref linkend="guc-intervalstyle"/> is set to
+ <literal>postgres_verbose</literal>.
</para>
<para>
Quantities of days, hours, minutes, and seconds can be specified without
- explicit unit markings. For example, <literal>'1 12:59:10'</> is read
- the same as <literal>'1 day 12 hours 59 min 10 sec'</>. Also,
+ explicit unit markings. For example, <literal>'1 12:59:10'</literal> is read
+ the same as <literal>'1 day 12 hours 59 min 10 sec'</literal>. Also,
a combination of years and months can be specified with a dash;
- for example <literal>'200-10'</> is read the same as <literal>'200 years
- 10 months'</>. (These shorter forms are in fact the only ones allowed
+ for example <literal>'200-10'</literal> is read the same as <literal>'200 years
+ 10 months'</literal>. (These shorter forms are in fact the only ones allowed
by the <acronym>SQL</acronym> standard, and are used for output when
- <varname>IntervalStyle</> is set to <literal>sql_standard</literal>.)
+ <varname>IntervalStyle</varname> is set to <literal>sql_standard</literal>.)
</para>
<para>
Interval values can also be written as ISO 8601 time intervals, using
- either the <quote>format with designators</> of the standard's section
- 4.4.3.2 or the <quote>alternative format</> of section 4.4.3.3. The
+ either the <quote>format with designators</quote> of the standard's section
+ 4.4.3.2 or the <quote>alternative format</quote> of section 4.4.3.3. The
format with designators looks like this:
<synopsis>
-P <replaceable>quantity</> <replaceable>unit</> <optional> <replaceable>quantity</> <replaceable>unit</> ...</optional> <optional> T <optional> <replaceable>quantity</> <replaceable>unit</> ...</optional></optional>
+P <replaceable>quantity</replaceable> <replaceable>unit</replaceable> <optional> <replaceable>quantity</replaceable> <replaceable>unit</replaceable> ...</optional> <optional> T <optional> <replaceable>quantity</replaceable> <replaceable>unit</replaceable> ...</optional></optional>
</synopsis>
- The string must start with a <literal>P</>, and may include a
- <literal>T</> that introduces the time-of-day units. The
+ The string must start with a <literal>P</literal>, and may include a
+ <literal>T</literal> that introduces the time-of-day units. The
available unit abbreviations are given in <xref
- linkend="datatype-interval-iso8601-units">. Units may be
+ linkend="datatype-interval-iso8601-units"/>. Units may be
omitted, and may be specified in any order, but units smaller than
- a day must appear after <literal>T</>. In particular, the meaning of
- <literal>M</> depends on whether it is before or after
- <literal>T</>.
+ a day must appear after <literal>T</literal>. In particular, the meaning of
+ <literal>M</literal> depends on whether it is before or after
+ <literal>T</literal>.
</para>
<table id="datatype-interval-iso8601-units">
@@ -2543,47 +2546,47 @@
<para>
In the alternative format:
<synopsis>
-P <optional> <replaceable>years</>-<replaceable>months</>-<replaceable>days</> </optional> <optional> T <replaceable>hours</>:<replaceable>minutes</>:<replaceable>seconds</> </optional>
+P <optional> <replaceable>years</replaceable>-<replaceable>months</replaceable>-<replaceable>days</replaceable> </optional> <optional> T <replaceable>hours</replaceable>:<replaceable>minutes</replaceable>:<replaceable>seconds</replaceable> </optional>
</synopsis>
the string must begin with <literal>P</literal>, and a
- <literal>T</> separates the date and time parts of the interval.
+ <literal>T</literal> separates the date and time parts of the interval.
The values are given as numbers similar to ISO 8601 dates.
</para>
<para>
- When writing an interval constant with a <replaceable>fields</>
+ When writing an interval constant with a <replaceable>fields</replaceable>
specification, or when assigning to an interval column that was defined
- with a <replaceable>fields</> specification, the interpretation of
- unmarked quantities depends on the <replaceable>fields</>. For
- example <literal>INTERVAL '1' YEAR</> is read as 1 year, whereas
- <literal>INTERVAL '1'</> means 1 second.
+ with a <replaceable>fields</replaceable> specification, the interpretation of
+ unmarked quantities depends on the <replaceable>fields</replaceable>. For
+ example <literal>INTERVAL '1' YEAR</literal> is read as 1 year, whereas
+ <literal>INTERVAL '1'</literal> means 1 second.
</para>
<para>
- According to the <acronym>SQL</> standard all fields of an interval
+ According to the <acronym>SQL</acronym> standard all fields of an interval
value must have the same sign, so a leading negative sign applies to all
fields; for example the negative sign in the interval literal
- <literal>'-1 2:03:04'</> applies to both the days and hour/minute/second
- parts. <productname>PostgreSQL</> allows the fields to have different
+ <literal>'-1 2:03:04'</literal> applies to both the days and hour/minute/second
+ parts. <productname>PostgreSQL</productname> allows the fields to have different
signs, and traditionally treats each field in the textual representation
as independently signed, so that the hour/minute/second part is
- considered positive in this example. If <varname>IntervalStyle</> is
+ considered positive in this example. If <varname>IntervalStyle</varname> is
set to <literal>sql_standard</literal> then a leading sign is considered
to apply to all fields (but only if no additional signs appear).
- Otherwise the traditional <productname>PostgreSQL</> interpretation is
+ Otherwise the traditional <productname>PostgreSQL</productname> interpretation is
used. To avoid ambiguity, it's recommended to attach an explicit sign
to each field if any field is negative.
</para>
<para>
- Internally <type>interval</> values are stored as months, days,
+ Internally <type>interval</type> values are stored as months, days,
and seconds. This is done because the number of days in a month
varies, and a day can have 23 or 25 hours if a daylight savings
time adjustment is involved. The months and days fields are integers
while the seconds field can store fractions. Because intervals are
- usually created from constant strings or <type>timestamp</> subtraction,
+ usually created from constant strings or <type>timestamp</type> subtraction,
this storage method works well in most cases. Functions
- <function>justify_days</> and <function>justify_hours</> are
+ <function>justify_days</function> and <function>justify_hours</function> are
available for adjusting days and hours that overflow their normal
ranges.
</para>
@@ -2591,18 +2594,18 @@
<para>
In the verbose input format, and in some fields of the more compact
input formats, field values can have fractional parts; for example
- <literal>'1.5 week'</> or <literal>'01:02:03.45'</>. Such input is
+ <literal>'1.5 week'</literal> or <literal>'01:02:03.45'</literal>. Such input is
converted to the appropriate number of months, days, and seconds
for storage. When this would result in a fractional number of
months or days, the fraction is added to the lower-order fields
using the conversion factors 1 month = 30 days and 1 day = 24 hours.
- For example, <literal>'1.5 month'</> becomes 1 month and 15 days.
+ For example, <literal>'1.5 month'</literal> becomes 1 month and 15 days.
Only seconds will ever be shown as fractional on output.
</para>
<para>
- <xref linkend="datatype-interval-input-examples"> shows some examples
- of valid <type>interval</> input.
+ <xref linkend="datatype-interval-input-examples"/> shows some examples
+ of valid <type>interval</type> input.
</para>
<table id="datatype-interval-input-examples">
@@ -2629,11 +2632,11 @@
</row>
<row>
<entry>P1Y2M3DT4H5M6S</entry>
- <entry>ISO 8601 <quote>format with designators</>: same meaning as above</entry>
+ <entry>ISO 8601 <quote>format with designators</quote>: same meaning as above</entry>
</row>
<row>
<entry>P0001-02-03T04:05:06</entry>
- <entry>ISO 8601 <quote>alternative format</>: same meaning as above</entry>
+ <entry>ISO 8601 <quote>alternative format</quote>: same meaning as above</entry>
</row>
</tbody>
</tgroup>
@@ -2652,16 +2655,16 @@
<para>
The output format of the interval type can be set to one of the
- four styles <literal>sql_standard</>, <literal>postgres</>,
- <literal>postgres_verbose</>, or <literal>iso_8601</>,
+ four styles <literal>sql_standard</literal>, <literal>postgres</literal>,
+ <literal>postgres_verbose</literal>, or <literal>iso_8601</literal>,
using the command <literal>SET intervalstyle</literal>.
- The default is the <literal>postgres</> format.
- <xref linkend="interval-style-output-table"> shows examples of each
+ The default is the <literal>postgres</literal> format.
+ <xref linkend="interval-style-output-table"/> shows examples of each
output style.
</para>
<para>
- The <literal>sql_standard</> style produces output that conforms to
+ The <literal>sql_standard</literal> style produces output that conforms to
the SQL standard's specification for interval literal strings, if
the interval value meets the standard's restrictions (either year-month
only or day-time only, with no mixing of positive
@@ -2671,20 +2674,21 @@
</para>
<para>
- The output of the <literal>postgres</> style matches the output of
- <productname>PostgreSQL</> releases prior to 8.4 when the
- <xref linkend="guc-datestyle"> parameter was set to <literal>ISO</>.
+ The output of the <literal>postgres</literal> style matches the output of
+ <productname>PostgreSQL</productname> releases prior to 8.4 when the
+ <xref linkend="guc-datestyle"/> parameter was set to <literal>ISO</literal>.
</para>
<para>
- The output of the <literal>postgres_verbose</> style matches the output of
- <productname>PostgreSQL</> releases prior to 8.4 when the
- <varname>DateStyle</> parameter was set to non-<literal>ISO</> output.
+ The output of the <literal>postgres_verbose</literal> style matches the output of
+ <productname>PostgreSQL</productname> releases prior to 8.4 when the
+ <varname>DateStyle</varname> parameter was set to
+ non-<literal>ISO</literal> output.
</para>
<para>
- The output of the <literal>iso_8601</> style matches the <quote>format
- with designators</> described in section 4.4.3.2 of the
+ The output of the <literal>iso_8601</literal> style matches the <quote>format
+ with designators</quote> described in section 4.4.3.2 of the
ISO 8601 standard.
</para>
@@ -2701,25 +2705,25 @@
</thead>
<tbody>
<row>
- <entry><literal>sql_standard</></entry>
+ <entry><literal>sql_standard</literal></entry>
<entry>1-2</entry>
<entry>3 4:05:06</entry>
<entry>-1-2 +3 -4:05:06</entry>
</row>
<row>
- <entry><literal>postgres</></entry>
+ <entry><literal>postgres</literal></entry>
<entry>1 year 2 mons</entry>
<entry>3 days 04:05:06</entry>
<entry>-1 year -2 mons +3 days -04:05:06</entry>
</row>
<row>
- <entry><literal>postgres_verbose</></entry>
+ <entry><literal>postgres_verbose</literal></entry>
<entry>@ 1 year 2 mons</entry>
<entry>@ 3 days 4 hours 5 mins 6 secs</entry>
<entry>@ 1 year 2 mons -3 days 4 hours 5 mins 6 secs ago</entry>
</row>
<row>
- <entry><literal>iso_8601</></entry>
+ <entry><literal>iso_8601</literal></entry>
<entry>P1Y2M</entry>
<entry>P3DT4H5M6S</entry>
<entry>P-1Y-2M3DT-4H-5M-6S</entry>
@@ -3820,7 +3824,8 @@
</para>
<para>
- Also, lexemes in a <type>tsquery</type> can be labeled with <literal>*</>
+ Also, lexemes in a <type>tsquery</type> can be labeled with
+ <literal>*</literal>
to specify prefix matching:
<programlisting>
SELECT 'super:*'::tsquery;
@@ -3828,8 +3833,8 @@
-----------
'super':*
</programlisting>
- This query will match any word in a <type>tsvector</> that begins
- with <quote>super</>.
+ This query will match any word in a <type>tsvector</type> that begins
+ with <quote>super</quote>.
</para>
<para>
Modified: traduc/trunk/postgresql/dblink.xml
===================================================================
--- traduc/trunk/postgresql/dblink.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/dblink.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -163,7 +163,7 @@
qui exécute le serveur <productname>PostgreSQL</productname> local.
Also, even if the remote server does demand a password,
it is possible for the password to be supplied from the server
- environment, such as a <filename>~/.pgpass</> file belonging to the
+ environment, such as a <filename>~/.pgpass</filename> file belonging to the
server's user. This opens not only a risk of impersonation, but the
possibility of exposing a password to an untrustworthy remote server.
C'est pourquoi,
@@ -174,8 +174,8 @@
<function>dblink_connect_u()</function> peut être accordé à quelque utilisateur
spécifique digne de confiance, mais cela doit se faire
avec une extrême prudence.It is also recommended
- that any <filename>~/.pgpass</> file belonging to the server's user
- <emphasis>not</> contain any records specifying a wildcard host name.
+ that any <filename>~/.pgpass</filename> file belonging to the server's user
+ <emphasis>not</emphasis> contain any records specifying a wildcard host name.
</para>
<para>
Modified: traduc/trunk/postgresql/ddl.xml
===================================================================
--- traduc/trunk/postgresql/ddl.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ddl.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -2099,7 +2099,7 @@
typically only work on individual, physical tables and do no
support recursing over inheritance hierarchies. The respective
behavior of each individual command is documented in the reference
- part (<xref linkend="sql-commands">).
+ part (<xref linkend="sql-commands"/>).
</para>
<para>
@@ -2719,12 +2719,12 @@
<para>
The default (and recommended) setting of
- <xref linkend="guc-constraint-exclusion"> is actually neither
- <literal>on</> nor <literal>off</>, but an intermediate setting
- called <literal>partition</>, which causes the technique to be
+ <xref linkend="guc-constraint-exclusion"/> is actually neither
+ <literal>on</literal> nor <literal>off</literal>, but an intermediate setting
+ called <literal>partition</literal>, which causes the technique to be
applied only to queries that are likely to be working on partitioned
- tables. The <literal>on</> setting causes the planner to examine
- <literal>CHECK</> constraints in all queries, even simple ones that
+ tables. The <literal>on</literal> setting causes the planner to examine
+ <literal>CHECK</literal> constraints in all queries, even simple ones that
are unlikely to benefit.
</para>
</sect2>
Modified: traduc/trunk/postgresql/errcodes.xml
===================================================================
--- traduc/trunk/postgresql/errcodes.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/errcodes.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -311,7 +311,7 @@
<row>
-<entry spanname="span13"><emphasis role="bold">Class 20 — Case Not Found</></entry>
+<entry spanname="span13"><emphasis role="bold">Class 20 — Case Not Found</emphasis></entry>
</row>
<row>
Modified: traduc/trunk/postgresql/extend.xml
===================================================================
--- traduc/trunk/postgresql/extend.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/extend.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -266,12 +266,12 @@
<para>
A variadic function (one taking a variable number of arguments, as in
- <xref linkend="xfunc-sql-variadic-functions">) can be
+ <xref linkend="xfunc-sql-variadic-functions"/>) can be
polymorphic: this is accomplished by declaring its last parameter as
- <literal>VARIADIC</> <type>anyarray</>. For purposes of argument
+ <literal>VARIADIC</literal> <type>anyarray</type>. For purposes of argument
matching and determining the actual result type, such a function behaves
the same as if you had written the appropriate number of
- <type>anynonarray</> parameters.
+ <type>anynonarray</type> parameters.
</para>
</sect2>
</sect1>
Modified: traduc/trunk/postgresql/filelist.xml
===================================================================
--- traduc/trunk/postgresql/filelist.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/filelist.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -96,11 +96,11 @@
<!-- contrib information -->
<!ENTITY contrib SYSTEM "contrib.xml">
<!ENTITY adminpack SYSTEM "adminpack.xml">
-<!entity auto-explain SYSTEM "auto-explain.sgml">
-<!entity btree-gin SYSTEM "btree-gin.sgml">
+<!ENTITY auto-explain SYSTEM "auto-explain.xml">
+<!ENTITY btree-gin SYSTEM "btree-gin.xml">
<!ENTITY btree-gist SYSTEM "btree-gist.xml">
<!ENTITY chkpass SYSTEM "chkpass.xml">
-<!entity citext SYSTEM "citext.sgml">
+<!ENTITY citext SYSTEM "citext.xml">
<!ENTITY cube SYSTEM "cube.xml">
<!ENTITY dblink SYSTEM "dblink.xml">
<!ENTITY dict-int SYSTEM "dict-int.xml">
@@ -121,7 +121,7 @@
<!ENTITY pgfreespacemap SYSTEM "pgfreespacemap.xml">
<!ENTITY pgrowlocks SYSTEM "pgrowlocks.xml">
<!ENTITY pgstandby SYSTEM "pgstandby.xml">
-<!entity pgstatstatements SYSTEM "pgstatstatements.sgml">
+<!ENTITY pgstatstatements SYSTEM "pgstatstatements.xml">
<!ENTITY pgstattuple SYSTEM "pgstattuple.xml">
<!ENTITY pgtrgm SYSTEM "pgtrgm.xml">
<!ENTITY seg SYSTEM "seg.xml">
Modified: traduc/trunk/postgresql/func.xml
===================================================================
--- traduc/trunk/postgresql/func.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/func.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -345,7 +345,7 @@
NULL ou quand tous les champs de la ligne sont NULL alors que
<literal>IS NOT NULL</literal> est vrai quand l'expression même de la ligne est
non NULL et que tous les champs de la ligne sont non NULL.Because of this behavior,
- <literal>IS NULL</> and <literal>IS NOT NULL</> do not always return
+ <literal>IS NULL</literal> and <literal>IS NOT NULL</literal> do not always return
inverse results for row-valued expressions, i.e. a row-valued
expression that contains both NULL and non-null values will return false
for both tests.
@@ -739,9 +739,9 @@
</row>
<row>
- <entry><literal><function>div</function>(<parameter>y</parameter> <type>numeric</>,
- <parameter>x</parameter> <type>numeric</>)</literal></entry>
- <entry><type>numeric</></entry>
+ <entry><literal><function>div</function>(<parameter>y</parameter> <type>numeric</type>,
+ <parameter>x</parameter> <type>numeric</type>)</literal></entry>
+ <entry><type>numeric</type></entry>
<entry>integer quotient of <parameter>y</parameter>/<parameter>x</parameter></entry>
<entry><literal>div(9,4)</literal></entry>
<entry><literal>2</literal></entry>
@@ -1650,7 +1650,7 @@
nécessaires (c'est-à-dire si la chaîne contient des caractères autres
que ceux de l'identifiant ou qu'il peut y avoir un problème de casse).
Les guillemets compris dans la chaîne sont correctement doublés.
- See also <xref linkend="plpgsql-quote-literal-example">.
+ See also <xref linkend="plpgsql-quote-literal-example"/>.
</entry>
<entry><literal>quote_ident('Foo bar')</literal></entry>
<entry><literal>"Foo bar"</literal></entry>
@@ -1666,7 +1666,7 @@
Note that <function>quote_literal</function> returns null on null
input; if the argument might be null,
<function>quote_nullable</function> is often more suitable.
- See also <xref linkend="plpgsql-quote-literal-example">.
+ See also <xref linkend="plpgsql-quote-literal-example"/>.
</entry>
<entry><literal>quote_literal( 'O\'Reilly')</literal></entry>
<entry><literal>'O''Reilly'</literal></entry>
@@ -1703,9 +1703,9 @@
<entry>
Return the given string suitably quoted to be used as a string literal
in an <acronym>SQL</acronym> statement string; or, if the argument
- is null, return <literal>NULL</>.
+ is null, return <literal>NULL</literal>.
Embedded single-quotes and backslashes are properly doubled.
- See also <xref linkend="plpgsql-quote-literal-example">.
+ See also <xref linkend="plpgsql-quote-literal-example"/>.
</entry>
<entry><literal>quote_nullable(NULL)</literal></entry>
<entry><literal>NULL</literal></entry>
@@ -1716,7 +1716,7 @@
<entry><type>text</type></entry>
<entry>
Coerce the given value to text and then quote it as a literal;
- or, if the argument is null, return <literal>NULL</>.
+ or, if the argument is null, return <literal>NULL</literal>.
Embedded single-quotes and backslashes are properly doubled.
</entry>
<entry><literal>quote_nullable(42.5)</literal></entry>
@@ -5354,7 +5354,7 @@
<row>
<entry>préfixe <literal>TM</literal></entry>
<entry>mode de traduction (affiche les noms des jours et mois localisés
- en fonction de <xref linkend="guc-lc-time">)</entry>
+ en fonction de <xref linkend="guc-lc-time"/>)</entry>
<entry><literal>TMMonth</literal></entry>
</row>
<row>
@@ -5477,8 +5477,8 @@
<para>
Attempting to construct a date using a mixture of ISO week and
Gregorian date fields is nonsensical, and will cause an error. In the
- context of an ISO year, the concept of a <quote>month</> or <quote>day
- of month</> has no meaning. In the context of a Gregorian year, the
+ context of an ISO year, the concept of a <quote>month</quote> or <quote>day
+ of month</quote> has no meaning. In the context of a Gregorian year, the
ISO week has no meaning. Users should take care to keep Gregorian and
ISO date specifications separate.
</para>
@@ -5676,7 +5676,7 @@
behavior. For example, <literal>FM9999</literal>
is the <literal>9999</literal> pattern with the
<literal>FM</literal> modifier.
- <xref linkend="functions-formatting-numericmod-table"> shows the
+ <xref linkend="functions-formatting-numericmod-table"/> shows the
modifier patterns for numeric formatting.
</para>
@@ -8753,7 +8753,7 @@
<bar/><foo>abc</foo>
]]></screen>
- Again, see <xref linkend="functions-aggregate"> for additional
+ Again, see <xref linkend="functions-aggregate"/> for additional
information.
</para>
</sect3>
@@ -9894,7 +9894,7 @@
</table>
<para>
- See also <xref linkend="functions-aggregate"> about the aggregate
+ See also <xref linkend="functions-aggregate"/> about the aggregate
function <function>array_agg</function> for use with arrays.
</para>
</sect1>
@@ -10118,7 +10118,7 @@
<entry>
<type>xml</type>
</entry>
- <entry>concatenation of XML values (see also <xref linkend="functions-xml-xmlagg">)</entry>
+ <entry>concatenation of XML values (see also <xref linkend="functions-xml-xmlagg"/>)</entry>
</row>
</tbody>
@@ -10185,7 +10185,7 @@
But this syntax is not allowed in the SQL standard, and is
not portable to other database systems. A future version of
- <productname>PostgreSQL</> might provide an additional feature to control
+ <productname>PostgreSQL</productname> might provide an additional feature to control
the order in a better-defined way (<literal>xmlagg(expr ORDER BY expr, expr,
...)</literal>).
</para>
@@ -10559,22 +10559,23 @@
<para>
<firstterm>Window functions</firstterm> provide the ability to perform
calculations across sets of rows that are related to the current query
- row. See <xref linkend="tutorial-window"> for an introduction to this
+ row. See <xref linkend="tutorial-window"/> for an introduction to this
feature.
</para>
<para>
The built-in window functions are listed in
- <xref linkend="functions-window-table">. Note that these functions
- <emphasis>must</> be invoked using window function syntax; that is an
- <literal>OVER</> clause is required.
+ <xref linkend="functions-window-table"/>. Note that these functions
+ <emphasis>must</emphasis> be invoked using window function syntax; that is an
+ <literal>OVER</literal> clause is required.
</para>
<para>
In addition to these functions, any built-in or user-defined aggregate
function can be used as a window function (see
- <xref linkend="functions-aggregate"> for a list of the built-in aggregates).
- Aggregate functions act as window functions only when an <literal>OVER</>
+ <xref linkend="functions-aggregate"/> for a list of the built-in aggregates).
+ Aggregate functions act as window functions only when an
+<literal>OVER</literal>
clause follows the call; otherwise they act as regular aggregates.
</para>
@@ -10614,7 +10615,8 @@
<entry>
<type>bigint</type>
</entry>
- <entry>rank of the current row with gaps; same as <function>row_number</> of its first peer</entry>
+ <entry>rank of the current row with gaps; same as
+<function>row_number</function> of its first peer</entry>
</row>
<row>
@@ -10640,7 +10642,7 @@
<entry>
<type>double precision</type>
</entry>
- <entry>relative rank of the current row: (<function>rank</> - 1) / (total rows - 1)</entry>
+ <entry>relative rank of the current row: (<function>rank</function> - 1) / (total rows - 1)</entry>
</row>
<row>
@@ -10661,7 +10663,7 @@
<indexterm>
<primary>ntile</primary>
</indexterm>
- <function>ntile(<replaceable class="parameter">num_buckets</replaceable> <type>integer</>)</function>
+ <function>ntile(<replaceable class="parameter">num_buckets</replaceable> <type>integer</type>)</function>
</entry>
<entry>
<type>integer</type>
@@ -10676,9 +10678,9 @@
<primary>lag</primary>
</indexterm>
<function>
- lag(<replaceable class="parameter">value</replaceable> <type>any</>
- [, <replaceable class="parameter">offset</replaceable> <type>integer</>
- [, <replaceable class="parameter">default</replaceable> <type>any</> ]])
+ lag(<replaceable class="parameter">value</replaceable> <type>any</type>
+ [, <replaceable class="parameter">offset</replaceable> <type>integer</type>
+ [, <replaceable class="parameter">default</replaceable> <type>any</type> ]])
</function>
</entry>
<entry>
@@ -10703,9 +10705,9 @@
<primary>lead</primary>
</indexterm>
<function>
- lead(<replaceable class="parameter">value</replaceable> <type>any</>
- [, <replaceable class="parameter">offset</replaceable> <type>integer</>
- [, <replaceable class="parameter">default</replaceable> <type>any</> ]])
+ lead(<replaceable class="parameter">value</replaceable> <type>any</type>
+ [, <replaceable class="parameter">offset</replaceable> <type>integer</type>
+ [, <replaceable class="parameter">default</replaceable> <type>any</type> ]])
</function>
</entry>
<entry>
@@ -10729,7 +10731,8 @@
<indexterm>
<primary>first_value</primary>
</indexterm>
- <function>first_value(<replaceable class="parameter">value</replaceable> <type>any</>)</function>
+ <function>first_value(<replaceable
+class="parameter">value</replaceable> <type>any</type>)</function>
</entry>
<entry>
<type>same type as <replaceable class="parameter">value</replaceable></type>
@@ -10745,7 +10748,7 @@
<indexterm>
<primary>last_value</primary>
</indexterm>
- <function>last_value(<replaceable class="parameter">value</replaceable> <type>any</>)</function>
+ <function>last_value(<replaceable class="parameter">value</replaceable> <type>any</type>)</function>
</entry>
<entry>
<type>same type as <replaceable class="parameter">value</replaceable></type>
@@ -10762,7 +10765,7 @@
<primary>nth_value</primary>
</indexterm>
<function>
- nth_value(<replaceable class="parameter">value</replaceable> <type>any</>, <replaceable class="parameter">nth</replaceable> <type>integer</>)
+ nth_value(<replaceable class="parameter">value</replaceable> <type>any</type>, <replaceable class="parameter">nth</replaceable> <type>integer</type>)
</function>
</entry>
<entry>
@@ -10780,47 +10783,50 @@
<para>
All of the functions listed in
- <xref linkend="functions-window-table"> depend on the sort ordering
- specified by the <literal>ORDER BY</> clause of the associated window
- definition. Rows that are not distinct in the <literal>ORDER BY</>
- ordering are said to be <firstterm>peers</>; the four ranking functions
+ <xref linkend="functions-window-table"/> depend on the sort ordering
+ specified by the <literal>ORDER BY</literal> clause of the associated window
+ definition. Rows that are not distinct in the <literal>ORDER BY</literal>
+ ordering are said to be <firstterm>peers</firstterm>; the four ranking functions
are defined so that they give the same answer for any two peer rows.
</para>
<para>
- Note that <function>first_value</>, <function>last_value</>, and
- <function>nth_value</> consider only the rows within the <quote>window
- frame</>, which by default contains the rows from the start of the
+ Note that <function>first_value</function>, <function>last_value</function>, and
+ <function>nth_value</function> consider only the rows within the <quote>window
+ frame</quote>, which by default contains the rows from the start of the
partition through the last peer of the current row. This is
- likely to give unhelpful results for <function>nth_value</> and
- particularly <function>last_value</>. You can redefine the frame as
+ likely to give unhelpful results for <function>nth_value</function> and
+ particularly <function>last_value</function>. You can redefine the frame as
being the whole partition by adding <literal>ROWS BETWEEN UNBOUNDED
- PRECEDING AND UNBOUNDED FOLLOWING</> to the <literal>OVER</> clause.
- See <xref linkend="syntax-window-functions"> for more information.
+ PRECEDING AND UNBOUNDED FOLLOWING</literal> to the <literal>OVER</literal> clause.
+ See <xref linkend="syntax-window-functions"/> for more information.
</para>
<para>
When an aggregate function is used as a window function, it aggregates
over the rows within the current row's window frame. To obtain
- aggregation over the whole partition, omit <literal>ORDER BY</> or use
- <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</>.
- An aggregate used with <literal>ORDER BY</> and the default window frame
- definition produces a <quote>running sum</> type of behavior, which may or
+ aggregation over the whole partition, omit <literal>ORDER BY</literal> or use
+ <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</literal>.
+ An aggregate used with <literal>ORDER BY</literal> and the default window frame
+ definition produces a <quote>running sum</quote> type of behavior, which may or
may not be what's wanted.
</para>
<note>
<para>
- The SQL standard defines a <literal>RESPECT NULLS</> or
- <literal>IGNORE NULLS</> option for <function>lead</>, <function>lag</>,
- <function>first_value</>, <function>last_value</>, and
- <function>nth_value</>. This is not implemented in
+ The SQL standard defines a <literal>RESPECT NULLS</literal> or
+ <literal>IGNORE NULLS</literal> option for <function>lead</function>,
+ <function>lag</function>,
+ <function>first_value</function>, <function>last_value</function>, and
+ <function>nth_value</function>. This is not implemented in
<productname>PostgreSQL</productname>: the behavior is always the
- same as the standard's default, namely <literal>RESPECT NULLS</>.
- Likewise, the standard's <literal>FROM FIRST</> or <literal>FROM LAST</>
- option for <function>nth_value</> is not implemented: only the
- default <literal>FROM FIRST</> behavior is supported. (You can achieve
- the result of <literal>FROM LAST</> by reversing the <literal>ORDER BY</>
+ same as the standard's default, namely <literal>RESPECT NULLS</literal>.
+ Likewise, the standard's <literal>FROM FIRST</literal> or <literal>FROM
+ LAST</literal>
+ option for <function>nth_value</function> is not implemented: only the
+ default <literal>FROM FIRST</literal> behavior is supported. (You can achieve
+ the result of <literal>FROM LAST</literal> by reversing the <literal>ORDER
+BY</literal>
ordering.)
</para>
</note>
@@ -11424,7 +11430,7 @@
result depends on comparing two NULL values or a NULL and a non-NULL.
<productname>PostgreSQL</productname> does this only when comparing the
results of two row constructors or comparing a row constructor to the
- output of a subquery (as in <xref linkend="functions-subquery">).
+ output of a subquery (as in <xref linkend="functions-subquery"/>).
In other contexts where two composite-type values are compared, two
NULL field values are considered equal, and a NULL is considered larger
than a non-NULL. This is necessary in order to have consistent sorting
@@ -11452,7 +11458,7 @@
ligne. Actuellement, les seules fonctions dans cette classe sont les
fonctions de génération de séries, détaillées dans le <xref
linkend="functions-srf-series"/> and
- <xref linkend="functions-srf-subscripts">.
+ <xref linkend="functions-srf-subscripts"/>.
</para>
<table id="functions-srf-series">
@@ -11491,7 +11497,7 @@
</row>
<row>
- <entry><literal><function>generate_series</function>(<parameter>start</parameter>, <parameter>stop</parameter>, <parameter>step</parameter> <type>interval</>)</literal></entry>
+ <entry><literal><function>generate_series</function>(<parameter>start</parameter>, <parameter>stop</parameter>, <parameter>step</parameter> <type>interval</type>)</literal></entry>
<entry><type>timestamp</type> or <type>timestamp with time zone</type></entry>
<entry><type>setof timestamp</type> or <type>setof timestamp with time zone</type> (same as argument type)</entry>
<entry>
@@ -11602,7 +11608,7 @@
</indexterm>
<para>
- <function>generate_subscripts</> is a convenience function that generates
+ <function>generate_subscripts</function> is a convenience function that generates
the set of valid subscripts for the specified dimension of the given
array.
Zero rows are returned for arrays that do not have the requested dimension,
@@ -12231,13 +12237,14 @@
par le nombre et le type de leurs arguments.) Lors de l'indication par
nom, il est possible de préciser le schéma. Les privilèges possibles,
indiqués sous la forme d'une chaîne de caractères, sont :
- literal>SELECT</literal>, <literal>INSERT</literal>,
- <literal>UPDATE</literal>, <literal>DELETE</literal>, <literal>TRUNCATE</>,
+ <literal>SELECT</literal>, <literal>INSERT</literal>,
+ <literal>UPDATE</literal>, <literal>DELETE</literal>,
+ <literal>TRUNCATE</literal>,
<literal>REFERENCES</literal>, or <literal>TRIGGER</literal>. Optionally,
- <literal>WITH GRANT OPTION</> can be added to a privilege type to test
+ <literal>WITH GRANT OPTION</literal> can be added to a privilege type to test
whether the privilege is held with grant option. Also, multiple privilege
types can be listed separated by commas, in which case the result will
- be <literal>true</> if any of the listed privileges is held.
+ be <literal>true</literal> if any of the listed privileges is held.
(Case of the privilege string is not significant, and extra whitespace
is allowed between but not within privilege names.)
Some examples:
@@ -12250,7 +12257,7 @@
<para>
<function>has_any_column_privilege</function> checks whether a user can
access any column of a table in a particular way. The possibilities for
- its arguments are the same as for <function>has_table_privilege</>,
+ its arguments are the same as for <function>has_table_privilege</function>,
except that the desired access privilege type must evaluate to some
combination of
<literal>SELECT</literal>,
@@ -12259,8 +12266,8 @@
<literal>REFERENCES</literal>. Note that having any of these privileges
at the table level implicitly grants it for each column of the table,
so <function>has_any_column_privilege</function> will always return
- <literal>true</> if <function>has_table_privilege</> does for the same
- arguments. But <function>has_any_column_privilege</> also succeeds if
+ <literal>true</literal> if <function>has_table_privilege</function> does for the same
+ arguments. But <function>has_any_column_privilege</function> also succeeds if
there is a column-level grant of the privilege for at least one column.
</para>
@@ -12295,8 +12302,8 @@
can access a function in a particular way. The possibilities for its
arguments are analogous to <function>has_table_privilege</function>.
When specifying a function by a text string rather than by OID,
- the allowed input is the same as for the <type>regprocedure</> data type
- (see <xref linkend="datatype-oid">).
+ the allowed input is the same as for the <type>regprocedure</type> data type
+ (see <xref linkend="datatype-oid"/>).
The desired access privilege type must evaluate to
<literal>EXECUTE</literal>.
An example is:
@@ -12637,7 +12644,7 @@
<row>
<entry><literal><function>pg_get_function_result</function>(<parameter>func_oid</parameter>)</literal></entry>
<entry><type>text</type></entry>
- <entry>get <literal>RETURNS</> clause for function</entry>
+ <entry>get <literal>RETURNS</literal> clause for function</entry>
</row>
<row>
<entry><literal><function>pg_get_indexdef</function>(<parameter>index_oid</parameter>)</literal></entry>
@@ -12726,11 +12733,12 @@
<para>
<function>pg_get_keywords</function> returns a set of records describing
- the SQL keywords recognized by the server. The <structfield>word</> column
- contains the keyword. The <structfield>catcode</> column contains a
- category code: <literal>U</> for unreserved, <literal>C</> for column name,
- <literal>T</> for type or function name, or <literal>R</> for reserved.
- The <structfield>catdesc</> column contains a possibly-localized string
+ the SQL keywords recognized by the server. The
+ <structfield>word</structfield> column
+ contains the keyword. The <structfield>catcode</structfield> column contains a
+ category code: <literal>U</literal> for unreserved, <literal>C</literal> for column name,
+ <literal>T</literal> for type or function name, or <literal>R</literal> for reserved.
+ The <structfield>catdesc</structfield> column contains a possibly-localized string
describing the category.
</para>
@@ -12756,16 +12764,16 @@
</para>
<para>
- <function>pg_get_functiondef</> returns a complete
- <command>CREATE OR REPLACE FUNCTION</> statement for a function.
+ <function>pg_get_functiondef</function> returns a complete
+ <command>CREATE OR REPLACE FUNCTION</command> statement for a function.
<function>pg_get_function_arguments</function> returns the argument list
of a function, in the form it would need to appear in within
- <command>CREATE FUNCTION</>.
+ <command>CREATE FUNCTION</command>.
<function>pg_get_function_result</function> similarly returns the
- appropriate <literal>RETURNS</> clause for the function.
+ appropriate <literal>RETURNS</literal> clause for the function.
<function>pg_get_function_identity_arguments</function> returns the
argument list necessary to identify a function, in the form it
- would need to appear in within <command>ALTER FUNCTION</>, for
+ would need to appear in within <command>ALTER FUNCTION</command>, for
instance. This form omits default values.
</para>
@@ -12809,8 +12817,8 @@
<function>pg_typeof</function> returns the OID of the data type of the
value that is passed to it. This can be helpful for troubleshooting or
dynamically constructing SQL queries. The function is declared as
- returning <type>regtype</>, which is an OID alias type (see
- <xref linkend="datatype-oid">); this means that it is the same as an
+ returning <type>regtype</type>, which is an OID alias type (see
+ <xref linkend="datatype-oid"/>); this means that it is the same as an
OID for comparison purposes but displays as a type name. For example:
<programlisting>
SELECT pg_typeof(33);
@@ -13035,8 +13043,8 @@
<entry><type>xip_list</type></entry>
<entry>
Active txids at the time of the snapshot. The list
- includes only those active txids between <literal>xmin</>
- and <literal>xmax</>; there might be active txids higher
+ includes only those active txids between <literal>xmin</literal>
+ and <literal>xmax</literal>; there might be active txids higher
than xmax. A txid that is <literal>xmin <= txid <
xmax</literal> and not in this list was already completed
at the time of the snapshot, and thus either visible or
@@ -13196,7 +13204,7 @@
</row>
<row>
<entry>
- <literal><function>pg_terminate_backend</function>(<parameter>pid</parameter> <type>int</>)</literal>
+ <literal><function>pg_terminate_backend</function>(<parameter>pid</parameter> <type>int</type>)</literal>
</entry>
<entry><type>boolean</type></entry>
<entry>Terminate a backend</entry>
@@ -13226,8 +13234,10 @@
</para>
<para>
- <function>pg_cancel_backend</function> and <function>pg_terminate_backend</> envoie un signal
- (respectivement <systemitem>SIGINT</systemitem> or <systemitem>SIGTERM</>) au processus serveur identifié
+ <function>pg_cancel_backend</function> and
+ <function>pg_terminate_backend</function> envoie un signal
+ (respectivement <systemitem>SIGINT</systemitem> or
+ <systemitem>SIGTERM</systemitem>) au processus serveur identifié
par l'ID du processus. L'identifiant du processus serveur actif
peut être trouvé dans la colonne <structfield>procpid</structfield>
dans la vue <structname>pg_stat_activity</structname> ou en listant les
@@ -13298,7 +13308,8 @@
<row>
<entry>
<literal><function>pg_start_backup</function>
- (<parameter>label</parameter> <type>text</type> <optional>, <parameter>fast</> <type>boolean</> </optional>)</literal>
+ (<parameter>label</parameter> <type>text</type> <optional>,
+ <parameter>fast</parameter> <type>boolean</type> </optional>)</literal>
</entry>
<entry><type>text</type></entry>
<entry>Préparation de la sauvegarde à chaud</entry>
@@ -13365,8 +13376,8 @@
-----------------
0/D4445B8
(1 row)</programlisting>
- There is an optional boolean second parameter. If <literal>true</>,
- it specifies executing <function>pg_start_backup</> as quickly as
+ There is an optional boolean second parameter. If <literal>true</literal>,
+ it specifies executing <function>pg_start_backup</function> as quickly as
possible. This forces an immediate checkpoint which will cause a
spike in I/O operations, slowing any concurrently executing queries.
</para>
@@ -13576,7 +13587,7 @@
<literal>'main'</literal> or leaving out the second argument returns the
size of the main data fork of the relation. Specifying
<literal>'fsm'</literal> returns the size of the
- Free Space Map (see <xref linkend="storage-fsm">) associated with the
+ Free Space Map (see <xref linkend="storage-fsm"/>) associated with the
relation.
</para>
@@ -13801,7 +13812,8 @@
<function>pg_advisory_lock</function> verrouille une ressource applicative
qui peut être identifiée soit par une valeur de clé sur 64
bits soit par deux valeurs de clé sur 32 bits (les deux espaces
- de clé ne se surchargent pas). The key type is specified in <literal>pg_locks.objid</>.
+ de clé ne se surchargent pas). The key type is specified in
+<literal>pg_locks.objid</literal>.
Si une autre session détient déjà un verrou
sur la même ressource, la fonction attend que la ressource
devienne disponible. Le verrou est exclusif. Les demandes de verrou
@@ -13879,8 +13891,8 @@
</indexterm>
<para>
- Currently <productname>PostgreSQL</> provides one built in trigger
- function, <function>suppress_redundant_updates_trigger</>,
+ Currently <productname>PostgreSQL</productname> provides one built in trigger
+ function, <function>suppress_redundant_updates_trigger</function>,
which will prevent any update
that does not actually change the data in the row from taking place, in
contrast to the normal behaviour which always performs the update
@@ -13897,7 +13909,7 @@
However, detecting such situations in client code is not
always easy, or even possible, and writing expressions to detect
them can be error-prone. An alternative is to use
- <function>suppress_redundant_updates_trigger</>, which will skip
+ <function>suppress_redundant_updates_trigger</function>, which will skip
updates that don't change the data. You should use this with care,
however. The trigger takes a small but non-trivial time for each record,
so if most of the records affected by an update are actually changed,
@@ -13905,7 +13917,7 @@
</para>
<para>
- The <function>suppress_redundant_updates_trigger</> function can be
+ The <function>suppress_redundant_updates_trigger</function> function can be
added to a table like this:
<programlisting>
CREATE TRIGGER z_min_update
@@ -13919,7 +13931,7 @@
</para>
<para>
For more information about creating triggers, see
- <xref linkend="SQL-CREATETRIGGER">.
+ <xref linkend="sql-createtrigger"/>.
</para>
</sect1>
</chapter>
Modified: traduc/trunk/postgresql/fuzzystrmatch.xml
===================================================================
--- traduc/trunk/postgresql/fuzzystrmatch.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/fuzzystrmatch.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -18,7 +18,7 @@
<caution>
<para>
- At present, <filename>fuzzystrmatch</> does not work well with
+ At present, <filename>fuzzystrmatch</filename> does not work well with
multi-byte encodings (such as UTF-8).
</para>
</caution>
Modified: traduc/trunk/postgresql/gin.xml
===================================================================
--- traduc/trunk/postgresql/gin.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/gin.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -113,33 +113,33 @@
<literal>query</literal> et les valeurs de clés à extraire.
Le nombre de clés renvoyées doit être stocké dans
<literal>*nkeys</literal>.
- If the query contains no keys then <function>extractQuery</>
- should store 0 or -1 into <literal>*nkeys</>, depending on the
+ If the query contains no keys then <function>extractQuery</function>
+ should store 0 or -1 into <literal>*nkeys</literal>, depending on the
semantics of the operator. 0 means that every
- value matches the <literal>query</> and a full-index scan should be
- performed (but see <xref linkend="gin-limit">).
- -1 means that nothing can match the <literal>query</>, and
+ value matches the <literal>query</literal> and a full-index scan should be
+ performed (but see <xref linkend="gin-limit"/>).
+ -1 means that nothing can match the <literal>query</literal>, and
so the index scan can be skipped entirely.
- <literal>pmatch</> is an output argument for use when partial match
- is supported. To use it, <function>extractQuery</> must allocate
- an array of <literal>*nkeys</> booleans and store its address at
- <literal>*pmatch</>. Each element of the array should be set to TRUE
+ <literal>pmatch</literal> is an output argument for use when partial match
+ is supported. To use it, <function>extractQuery</function> must allocate
+ an array of <literal>*nkeys</literal> booleans and store its address at
+ <literal>*pmatch</literal>. Each element of the array should be set to TRUE
if the corresponding key requires partial match, FALSE if not.
- If <literal>*pmatch</> is set to NULL then GIN assumes partial match
+ If <literal>*pmatch</literal> is set to NULL then GIN assumes partial match
is not required. The variable is initialized to NULL before call,
so this argument can simply be ignored by operator classes that do
not support partial match.
- <literal>extra_data</> is an output argument that allows
- <function>extractQuery</> to pass additional data to the
- <function>consistent</> and <function>comparePartial</> methods.
- To use it, <function>extractQuery</> must allocate
- an array of <literal>*nkeys</> Pointers and store its address at
- <literal>*extra_data</>, then store whatever it wants to into the
+ <literal>extra_data</literal> is an output argument that allows
+ <function>extractQuery</function> to pass additional data to the
+ <function>consistent</function> and <function>comparePartial</function> methods.
+ To use it, <function>extractQuery</function> must allocate
+ an array of <literal>*nkeys</literal> Pointers and store its address at
+ <literal>*extra_data</literal>, then store whatever it wants to into the
individual pointers. The variable is initialized to NULL before
call, so this argument can simply be ignored by operator classes that
- do not require extra data. If <literal>*extra_data</> is set, the
- whole array is passed to the <function>consistent</> method, and
- the appropriate element to the <function>comparePartial</> method.
+ do not require extra data. If <literal>*extra_data</literal> is set, the
+ whole array is passed to the <function>consistent</function> method, and
+ the appropriate element to the <function>comparePartial</function> method.
</para>
</listitem>
</varlistentry>
@@ -150,10 +150,11 @@
<listitem>
<para>
Returns TRUE if the indexed value satisfies the query operator with
- strategy number <literal>n</> (or might satisfy, if the recheck
- indication is returned). The <literal>check</> array has length
- <literal>nkeys</>, which is the same as the number of keys previously
- returned by <function>extractQuery</> for this <literal>query</> datum.
+ strategy number <literal>n</literal> (or might satisfy, if the recheck
+ indication is returned). The <literal>check</literal> array has length
+ <literal>nkeys</literal>, which is the same as the number of keys previously
+ returned by <function>extractQuery</function> for this
+ <literal>query</literal> datum.
Chaque élément du tableau <literal>check</literal> est
TRUE si la valeur indexée contient la clé correspondante de la requête,
c'est-à-dire que si (check[i] == TRUE), la i-ème clé du tableau résultant
@@ -161,9 +162,9 @@
Le datum <literal>query</literal> d'origine (pas le tableau de clés
extrait !) est passé au cas où la méthode
<function>consistent</function> a besoin de le consulter.
- <literal>extra_data</> is the extra-data array returned by
- <function>extractQuery</>, or NULL if none.
- On success, <literal>*recheck</> should be set to TRUE if the heap
+ <literal>extra_data</literal> is the extra-data array returned by
+ <function>extractQuery</function>, or NULL if none.
+ On success, <literal>*recheck</literal> should be set to TRUE if the heap
tuple needs to be rechecked against the query operator, or FALSE if
the index test is exact.
</para>
@@ -190,11 +191,11 @@
does not match the query, but the index scan should continue; zero
means that the index key does match the query; greater than zero
indicates that the index scan should stop because no more matches
- are possible. The strategy number <literal>n</> of the operator
+ are possible. The strategy number <literal>n</literal> of the operator
that generated the partial match query is provided, in case its
semantics are needed to determine when to end the scan. Also,
- <literal>extra_data</> is the corresponding element of the extra-data
- array made by <function>extractQuery</>, or NULL if none.
+ <literal>extra_data</literal> is the corresponding element of the extra-data
+ array made by <function>extractQuery</function>, or NULL if none.
</para>
</listitem>
</varlistentry>
@@ -202,11 +203,12 @@
</variablelist>
<para>
- To support <quote>partial match</> queries, an operator class must
- provide the <function>comparePartial</> method, and its
- <function>extractQuery</> method must set the <literal>pmatch</>
+ To support <quote>partial match</quote> queries, an operator class must
+ provide the <function>comparePartial</function> method, and its
+ <function>extractQuery</function> method must set the
+ <literal>pmatch</literal>
parameter when a partial-match query is encountered. See
- <xref linkend="gin-partial-match"> for details.
+ <xref linkend="gin-partial-match"/> for details.
</para>
</sect1>
@@ -229,10 +231,10 @@
intrinsic nature of inverted indexes: inserting or updating one heap row
can cause many inserts into the index (one for each key extracted
from the indexed value). As of <productname>PostgreSQL</productname> 8.4,
- <acronym>GIN</> is capable of postponing much of this work by inserting
+ <acronym>GIN</acronym> is capable of postponing much of this work by inserting
new tuples into a temporary, unsorted list of pending entries.
When the table is vacuumed, or if the pending list becomes too large
- (larger than <xref linkend="guc-work-mem">), the entries are moved to the
+ (larger than <xref linkend="guc-work-mem"/>), the entries are moved to the
main <acronym>GIN</acronym> data structure using the same bulk insert
techniques used during initial index creation. This greatly improves
<acronym>GIN</acronym> index update speed, even counting the additional
@@ -245,7 +247,7 @@
of pending entries in addition to searching the regular index, and so
a large list of pending entries will slow searches significantly.
Another disadvantage is that, while most updates are fast, an update
- that causes the pending list to become <quote>too large</> will incur an
+ that causes the pending list to become <quote>too large</quote> will incur an
immediate cleanup cycle and thus be much slower than other updates.
Proper use of autovacuum can minimize both of these problems.
</para>
@@ -255,7 +257,7 @@
use of pending entries can be disabled by turning off the
<literal>FASTUPDATE</literal> storage parameter for a
<acronym>GIN</acronym> index. See <xref linkend="sql-createindex"
- endterm="sql-createindex-title"> for details.
+ endterm="sql-createindex-title"/> for details.
</para>
</sect2>
@@ -263,15 +265,15 @@
<title>Partial match algorithm</title>
<para>
- GIN can support <quote>partial match</> queries, in which the query
+ GIN can support <quote>partial match</quote> queries, in which the query
does not determine an exact match for one or more keys, but the possible
matches fall within a reasonably narrow range of key values (within the
- key sorting order determined by the <function>compare</> support method).
- The <function>extractQuery</> method, instead of returning a key value
+ key sorting order determined by the <function>compare</function> support method).
+ The <function>extractQuery</function> method, instead of returning a key value
to be matched exactly, returns a key value that is the lower bound of
- the range to be searched, and sets the <literal>pmatch</> flag true.
- The key range is then searched using the <function>comparePartial</>
- method. <function>comparePartial</> must return zero for an actual
+ the range to be searched, and sets the <literal>pmatch</literal> flag true.
+ The key range is then searched using the <function>comparePartial</function>
+ method. <function>comparePartial</function> must return zero for an actual
match, less than zero for a non-match that is still within the range
to be searched, or greater than zero if the index key is past the range
that could match.
@@ -298,7 +300,7 @@
<para>
As of <productname>PostgreSQL</productname> 8.4, this advice is less
necessary since delayed indexing is used (see <xref
- linkend="gin-fast-update"> for details). But for very large updates
+ linkend="gin-fast-update"/> for details). But for very large updates
it may still be best to drop and recreate the index.
</para>
</listitem>
@@ -317,17 +319,17 @@
</varlistentry>
<varlistentry>
- <term><xref linkend="guc-work-mem"></term>
+ <term><xref linkend="guc-work-mem"/></term>
<listitem>
<para>
During a series of insertions into an existing <acronym>GIN</acronym>
- index that has <literal>FASTUPDATE</> enabled, the system will clean up
+ index that has <literal>FASTUPDATE</literal> enabled, the system will clean up
the pending-entry list whenever it grows larger than
- <varname>work_mem</>. To avoid fluctuations in observed response time,
+ <varname>work_mem</varname>. To avoid fluctuations in observed response time,
it's desirable to have pending-list cleanup occur in the background
(i.e., via autovacuum). Foreground cleanup operations can be avoided by
- increasing <varname>work_mem</> or making autovacuum more aggressive.
- However, enlarging <varname>work_mem</> means that if a foreground
+ increasing <varname>work_mem</varname> or making autovacuum more aggressive.
+ However, enlarging <varname>work_mem</varname> means that if a foreground
cleanup does occur, it will take even longer.
</para>
</listitem>
@@ -373,7 +375,7 @@
<para>
<acronym>GIN</acronym> doesn't support full index scans. The reason for
- this is that <function>extractValue</> is allowed to return zero keys,
+ this is that <function>extractValue</function> is allowed to return zero keys,
as for example might happen with an empty string or empty array. In such
a case the indexed value will be unrepresented in the index. It is
therefore impossible for <acronym>GIN</acronym> to guarantee that a
@@ -382,25 +384,25 @@
<para>
Because of this limitation, when <function>extractQuery</function> returns
- <literal>nkeys = 0</> to indicate that all values match the query,
+ <literal>nkeys = 0</literal> to indicate that all values match the query,
<acronym>GIN</acronym> will emit an error. (If there are multiple ANDed
indexable operators in the query, this happens only if they all return zero
- for <literal>nkeys</>.)
+ for <literal>nkeys</literal>.)
</para>
<para>
It is possible for an operator class to circumvent the restriction against
- full index scan. To do that, <function>extractValue</> must return at least
+ full index scan. To do that, <function>extractValue</function> must return at least
one (possibly dummy) key for every indexed value, and
<function>extractQuery</function> must convert an unrestricted search into
a partial-match query that will scan the whole index. This is inefficient
but might be necessary to avoid corner-case failures with operators such
- as <literal>LIKE</> or subset inclusion.
+ as <literal>LIKE</literal> or subset inclusion.
</para>
<para>
<acronym>GIN</acronym> assumes that indexable operators are strict.
- This means that <function>extractValue</> will not be called at all on
+ This means that <function>extractValue</function> will not be called at all on
a NULL value (so the value will go unindexed), and
<function>extractQuery</function> will not be called on a NULL comparison
value either (instead, the query is presumed to be unmatchable).
@@ -421,7 +423,7 @@
des classes d'opérateur <acronym>GIN</acronym> pour <type>tsvector</type> et
pour les tableaux unidimensionnel de tous
les types internes. Prefix searching in
- <type>tsvector</> is implemented using the <acronym>GIN</> partial match
+ <type>tsvector</type> is implemented using the <acronym>GIN</acronym> partial match
feature. Les modules <filename>contrib</filename> suivants
contiennent aussi des classes d'opérateurs <acronym>GIN</acronym> :
</para>
Modified: traduc/trunk/postgresql/gist.xml
===================================================================
--- traduc/trunk/postgresql/gist.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/gist.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -121,9 +121,9 @@
faux si <literal>p</literal> et <literal>q</literal> ne peuvent pas
être simultanément vrais pour un élément de
données particulier. For a true result, a
- <literal>recheck</> flag must also be returned; this indicates whether
- the predicate implies the query (<literal>recheck</> = false) or
- not (<literal>recheck</> = true).
+ <literal>recheck</literal> flag must also be returned; this indicates whether
+ the predicate implies the query (<literal>recheck</literal> = false) or
+ not (<literal>recheck</literal> = true).
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/indexam.xml
===================================================================
--- traduc/trunk/postgresql/indexam.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/indexam.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -253,8 +253,8 @@
<para>
As of <productname>PostgreSQL</productname> 8.4,
- <function>amvacuumcleanup</> will also be called at completion of an
- <command>ANALYZE</> operation. In this case <literal>stats</> is always
+ <function>amvacuumcleanup</function> will also be called at completion of an
+ <command>ANALYZE</command> operation. In this case <literal>stats</literal> is always
NULL and any return value will be ignored. This case can be distinguished
by checking <literal>info->analyze_only</literal>. It is recommended
that the access method do nothing except post-insert cleanup in such a
@@ -311,8 +311,8 @@
(<foreignphrase>qualifier</foreignphrase>) ou <firstterm>clé de
parcours</firstterm> (<foreignphrase>scan key</foreignphrase>). La sémantique
du parcours d'index est décrite plus complètement dans <xref linkend="index-scanning"/>,
- ci-dessous. An index access method can support <quote>plain</> index scans,
- <quote>bitmap</> index scans, or both. Les fonctions liées au parcours qu'une méthode d'accès à
+ ci-dessous. An index access method can support <quote>plain</quote> index scans,
+ <quote>bitmap</quote> index scans, or both. Les fonctions liées au parcours qu'une méthode d'accès à
l'index doit ou devrait fournir sont :
</para>
@@ -344,21 +344,22 @@
<literal>scan</literal>. <quote>success</quote> signifie uniquement que
l'index contient une entrée qui correspond aux clés de parcours, pas que
la ligne existe toujours dans la pile ou qu'elle peut réussir le test
- d'instantané de l'appelant.On success, <function>amgettuple</>
- must also set <literal>scan->xs_recheck</> to TRUE or FALSE.
+ d'instantané de l'appelant.On success, <function>amgettuple</function>
+ must also set <literal>scan->xs_recheck</literal> to TRUE or FALSE.
FALSE means it is certain that the index entry matches the scan keys.
TRUE means this is not certain, and the conditions represented by the
scan keys must be rechecked against the heap tuple after fetching it.
- This provision supports <quote>lossy</> index operators.
+ This provision supports <quote>lossy</quote> index operators.
Note that rechecking will extend only to the scan conditions; a partial
- index predicate (if any) is never rechecked by <function>amgettuple</>
- callers.
+ index predicate (if any) is never rechecked by
+ <function>amgettuple</function> callers.
</para>
<para>
- The <function>amgettuple</> function need only be provided if the access
- method supports <quote>plain</> index scans. If it doesn't, the
- <structfield>amgettuple</> field in its <structname>pg_am</> row must
+ The <function>amgettuple</function> function need only be provided if the access
+ method supports <quote>plain</quote> index scans. If it doesn't, the
+ <structfield>amgettuple</structfield> field in its
+ <structname>pg_am</structname> row must
be set to zero.
</para>
@@ -372,24 +373,25 @@
TIDBitmap (that is, OR the set of tuple IDs into whatever set is already
in the bitmap). The number of tuples fetched is returned (this might be
just an approximate count, for instance some AMs do not detect duplicates).
- While inserting tuple IDs into the bitmap, <function>amgetbitmap</> can
+ While inserting tuple IDs into the bitmap, <function>amgetbitmap</function> can
indicate that rechecking of the scan conditions is required for specific
- tuple IDs. This is analogous to the <literal>xs_recheck</> output parameter
- of <function>amgettuple</>. Note: in the current implementation, support
+ tuple IDs. This is analogous to the <literal>xs_recheck</literal> output parameter
+ of <function>amgettuple</function>. Note: in the current implementation, support
for this feature is conflated with support for lossy storage of the bitmap
itself, and therefore callers recheck both the scan conditions and the
partial index predicate (if any) for recheckable tuples. That might not
always be true, however.
- <function>amgetbitmap</> and
- <function>amgettuple</> cannot be used in the same index scan; there
- are other restrictions too when using <function>amgetbitmap</>, as explained
- in <xref linkend="index-scanning">.
+ <function>amgetbitmap</function> and
+ <function>amgettuple</function> cannot be used in the same index scan; there
+ are other restrictions too when using <function>amgetbitmap</function>, as explained
+ in <xref linkend="index-scanning"/>.
</para>
<para>
- The <function>amgetbitmap</> function need only be provided if the access
- method supports <quote>bitmap</> index scans. If it doesn't, the
- <structfield>amgetbitmap</> field in its <structname>pg_am</> row must
+ The <function>amgetbitmap</function> function need only be provided if the access
+ method supports <quote>bitmap</quote> index scans. If it doesn't, the
+ <structfield>amgetbitmap</structfield> field in its
+ <structname>pg_am</structname> row must
be set to zero.
</para>
@@ -528,18 +530,19 @@
le premier appel, <function>amgettuple</function>
doit être préparé pour continuer le parcours dans la direction adaptée à partir de
l'entrée la plus récemment renvoyée.(But if
- <structname>pg_am</>.<structfield>amcanbackward</> is false, all subsequent
+ <structname>pg_am</structname>.<structfield>amcanbackward</structfield> is false, all subsequent
calls will have the same direction as the first one.)
</para>
<para>
- Access methods that support ordered scans must support <quote>marking</> a
+ Access methods that support ordered scans must support
+ <quote>marking</quote> a
position in a scan and later returning to the marked position. The same
position might be restored multiple times. However, only one position need
- be remembered per scan; a new <function>ammarkpos</> call overrides the
+ be remembered per scan; a new <function>ammarkpos</function> call overrides the
previously marked position. An access method that does not support
ordered scans should still provide mark and restore functions in
- <structname>pg_am</>, but it is sufficient to have them throw errors if
+ <structname>pg_am</structname>, but it is sufficient to have them throw errors if
called.
</para>
@@ -569,8 +572,8 @@
<function>amgetbitmap</function> returns all
tuples at once and marking or restoring scan positions isn't
supported. Secondly, the tuples are returned in a bitmap which doesn't
- have any specific ordering, which is why <function>amgetbitmap</> doesn't
- take a <literal>direction</> argument. Enfin,
+ have any specific ordering, which is why <function>amgetbitmap</function> doesn't
+ take a <literal>direction</literal> argument. Enfin,
<function>amgetmulti</function> ne garantit pas le verrouillage
des lignes renvoyées, avec les implications précisées dans <xref
linkend="index-locking"/>.
@@ -578,7 +581,7 @@
<para>
Note that it is permitted for an access method to implement only
- <function>amgetbitmap</> and not <function>amgettuple</>, or vice versa,
+ <function>amgetbitmap</function> and not <function>amgettuple</function>, or vice versa,
if its internal implementation is unsuited to one API or the other.
</para>
Modified: traduc/trunk/postgresql/indices.xml
===================================================================
--- traduc/trunk/postgresql/indices.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/indices.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -930,8 +930,8 @@
comme ceci :
<programlisting>CREATE INDEX test_index ON test_table (col varchar_pattern_ops);</programlisting>
Il faut créer un index avec la classe d'opérateurs par
- défaut pour que les requêtes qui utilisent une comparaison <literal><</>,
- <literal><=</>, <literal>></> ou <literal>>=</>
+ défaut pour que les requêtes qui utilisent une comparaison <literal><</literal>,
+ <literal><=</literal>, <literal>></literal> ou <literal>>=</literal>
ordinaire utilisent un index. De telles requêtes ne peuvent pas utiliser
les classes d'opérateurs
<literal><replaceable>xxx</replaceable>_pattern_ops</literal>.
Modified: traduc/trunk/postgresql/install-win32.xml
===================================================================
--- traduc/trunk/postgresql/install-win32.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/install-win32.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -39,7 +39,7 @@
La construction par <productname>MinGW</productname> ou
<productname>Cygwin</productname> utilise le système habituel de construction,
voir <xref linkend="installation"/> et les notes spécifiques dans <xref
- linkend="installation-notes-mingw"> et <xref linkend="installation-notes-cygwin">.
+ linkend="installation-notes-mingw"/> et <xref linkend="installation-notes-cygwin"/>.
<productname>Cygwin</productname> n'est pas recommandé, et devrait
seulement être utilisé pour les anciennes versions de
<productname>Windows</productname> où la construction native ne fonctionne
Modified: traduc/trunk/postgresql/installation.xml
===================================================================
--- traduc/trunk/postgresql/installation.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/installation.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -96,7 +96,7 @@
<application>tar</application> est requis pour déballer la distribution
des sources, associé à <application>gzip</application> ou
<application>bzip2</application>. In
- addition, <application>gzip</> is required to install the
+ addition, <application>gzip</application> is required to install the
documentation.
</para>
</listitem>
@@ -619,36 +619,36 @@
</varlistentry>
<varlistentry>
- <term><option>--datarootdir=<replaceable>DIRECTORY</></option></term>
+ <term><option>--datarootdir=<replaceable>DIRECTORY</replaceable></option></term>
<listitem>
<para>
Sets the root directory for various types of read-only data
files. This only sets the default for some of the following
options. The default is
- <filename><replaceable>PREFIX</>/share</>.
+ <filename><replaceable>PREFIX</replaceable>/share</filename>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--datadir=<replaceable>DIRECTORY</></option></term>
+ <term><option>--datadir=<replaceable>DIRECTORY</replaceable></option></term>
<listitem>
<para>
Sets the directory for read-only data files used by the
installed programs. The default is
- <filename><replaceable>DATAROOTDIR</></>. Note that this has
+ <filename><replaceable>DATAROOTDIR</replaceable></filename>. Note that this has
nothing to do with where your database files will be placed.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--localedir=<replaceable>DIRECTORY</></option></term>
+ <term><option>--localedir=<replaceable>DIRECTORY</replaceable></option></term>
<listitem>
<para>
Sets the directory for installing locale data, in particular
message translation catalog files. The default is
- <filename><replaceable>DATAROOTDIR</>/locale</>.
+ <filename><replaceable>DATAROOTDIR</replaceable>/locale</filename>.
</para>
</listitem>
</varlistentry>
@@ -670,21 +670,21 @@
<listitem>
<para>
Sets the root directory for installing documentation files,
- except <quote>man</> pages. This only sets the default for
+ except <quote>man</quote> pages. This only sets the default for
the following options. The default value for this option is
- <filename><replaceable>DATAROOTDIR</>/doc/postgresql</>.
+ <filename><replaceable>DATAROOTDIR</replaceable>/doc/postgresql</filename>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--htmldir=<replaceable>DIRECTORY</></option></term>
+ <term><option>--htmldir=<replaceable>DIRECTORY</replaceable></option></term>
<listitem>
<para>
The HTML-formatted documentation for
<productname>PostgreSQL</productname> will be installed under
this directory. The default is
- <filename><replaceable>DATAROOTDIR</></>.
+ <filename><replaceable>DATAROOTDIR</replaceable></filename>.
</para>
</listitem>
</varlistentry>
@@ -1028,8 +1028,8 @@
this option can be used when no such type is available, or
for compatibility with applications written for prior
versions of <productname>PostgreSQL</productname>. See
- <![%standalone-include[the documentation about datetime datatypes]]>
- <![%standalone-ignore[<xref linkend="datatype-datetime">]]>
+ <phrase>the documentation about datetime datatypes</phrase>
+ <phrase><xref linkend="datatype-datetime"/></phrase>
for more information.
</para>
</listitem>
@@ -1039,13 +1039,13 @@
<term><option>--disable-float4-byval</option></term>
<listitem>
<para>
- Disable passing float4 values <quote>by value</>, causing them
- to be passed <quote>by reference</> instead. This option costs
+ Disable passing float4 values <quote>by value</quote>, causing them
+ to be passed <quote>by reference</quote> instead. This option costs
performance, but may be needed for compatibility with old
user-defined functions that are written in C and use the
- <quote>version 0</> calling convention. A better long-term
+ <quote>version 0</quote> calling convention. A better long-term
solution is to update any such functions to use the
- <quote>version 1</> calling convention.
+ <quote>version 1</quote> calling convention.
</para>
</listitem>
</varlistentry>
@@ -1054,17 +1054,17 @@
<term><option>--disable-float8-byval</option></term>
<listitem>
<para>
- Disable passing float8 values <quote>by value</>, causing them
- to be passed <quote>by reference</> instead. This option costs
+ Disable passing float8 values <quote>by value</quote>, causing them
+ to be passed <quote>by reference</quote> instead. This option costs
performance, but may be needed for compatibility with old
user-defined functions that are written in C and use the
- <quote>version 0</> calling convention. A better long-term
+ <quote>version 0</quote> calling convention. A better long-term
solution is to update any such functions to use the
- <quote>version 1</> calling convention.
+ <quote>version 1</quote> calling convention.
Note that this option affects not only float8, but also int8 and some
related types such as timestamp.
- On 32-bit platforms, <option>--disable-float8-byval</> is the default
- and it is not allowed to select <option>--enable-float8-byval</>.
+ On 32-bit platforms, <option>--disable-float8-byval</option> is the default
+ and it is not allowed to select <option>--enable-float8-byval</option>.
</para>
</listitem>
</varlistentry>
@@ -1073,17 +1073,17 @@
<term><option>--with-segsize=<replaceable>SEGSIZE</replaceable></option></term>
<listitem>
<para>
- Set the <firstterm>segment size</>, in gigabytes. Large tables are
+ Set the <firstterm>segment size</firstterm>, in gigabytes. Large tables are
divided into multiple operating-system files, each of size equal
to the segment size. This avoids problems with file size limits
that exist on many platforms. The default segment size, 1 gigabyte,
is safe on all supported platforms. If your operating system has
- <quote>largefile</> support (which most do, nowadays), you can use
+ <quote>largefile</quote> support (which most do, nowadays), you can use
a larger segment size. This can be helpful to reduce the number of
file descriptors consumed when working with very large tables.
But be careful not to select a value larger than is supported
by your platform and the filesystem(s) you intend to use. Other
- tools you might wish to use, such as <application>tar</>, could
+ tools you might wish to use, such as <application>tar</application>, could
also set limits on the usable file size.
It is recommended, though not absolutely required, that this value
be a power of 2.
@@ -1096,7 +1096,7 @@
<term><option>--with-blocksize=<replaceable>BLOCKSIZE</replaceable></option></term>
<listitem>
<para>
- Set the <firstterm>block size</>, in kilobytes. This is the unit
+ Set the <firstterm>block size</firstterm>, in kilobytes. This is the unit
of storage and I/O within tables. The default, 8 kilobytes,
is suitable for most situations; but other values may be useful
in special cases.
@@ -1110,7 +1110,7 @@
<term><option>--with-wal-segsize=<replaceable>SEGSIZE</replaceable></option></term>
<listitem>
<para>
- Set the <firstterm>WAL segment size</>, in megabytes. This is
+ Set the <firstterm>WAL segment size</firstterm>, in megabytes. This is
the size of each individual file in the WAL log. It may be useful
to adjust this size to control the granularity of WAL log shipping.
The default size is 16 megabytes.
@@ -1124,7 +1124,7 @@
<term><option>--with-wal-blocksize=<replaceable>BLOCKSIZE</replaceable></option></term>
<listitem>
<para>
- Set the <firstterm>WAL block size</>, in kilobytes. This is the unit
+ Set the <firstterm>WAL block size</firstterm>, in kilobytes. This is the unit
of storage and I/O within the WAL log. The default, 8 kilobytes,
is suitable for most situations; but other values may be useful
in special cases.
@@ -1249,8 +1249,8 @@
code coverage testing instrumentation. When run, they
generate files in the build directory with code coverage
metrics.
- <![%standalone-ignore[See <xref linkend="regress-coverage">
- for more information.]]> This option is for use only with GCC
+ <phrase>See <xref linkend="regress-coverage"/>
+ for more information.</phrase> This option is for use only with GCC
and when doing development work.
</para>
</listitem>
@@ -1310,8 +1310,8 @@
</indexterm>
Compile <productname>PostgreSQL</productname> avec le support de l'outil
de trace dynamique, DTrace.
- <![%standalone-ignore[See <xref linkend="dynamic-trace">
- for more information.]]>
+ <phrase>See <xref linkend="dynamic-trace"/>
+ for more information.</phrase>
</para>
<para>
@@ -1981,7 +1981,7 @@
Unix peuvent aussi fonctionner mais n'ont pas été récemment testés. Dans
la plupart des cas, toutes les architectures processeurs supportées par
une système d'exploitation données fonctionneront. Cherchez dans le
- répertoire <xref linkend="installation-platform-notes"> below to see if
+ répertoire <xref linkend="installation-platform-notes"/> below to see if
there is information spécifique à votre système d'exploitation,
tout particulièrement dans le cas d'un vieux système.
</para>
@@ -2004,10 +2004,10 @@
This section documents additional platform-specific issues
regarding the installation and setup of PostgreSQL. Be sure to
read the installation instructions, and in
- particular <xref linkend="install-requirements"> as well. Also,
- check <![%standalone-include[the
- file <filename>src/test/regress/README</> and the documentation]]>
- <![%standalone-ignore[<xref linkend="regress">]]> regarding the
+ particular <xref linkend="install-requirements"/> as well. Also,
+ check <phrase>the
+ file <filename>src/test/regress/README</filename> and the documentation</phrase>
+ <phrase><xref linkend="regress"/></phrase> regarding the
interpretation of regression test results.
</para>
@@ -2193,7 +2193,8 @@
<command>xlc</command> might differ.) If you omit the export of
<envar>OBJECT_MODE</envar>, your build may fail with linker errors. When
<envar>OBJECT_MODE</envar> is set, it tells AIX's build utilities
- such as <command>ar</>, <command>as</>, and <command>ld</> what
+ such as <command>ar</command>, <command>as</command>, and
+ <command>ld</command> what
type of objects to default to handling.
</para>
@@ -2323,7 +2324,7 @@
<para>
PostgreSQL can be built using Cygwin, a Linux-like environment for
Windows, but that method is inferior to the native Windows build
- <![%standalone-ignore[(see <xref linkend="install-win32">)]]> and
+ <phrase>(see <xref linkend="install-win32"/>)</phrase> and
is no longer recommended.
</para>
@@ -2523,8 +2524,9 @@
problems trying to build with GCC. It is a known GCC bug (not
fixed as of version 3.0) related to using functions that return
certain kinds of structures. This bug affects functions like
- <function>inet_ntoa</>, <function>inet_lnaof</>, <function>inet_netof</>, <function>inet_makeaddr</>,
- and <function>semctl</>. It is supposed to be fixed by forcing
+ <function>inet_ntoa</function>, <function>inet_lnaof</function>,
+ <function>inet_netof</function>, <function>inet_makeaddr</function>,
+ and <function>semctl</function>. It is supposed to be fixed by forcing
code to link those functions with libgcc, but this has not been
tested yet.
</para>
@@ -2547,8 +2549,8 @@
Some versions include TCP definitions
in <filename>sys/xti.h</filename>, so it is necessary to
add <literal>#include <sys/xti.h></literal>
- in <filename>src/backend/libpq/pqcomm.c</> and in
- <filename>src/interfaces/libpq/fe-connect.c</>. If you encounter
+ in <filename>src/backend/libpq/pqcomm.c</filename> and in
+ <filename>src/interfaces/libpq/fe-connect.c</filename>. If you encounter
this, please let us know so we can develop a proper fix.
</para>
@@ -2573,8 +2575,8 @@
Microsoft's <productname>Visual C++</productname> compiler suite.
The MinGW build variant uses the normal build system described in
this chapter; the Visual C++ build works completely differently
- and is described in <![%standalone-include[the
- documentation]]><![%standalone-ignore[<xref linkend="install-win32">]]>.
+ and is described in <phrase>the
+ documentation</phrase><phrase><xref linkend="install-win32"/></phrase>.
There is also a precompiled binary installer which you can find at
from <ulink url="http://pgfoundry.org/projects/pginstaller"></ulink>.
It is a fully native build and uses no additional software like
@@ -2681,8 +2683,8 @@
</para>
<para>
- By default, Readline installs into <filename>/usr/local/lib</> and
- <filename>/usr/local/include</>. However, the
+ By default, Readline installs into <filename>/usr/local/lib</filename> and
+ <filename>/usr/local/include</filename>. However, the
PostgreSQL <command>configure</command> program will not find it
there without help. If you installed Readline, then use the
following options to <command>configure</command>:
@@ -2757,7 +2759,7 @@
on <emphasis>all</emphasis> libpq-using programs. libpq
uses <function>pthread_*</function> calls, which are only
available with the
- <option>-Kpthread</>/<option>-Kthread</> flag.
+ <option>-Kpthread</option>/<option>-Kthread</option> flag.
</para>
</sect3>
</sect2>
@@ -2848,8 +2850,8 @@
<programlisting>
configure ... LDFLAGS="-R /usr/sfw/lib:/opt/sfw/lib:/usr/local/lib"
</programlisting>
- See
- the <citerefentry><refentrytitle>ld</><manvolnum>1</></citerefentry>
+ See the
+<citerefentry><refentrytitle>ld</refentrytitle><manvolnum>1</manvolnum></citerefentry>
man page for more information.
</para>
</sect3>
@@ -2915,9 +2917,9 @@
<title>Using DTrace for tracing PostgreSQL</title>
<para>
- Yes, using DTrace is possible. See <![%standalone-include[the
- documentation]]>
- <![%standalone-ignore[<xref linkend="dynamic-trace">]]> for further
+ Yes, using DTrace is possible. See <phrase>the
+ documentation</phrase>
+ <phrase><xref linkend="dynamic-trace"/></phrase> for further
information. You can also find more information in this
article: <ulink url="http://blogs.sun.com/robertlor/entry/user_level_dtrace_probes_in"></ulink>.
</para>
Modified: traduc/trunk/postgresql/intagg.xml
===================================================================
--- traduc/trunk/postgresql/intagg.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/intagg.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -26,7 +26,7 @@
L'agrégateur est une fonction d'agrégat
<function>int_array_aggregate(integer)</function> qui produit un tableau
d'entiers contenant exactement les entiers fournis en argument.
- This is a wrapper around <function>array_agg</>,
+ This is a wrapper around <function>array_agg</function>,
which does the same thing for any array type.
</para>
@@ -35,7 +35,7 @@
<function>int_array_enum(integer[])</function> qui renvoie
<type>setof integer</type>. C'est essentiellement une opération reverse de
l'agrégateur : elle étend un tableau d'entiers en un ensemble de
- lignes. This is a wrapper around <function>unnest</>,
+ lignes. This is a wrapper around <function>unnest</function>,
which does the same thing for any array type.
</para>
Modified: traduc/trunk/postgresql/intarray.xml
===================================================================
--- traduc/trunk/postgresql/intarray.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/intarray.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -218,10 +218,10 @@
</table>
<para>
- The containment operators <literal>@</> and <literal>~</> are functionally
- equivalent to <productname>PostgreSQL</>'s built-in operators
- <literal>@></> and <literal><@</>, respectively, except that
- <literal>@</> and <literal>~</> work only on integer arrays. These
+ The containment operators <literal>@</literal> and <literal>~</literal> are functionally
+ equivalent to <productname>PostgreSQL</productname>'s built-in operators
+ <literal>@></literal> and <literal><@</literal>, respectively, except that
+ <literal>@</literal> and <literal>~</literal> work only on integer arrays. These
operator names are deprecated and will eventually be retired. (Notice that
these names are reversed from the convention formerly followed by the core
geometric datatypes!)
@@ -249,7 +249,7 @@
opérateurs <literal>&&</literal>, <literal>@</literal>,
<literal>~</literal> et <literal>@@</literal>, ainsi qu'une égalité
des tableaux standards
- and the built-in <literal>@></> and <literal><@</> operators
+ and the built-in <literal>@></literal> and <literal><@</literal> operators
(when used on integer arrays).
</para>
Modified: traduc/trunk/postgresql/libpq.xml
===================================================================
--- traduc/trunk/postgresql/libpq.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/libpq.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -236,10 +236,10 @@
<listitem>
<para>
Adds command-line options to send to the server at run-time.
- For example, setting this to <literal>-c geqo=off</> sets the
- session's value of the <varname>geqo</> parameter to
- <literal>off</>. For a detailed discussion of the available
- options, consult <xref linkend="runtime-config">.
+ For example, setting this to <literal>-c geqo=off</literal> sets the
+ session's value of the <varname>geqo</varname> parameter to
+ <literal>off</literal>. For a detailed discussion of the available
+ options, consult <xref linkend="runtime-config"/>.
</para>
</listitem>
</varlistentry>
@@ -287,33 +287,33 @@
<listitem>
<para>
This option controls how libpq verifies the certificate on the
- server when performing an <acronym>SSL</> connection. There are
- three options: <literal>none</> disables verification completely
- (not recommended); <literal>cert</> enables verification that
+ server when performing an <acronym>SSL</acronym> connection. There are
+ three options: <literal>none</literal> disables verification completely
+ (not recommended); <literal>cert</literal> enables verification that
the server certificate chains to a known certificate
- authority (CA); <literal>cn</> will both verify that the
- certificate chains to a known CA and that the <literal>cn</>
+ authority (CA); <literal>cn</literal> will both verify that the
+ certificate chains to a known CA and that the <literal>cn</literal>
attribute of the server certificate matches the server's
hostname (default).
</para>
<para>
- It is always recommended to use the <literal>cn</> value for
+ It is always recommended to use the <literal>cn</literal> value for
this parameter, since this is the only option that prevents
man-in-the-middle attacks. Note that this requires the server
name on the certificate to match exactly with the host name
used for the connection, and therefore does not support connections
to aliased names. It can be used with pure IP address connections
only if the certificate also has just the IP address in the
- <literal>cn</> field.
+ <literal>cn</literal> field.
</para>
<para>
- If the <literal>cn</> attribute in the certificate sent by the
- server starts with an asterisk (<literal>*</>), it will be treated
+ If the <literal>cn</literal> attribute in the certificate sent by the
+ server starts with an asterisk (<literal>*</literal>), it will be treated
as a wildcard. This wildcard can only be present at the start of
- the value, and will match all characters <emphasis>except</> a
- dot (<literal>.</>). This means the certificate will not match
+ the value, and will match all characters <emphasis>except</emphasis> a
+ dot (<literal>.</literal>). This means the certificate will not match
subdomains.
</para>
</listitem>
@@ -356,8 +356,8 @@
This parameter specifies the location for the secret key
used for the client certificate. It can either specify a filename
that will be used instead of the default
- <filename>~/.postgresql/postgresql.key</>, or can specify an external
- engine (engines are <productname>OpenSSL</> loadable modules). The
+ <filename>~/.postgresql/postgresql.key</filename>, or can specify an external
+ engine (engines are <productname>OpenSSL</productname> loadable modules). The
external engine specification should consist of a colon-separated
engine name and an engine-specific key identifier.
</para>
@@ -736,7 +736,7 @@
</varlistentry>
<varlistentry>
- <term><function>PQconninfoParse</function><indexterm><primary>PQconninfoParse</></></term>
+ <term><function>PQconninfoParse</function><indexterm><primary>PQconninfoParse</primary></indexterm></term>
<listitem>
<para>
Returns parsed connection options from the provided connection string.
@@ -753,7 +753,7 @@
the <function>PQconnectdb</function> options in the provided
connection string. The return value points to an array of
<structname>PQconninfoOption</structname> structures, which ends
- with an entry having a null <structfield>keyword</> pointer.
+ with an entry having a null <structfield>keyword</structfield> pointer.
</para>
<para>
@@ -762,9 +762,10 @@
</para>
<para>
- If <literal>errmsg</> is not NULL, then <literal>*errmsg</> is set
+ If <literal>errmsg</literal> is not NULL, then
+ <literal>*errmsg</literal> is set
to NULL on success, else to a malloc'd error string explaining
- the problem. (It is also possible for <literal>*errmsg</> to be
+ the problem. (It is also possible for <literal>*errmsg</literal> to be
set to NULL even when NULL is returned; this indicates an out-of-memory
situation.)
</para>
@@ -773,8 +774,8 @@
After processing the options array, free it by passing it to
<function>PQconninfoFree</function>. If this is not done, some memory
is leaked for each call to <function>PQconninfoParse</function>.
- Conversely, if an error occurs and <literal>errmsg</> is not NULL,
- be sure to free the error string using <function>PQfreemem</>.
+ Conversely, if an error occurs and <literal>errmsg</literal> is not NULL,
+ be sure to free the error string using <function>PQfreemem</function>.
</para>
</listitem>
@@ -1050,7 +1051,7 @@
<literal>is_superuser</literal>,
<literal>session_authorization</literal>,
<literal>datestyle</literal>,
- <literal>IntervalStyle</>,
+ <literal>IntervalStyle</literal>,
<literal>TimeZone</literal>,
<literal>integer_datetimes</literal> et
<literal>standard_conforming_strings</literal>.
@@ -1058,7 +1059,7 @@
<literal>integer_datetimes</literal> n'étaient pas rapportés dans les versions
antérieures à la 8.0 ;
<literal>standard_conforming_strings</literal> n'était pas rapporté dans les versions
-antérieures à la 8.1; <literal>IntervalStyle</> was not reported by releases
+antérieures à la 8.1; <literal>IntervalStyle</literal> was not reported by releases
before 8.4).
Notez que
<literal>server_version</literal>,
@@ -1446,11 +1447,11 @@
Values passed in binary format require knowlege of
the internal representation expected by the backend.
For example, integers must be passed in network byte
- order. Passing <type>numeric</> values requires
+ order. Passing <type>numeric</type> values requires
knowledge of the server storage format, as implemented
in
- <filename>src/backend/utils/adt/numeric.c::numeric_send()</> and
- <filename>src/backend/utils/adt/numeric.c::numeric_recv()</>.
+ <filename>src/backend/utils/adt/numeric.c::numeric_send()</filename> and
+ <filename>src/backend/utils/adt/numeric.c::numeric_recv()</filename>.
</para>
</listitem>
</varlistentry>
@@ -4090,7 +4091,6 @@
Comme toujours, certains fonctions ne sont pas catégorisables.
</para>
-<variablelist>
<variablelist>
<varlistentry>
<term>
@@ -4102,25 +4102,25 @@
<listitem>
<para>
- Frees memory allocated by <application>libpq</>.
+ Frees memory allocated by <application>libpq</application>.
<synopsis>
void PQfreemem(void *ptr);
</synopsis>
</para>
<para>
- Frees memory allocated by <application>libpq</>, particularly
+ Frees memory allocated by <application>libpq</application>, particularly
<function>PQescapeByteaConn</function>,
<function>PQescapeBytea</function>,
<function>PQunescapeBytea</function>,
and <function>PQnotifies</function>.
It is particularly important that this function, rather than
- <function>free()</>, be used on Microsoft Windows. This is because
+ <function>free()</function>, be used on Microsoft Windows. This is because
allocating memory in a DLL and releasing it in the application works
only if multithreaded/single-threaded, release/debug, and static/dynamic
flags are the same for the DLL and the application. On non-Microsoft
Windows platforms, this function is the same as the standard library
- function <function>free()</>.
+ function <function>free()</function>.
</para>
</listitem>
</varlistentry>
@@ -4136,7 +4136,8 @@
<listitem>
<para>
Frees the data structures allocated by
- <function>PQconndefaults</> or <function>PQconninfoParse</>.
+ <function>PQconndefaults</function> or
+ <function>PQconninfoParse</function>.
<synopsis>
void PQconninfoFree(PQconninfoOption *connOptions);
</synopsis>
@@ -4190,18 +4191,18 @@
</para>
<para>
- This is <application>libpq</>'s internal function to allocate and
+ This is <application>libpq</application>'s internal function to allocate and
initialize an empty <structname>PGresult</structname> object. This
function returns NULL if memory could not be allocated. It is
exported because some applications find it useful to generate result
objects (particularly objects with error status) themselves. If
- <parameter>conn</parameter> is not null and <parameter>status</>
+ <parameter>conn</parameter> is not null and <parameter>status</parameter>
indicates an error, the current error message of the specified
connection is copied into the <structname>PGresult</structname>.
Also, if <parameter>conn</parameter> is not null, any event procedures
registered in the connection are copied into the
<structname>PGresult</structname>. (They do not get
- <literal>PGEVT_RESULTCREATE</> calls, but see
+ <literal>PGEVT_RESULTCREATE</literal> calls, but see
<function>PQfireResultCreateEvents</function>.)
Note that <function>PQclear</function> should eventually be called
on the object, just as with a <structname>PGresult</structname>
@@ -4220,7 +4221,7 @@
<listitem>
<para>
Fires a <literal>PGEVT_RESULTCREATE</literal> event (see <xref
- linkend="libpq-events">) for each event procedure registered in the
+ linkend="libpq-events"/>) for each event procedure registered in the
<structname>PGresult</structname> object. Returns non-zero for success,
zero if any event procedure fails.
@@ -4230,14 +4231,15 @@
</para>
<para>
- The <literal>conn</> argument is passed through to event procedures
- but not used directly. It can be <literal>NULL</> if the event
+ The <literal>conn</literal> argument is passed through to event procedures
+ but not used directly. It can be <literal>NULL</literal> if the event
procedures won't use it.
</para>
<para>
Event procedures that have already received a
- <literal>PGEVT_RESULTCREATE</> or <literal>PGEVT_RESULTCOPY</> event
+ <literal>PGEVT_RESULTCREATE</literal> or
+<literal>PGEVT_RESULTCOPY</literal> event
for this object are not fired again.
</para>
@@ -4372,7 +4374,7 @@
<parameter>res</parameter> is cleared. If the function fails,
the return value is <literal>NULL</literal>. The result is
guaranteed to be adequately aligned for any type of data,
- just as for <function>malloc</>.
+ just as for <function>malloc</function>.
</para>
</listitem>
</varlistentry>
@@ -4502,21 +4504,25 @@
<para>
Each registered event handler is associated with two pieces of data,
- known to <application>libpq</application> only as opaque <literal>void *</>
- pointers. There is a <firstterm>passthrough</> pointer that is provided
+ known to <application>libpq</application> only as opaque <literal>void
+ *</literal>
+ pointers. There is a <firstterm>passthrough</firstterm> pointer that is provided
by the application when the event handler is registered with a
- <structname>PGconn</>. The passthrough pointer never changes for the
- life of the <structname>PGconn</> and all <structname>PGresult</>s
+ <structname>PGconn</structname>. The passthrough pointer never changes for the
+ life of the <structname>PGconn</structname> and all
+ <structname>PGresult</structname>s
generated from it; so if used, it must point to long-lived data.
- In addition there is an <firstterm>instance data</> pointer, which starts
- out NULL in every <structname>PGconn</> and <structname>PGresult</>.
+ In addition there is an <firstterm>instance data</firstterm> pointer, which starts
+ out NULL in every <structname>PGconn</structname> and
+ <structname>PGresult</structname>.
This pointer can be manipulated using the
<function>PQinstanceData</function>,
<function>PQsetInstanceData</function>,
<function>PQresultInstanceData</function> and
<function>PQsetResultInstanceData</function> functions. Note that
- unlike the passthrough pointer, instance data of a <structname>PGconn</>
- is not automatically inherited by <structname>PGresult</>s created from
+ unlike the passthrough pointer, instance data of a
+ <structname>PGconn</structname>
+ is not automatically inherited by <structname>PGresult</structname>s created from
it. <application>libpq</application> does not know what passthrough
and instance data pointers point to (if anything) and will never attempt
to free them — that is the responsibility of the event handler.
@@ -4526,7 +4532,7 @@
<title>Event Types</title>
<para>
- The enum <literal>PGEventId</> names the types of events handled by
+ The enum <literal>PGEventId</literal> names the types of events handled by
the event system. All its values have names beginning with
<literal>PGEVT</literal>. For each event type, there is a corresponding
event info structure that carries the parameters passed to the event
@@ -4590,8 +4596,8 @@
<structname>PGconn</structname> was just reset, all event data remains
unchanged. This event should be used to reset/reload/requery any
associated <literal>instanceData</literal>. Note that even if the
- event procedure fails to process <literal>PGEVT_CONNRESET</>, it will
- still receive a <literal>PGEVT_CONNDESTROY</> event when the connection
+ event procedure fails to process <literal>PGEVT_CONNRESET</literal>, it will
+ still receive a <literal>PGEVT_CONNDESTROY</literal> event when the connection
is closed.
</para>
</listitem>
@@ -4651,7 +4657,7 @@
<literal>instanceData</literal> that needs to be associated with the
result. If the event procedure fails, the result will be cleared and
the failure will be propagated. The event procedure must not try to
- <function>PQclear</> the result object for itself. When returning a
+ <function>PQclear</function> the result object for itself. When returning a
failure code, all cleanup must be performed as no
<literal>PGEVT_RESULTDESTROY</literal> event will be sent.
</para>
@@ -4758,7 +4764,7 @@
<para>
A particular event procedure can be registered only once in any
- <structname>PGconn</>. This is because the address of the procedure
+ <structname>PGconn</structname>. This is because the address of the procedure
is used as a lookup key to identify the associated instance data.
</para>
@@ -4767,9 +4773,9 @@
On Windows, functions can have two different addresses: one visible
from outside a DLL and another visible from inside the DLL. One
should be careful that only one of these addresses is used with
- <application>libpq</>'s event-procedure functions, else confusion will
+ <application>libpq</application>'s event-procedure functions, else confusion will
result. The simplest rule for writing code that will work is to
- ensure that event procedures are declared <literal>static</>. If the
+ ensure that event procedures are declared <literal>static</literal>. If the
procedure's address must be available outside its own source file,
expose a separate function to return the address.
</para>
@@ -4803,7 +4809,7 @@
<para>
An event procedure must be registered once on each
- <structname>PGconn</> you want to receive events about. There is no
+ <structname>PGconn</structname> you want to receive events about. There is no
limit, other than memory, on the number of event procedures that
can be registered with a connection. The function returns a non-zero
value if it succeeds and zero if it fails.
@@ -4815,7 +4821,7 @@
<literal>instanceData</literal>. The <parameter>name</parameter>
argument is used to refer to the event procedure in error messages.
This value cannot be NULL or a zero-length string. The name string is
- copied into the <structname>PGconn</>, so what is passed need not be
+ copied into the <structname>PGconn</structname>, so what is passed need not be
long-lived. The <parameter>passThrough</parameter> pointer is passed
to the <parameter>proc</parameter> whenever an event occurs. This
argument can be NULL.
@@ -5082,7 +5088,7 @@
<primary><envar>PGHOST</envar></primary>
</indexterm>
<envar>PGHOST</envar> behaves the same as <xref
- linkend="libpq-connect-host"> connection parameter.
+ linkend="libpq-connect-host"/> connection parameter.
</para>
</listitem>
<listitem>
@@ -5091,7 +5097,7 @@
<primary><envar>PGHOSTADDR</envar></primary>
</indexterm>
<envar>PGHOSTADDR</envar> behaves the same as <xref
-linkend="libpq-connect-hostaddr"> connection parameter.
+linkend="libpq-connect-hostaddr"/> connection parameter.
Elle peut être initialisée avec <envar>PGHOST</envar> pour éviter
la surcharge des recherches DNS.
</para>
@@ -5102,7 +5108,7 @@
<primary><envar>PGPORT</envar></primary>
</indexterm>
<envar>PGPORT</envar> behaves the same as <xref
- linkend="libpq-connect-port"> connection parameter.
+ linkend="libpq-connect-port"/> connection parameter.
</para>
</listitem>
<listitem>
@@ -5111,7 +5117,7 @@
<primary><envar>PGDATABASE</envar></primary>
</indexterm>
<envar>PGDATABASE</envar> behaves the same as <xref
- linkend="libpq-connect-dbname"> connection parameter.
+ linkend="libpq-connect-dbname"/> connection parameter.
</para>
</listitem>
<listitem>
@@ -5120,7 +5126,7 @@
<primary><envar>PGUSER</envar></primary>
</indexterm>
<envar>PGUSER</envar> behaves the same as <xref
- linkend="libpq-connect-user"> connection parameter.
+ linkend="libpq-connect-user"/> connection parameter.
database.
</para>
</listitem>
@@ -5130,7 +5136,7 @@
<primary><envar>PGPASSWORD</envar></primary>
</indexterm>
<envar>PGPASSWORD</envar> behaves the same as <xref
- linkend="libpq-connect-password"> connection parameter. L'utilisation de cette variable
+ linkend="libpq-connect-password"/> connection parameter. L'utilisation de cette variable
d'environnement n'est pas recommandée pour des raisons de sécurité (certains
systèmes d'exploitation autorisent les utilisateurs autres que root à voir les
variables d'environnement du processus via <application>ps</application>) ; à la
@@ -5155,7 +5161,7 @@
<primary><envar>PGSERVICE</envar></primary>
</indexterm>
<envar>PGSERVICE</envar> behaves the same as <xref
- linkend="libpq-connect-service"> connection parameter.
+ linkend="libpq-connect-service"/> connection parameter.
</para>
</listitem>
<listitem>
@@ -5179,7 +5185,7 @@
<primary><envar>PGOPTIONS</envar></primary>
</indexterm>
<envar>PGOPTIONS</envar> behaves the same as <xref
- linkend="libpq-connect-options"> connection parameter.
+ linkend="libpq-connect-options"/> connection parameter.
</para>
</listitem>
<listitem>
@@ -5188,7 +5194,7 @@
<primary><envar>PGSSLMODE</envar></primary>
</indexterm>
<envar>PGSSLMODE</envar> behaves the same as <xref
- linkend="libpq-connect-sslmode"> connection parameter.
+ linkend="libpq-connect-sslmode"/> connection parameter.
</para>
</listitem>
<listitem>
@@ -5197,7 +5203,7 @@
<primary><envar>PGSSLVERIFY</envar></primary>
</indexterm>
<envar>PGSSLVERIFY</envar> behaves the same as <xref
- linkend="libpq-connect-sslverify"> connection parameter.
+ linkend="libpq-connect-sslverify"/> connection parameter.
</para>
</listitem>
@@ -5207,7 +5213,7 @@
<primary><envar>PGREQUIRESSL</envar></primary>
</indexterm>
<envar>PGREQUIRESSL</envar> behaves the same as <xref
- linkend="libpq-connect-requiressl"> connection parameter.
+ linkend="libpq-connect-requiressl"/> connection parameter.
</para>
</listitem>
<listitem>
@@ -5230,7 +5236,7 @@
<primary><envar>PGSSLCERT</envar></primary>
</indexterm>
<envar>PGSSLCERT</envar> behaves the same as <xref
- linkend="libpq-connect-sslcert"> connection parameter.
+ linkend="libpq-connect-sslcert"/> connection parameter.
</para>
</listitem>
@@ -5240,7 +5246,7 @@
<primary><envar>PGSSLKEY</envar></primary>
</indexterm>
<envar>PGSSLKEY</envar> behaves the same as <xref
- linkend="libpq-connect-sslkey"> connection parameter.
+ linkend="libpq-connect-sslkey"/> connection parameter.
</para>
</listitem>
<listitem>
@@ -5249,7 +5255,7 @@
<primary><envar>PGSSLROOTCERT</envar></primary>
</indexterm>
<envar>PGSSLROOTCERT</envar> behaves the same as <xref
- linkend="libpq-connect-sslrootcert"> connection parameter.
+ linkend="libpq-connect-sslrootcert"/> connection parameter.
</para>
</listitem>
@@ -5259,7 +5265,7 @@
<primary><envar>PGSSLCRL</envar></primary>
</indexterm>
<envar>PGSSLCRL</envar> behaves the same as <xref
- linkend="libpq-connect-sslcrl"> connection parameter.
+ linkend="libpq-connect-sslcrl"/> connection parameter.
</para>
</listitem>
@@ -5269,7 +5275,7 @@
<primary><envar>PGKRBSRVNAME</envar></primary>
</indexterm>
<envar>PGKRBSRVNAME</envar> behaves the same as <xref
- linkend="libpq-connect-krbsrvname"> connection parameter.
+ linkend="libpq-connect-krbsrvname"/> connection parameter.
</para>
</listitem>
@@ -5279,7 +5285,7 @@
<primary><envar>PGGSSLIB</envar></primary>
</indexterm>
<envar>PGGSSLIB</envar> behaves the same as <xref
- linkend="libpq-connect-gsslib"> connection parameter.
+ linkend="libpq-connect-gsslib"/> connection parameter.
</para>
</listitem>
@@ -5289,7 +5295,7 @@
<primary><envar>PGCONNECT_TIMEOUT</envar></primary>
</indexterm>
<envar>PGCONNECT_TIMEOUT</envar> behaves the same as <xref
- linkend="libpq-connect-connect-timeout"> connection parameter.
+ linkend="libpq-connect-connect-timeout"/> connection parameter.
</para>
</listitem>
</itemizedlist>
@@ -5561,10 +5567,11 @@
</para>
<para>
- When the <literal>sslverify</> parameter is set to <literal>cn</> or
- <literal>cert</>, libpq will verify that the server certificate is
- trustworthy by checking the certificate chain up to a <acronym>CA</>.
- For this to work, place the certificate of a trusted <acronym>CA</>
+ When the <literal>sslverify</literal> parameter is set to
+ <literal>cn</literal> or
+ <literal>cert</literal>, libpq will verify that the server certificate is
+ trustworthy by checking the certificate chain up to a <acronym>CA</acronym>.
+ For this to work, place the certificate of a trusted <acronym>CA</acronym>
in the
fichier <filename>~/.postgresql/root.crt</filename> dans le répertoire
personnel de l'utilisateur.
@@ -5578,8 +5585,10 @@
(<filename>%APPDATA%\postgresql\root.crl</filename> sur Microsoft
Windows).
The location of the root certificate store and the CRL can be overridden
- by the connection parameters <literal>sslrootcert</> and <literal>sslcrl</>
- or the environment variables <envar>PGSSLROOTCERT</> and <envar>PGSSLCRL</>.
+ by the connection parameters <literal>sslrootcert</literal> and
+ <literal>sslcrl</literal>
+ or the environment variables <envar>PGSSLROOTCERT</envar> and
+ <envar>PGSSLCRL</envar>.
</para>
<para>
@@ -5597,8 +5606,9 @@
<filename>%APPDATA%\postgresql\postgresql.key</filename>, and there
is no special permissions check since the directory is presumed secure.
The location of the certificate and key files can be overridden by the
- connection parameters <literal>sslcert</> and <literal>sslkey</> or the
- environment variables <envar>PGSSLCERT</> and <envar>PGSSLKEY</>.
+ connection parameters <literal>sslcert</literal> and
+ <literal>sslkey</literal> or the
+ environment variables <envar>PGSSLCERT</envar> and <envar>PGSSLKEY</envar>.
</para>
<table id="libpq-ssl-file-usage">
@@ -5646,11 +5656,11 @@
</table>
<para>
- If your application initializes <literal>libssl</> and/or
- <literal>libcrypto</> libraries and <application>libpq</application>
- is built with <acronym>SSL</> support, you should call
- <function>PQinitOpenSSL</> to tell <application>libpq</application>
- that the <literal>libssl</> and/or <literal>libcrypto</> libraries
+ If your application initializes <literal>libssl</literal> and/or
+ <literal>libcrypto</literal> libraries and <application>libpq</application>
+ is built with <acronym>SSL</acronym> support, you should call
+ <function>PQinitOpenSSL</function> to tell <application>libpq</application>
+ that the <literal>libssl</literal> and/or <literal>libcrypto</literal> libraries
have been initialized by your application, so that
<application>libpq</application> will not also initialize those libraries.
<!-- If this URL changes replace it with a URL to www.archive.org. -->
@@ -5678,18 +5688,20 @@
</para>
<para>
- When <parameter>do_ssl</> is non-zero, <application>libpq</application>
- will initialize the <application>OpenSSL</> library before first
- opening a database connection. When <parameter>do_crypto</> is
- non-zero, the <literal>libcrypto</> library will be initialized. By
- default (if <function>PQinitOpenSSL</> is not called), both libraries
+ When <parameter>do_ssl</parameter> is non-zero, <application>libpq</application>
+ will initialize the <application>OpenSSL</application> library before first
+ opening a database connection. When <parameter>do_crypto</parameter> is
+ non-zero, the <literal>libcrypto</literal> library will be initialized. By
+ default (if <function>PQinitOpenSSL</function> is not called), both libraries
are initialized. When SSL support is not compiled in, this function is
present but does nothing.
</para>
<para>
- If your application uses and initializes either <application>OpenSSL</>
- or its underlying <literal>libcrypto</> library, you <emphasis>must</>
+ If your application uses and initializes either
+ <application>OpenSSL</application>
+ or its underlying <literal>libcrypto</literal> library, you
+ <emphasis>must</emphasis>
call this function with zeroes for the appropriate parameter(s)
before first opening a database connection. Also be sure that you
have done that initialization before opening a database connection.
@@ -5715,15 +5727,17 @@
<para>
This function is equivalent to
- <literal>PQinitOpenSSL(do_ssl, do_ssl)</>.
+ <literal>PQinitOpenSSL(do_ssl, do_ssl)</literal>.
It is sufficient for applications that initialize both or neither
- of <application>OpenSSL</> and <literal>libcrypto</>.
+ of <application>OpenSSL</application> and <literal>libcrypto</literal>.
</para>
<para>
- <function>PQinitSSL</> has been present since
- <productname>PostgreSQL</> 8.0, while <function>PQinitOpenSSL</>
- was added in <productname>PostgreSQL</> 8.4, so <function>PQinitSSL</>
+ <function>PQinitSSL</function> has been present since
+ <productname>PostgreSQL</productname> 8.0, while
+ <function>PQinitOpenSSL</function>
+ was added in <productname>PostgreSQL</productname> 8.4, so
+ <function>PQinitSSL</function>
might be preferable for applications that need to work with older
versions of <application>libpq</application>.
</para>
Modified: traduc/trunk/postgresql/lobj.xml
===================================================================
--- traduc/trunk/postgresql/lobj.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/lobj.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -161,19 +161,20 @@
<synopsis>
Oid lo_import_with_oid(PGconn *conn, const char *filename, Oid lobjId);
</synopsis>
- <indexterm><primary>lo_import_with_oid</></>
+ <indexterm><primary>lo_import_with_oid</primary></indexterm>
also imports a new large object. The OID to be assigned can be
specified by <replaceable class="parameter">lobjId</replaceable>;
if so, failure occurs if that OID is already in use for some large
object. If <replaceable class="parameter">lobjId</replaceable>
- is <symbol>InvalidOid</symbol> (zero) then <function>lo_import_with_oid</> assigns an unused
- OID (this is the same behavior as <function>lo_import</>).
+ is <symbol>InvalidOid</symbol> (zero) then
+ <function>lo_import_with_oid</function> assigns an unused
+ OID (this is the same behavior as <function>lo_import</function>).
The return value is the OID that was assigned to the new large object,
or <symbol>InvalidOid</symbol> (zero) on failure.
</para>
<para>
- <function>lo_import_with_oid</> is new as of <productname>PostgreSQL</productname>
+ <function>lo_import_with_oid</function> is new as of <productname>PostgreSQL</productname>
8.4 and uses <function>lo_create</function> internally which is new in 8.1; if this function is run against 8.0 or before, it will
fail and return <symbol>InvalidOid</symbol>.
</para>
@@ -687,7 +688,7 @@
PQfinish(conn);
exit(0);
}
-</programlisting>
+]]></programlisting>
</example>
</sect1>
Modified: traduc/trunk/postgresql/maintenance.xml
===================================================================
--- traduc/trunk/postgresql/maintenance.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/maintenance.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -51,9 +51,9 @@
<para>
<ulink
- url="http://bucardo.org/check_postgres/"><application>check_postgres.pl</></ulink>
+ url="http://bucardo.org/check_postgres/"><application>check_postgres.pl</application></ulink>
is available for monitoring database health and reporting unusual
- conditions. <application>check_postgres.pl</> integrates with
+ conditions. <application>check_postgres.pl</application> integrates with
Nagios and MRTG, but can be run standalone too.
</para>
@@ -72,15 +72,15 @@
<para>
<productname>PostgreSQL</productname> databases require periodic
- maintenance known as <firstterm>vacuuming</>. For many installations, it
+ maintenance known as <firstterm>vacuuming</firstterm>. For many installations, it
is sufficient to let vacuuming be performed by the <firstterm>autovacuum
- daemon</>, which is described in <xref linkend="autovacuum">. You might
+ daemon</firstterm>, which is described in <xref linkend="autovacuum"/>. You might
need to adjust the autovacuuming parameters described there to obtain best
results for your situation. Some database administrators will want to
supplement or replace the daemon's activities with manually-managed
- <command>VACUUM</> commands, which typically are executed according to a
+ <command>VACUUM</command> commands, which typically are executed according to a
schedule by <application>cron</application> or <application>Task
- Scheduler</> scripts. To set up manually-managed vacuuming properly,
+ Scheduler</application> scripts. To set up manually-managed vacuuming properly,
it is essential to understand the issues discussed in the next few
subsections. Administrators who rely on autovacuuming may still wish
to skim this material to help them understand and adjust autovacuuming.
@@ -110,29 +110,29 @@
d'un <firstterm>cycle de l'identifiant de transaction (XID)</firstterm>.</simpara>
</listitem>
</orderedlist>
- </para>
- Each of these reasons dictates performing <command>VACUUM</> operations
+ Each of these reasons dictates performing <command>VACUUM</command> operations
of varying frequency and scope, as explained in the following subsections.
</para>
<para>
- There are two variants of <command>VACUUM</>: standard <command>VACUUM</>
- and <command>VACUUM FULL</>. <command>VACUUM FULL</> can reclaim more
+ There are two variants of <command>VACUUM</command>: standard
+ <command>VACUUM</command>
+ and <command>VACUUM FULL</command>. <command>VACUUM FULL</command> can reclaim more
disk space but runs much more slowly. Also,
- the standard form of <command>VACUUM</> can run in parallel with production
+ the standard form of <command>VACUUM</command> can run in parallel with production
database operations. (Commands such as <command>SELECT</command>,
<command>INSERT</command>, <command>UPDATE</command>, and
<command>DELETE</command> will continue to function as normal, though you
will not be able to modify the definition of a table with commands such as
<command>ALTER TABLE</command> while it is being vacuumed.)
- <command>VACUUM FULL</> requires exclusive lock on the table it is
+ <command>VACUUM FULL</command> requires exclusive lock on the table it is
working on, and therefore cannot be done in parallel with other use
- of the table. Another disadvantage of <command>VACUUM FULL</> is that
+ of the table. Another disadvantage of <command>VACUUM FULL</command> is that
while it reduces table size, it does not reduce index size proportionally;
- in fact it can make indexes <emphasis>larger</>. Generally, therefore,
- administrators should strive to use standard <command>VACUUM</> and
- avoid <command>VACUUM FULL</>.
+ in fact it can make indexes <emphasis>larger</emphasis>. Generally, therefore,
+ administrators should strive to use standard <command>VACUUM</command> and
+ avoid <command>VACUUM FULL</command>.
</para>
<para>
@@ -140,7 +140,7 @@
traffic, which can cause poor performance for other active sessions.
There are configuration parameters that can be adjusted to reduce the
performance impact of background vacuuming — see
- <xref linkend="runtime-config-resource-vacuum-cost">.
+ <xref linkend="runtime-config-resource-vacuum-cost"/>.
</para>
</sect2>
@@ -171,7 +171,7 @@
future reuse. However, it will not return the space to the operating
system, except in the special case where one or more pages at the
end of a table become entirely free and an exclusive table lock can be
- easily obtained. In contrast, <command>VACUUM FULL</> actively compacts
+ easily obtained. In contrast, <command>VACUUM FULL</command> actively compacts
tables by moving row versions to earlier pages. It is thus able to
force pages at the end of the table to become entirely free, whereupon
it will return them to the operating system. However, if many rows
@@ -182,18 +182,19 @@
</para>
<para>
- The usual goal of routine vacuuming is to do standard <command>VACUUM</>s
- often enough to avoid needing <command>VACUUM FULL</>. The
+ The usual goal of routine vacuuming is to do standard
+ <command>VACUUM</command>s
+ often enough to avoid needing <command>VACUUM FULL</command>. The
autovacuum daemon attempts to work this way, and in fact will
- never issue <command>VACUUM FULL</>. In this approach, the idea
+ never issue <command>VACUUM FULL</command>. In this approach, the idea
is not to keep tables at their minimum size, but to maintain steady-state
usage of disk space: each table occupies space equivalent to its
minimum size plus however much space gets used up between vacuumings.
- Although <command>VACUUM FULL</> can be used to shrink a table back
+ Although <command>VACUUM FULL</command> can be used to shrink a table back
to its minimum size and return the disk space to the operating system,
there is not much point in this if the table will just grow again in the
- future. Thus, moderately-frequent standard <command>VACUUM</> runs are a
- better approach than infrequent <command>VACUUM FULL</> runs for
+ future. Thus, moderately-frequent standard <command>VACUUM</command> runs are a
+ better approach than infrequent <command>VACUUM FULL</command> runs for
maintaining heavily-updated tables.
</para>
@@ -202,14 +203,14 @@
doing all the work at night when load is low.
The difficulty with doing vacuuming according to a fixed schedule
is that if a table has an unexpected spike in update activity, it may
- get bloated to the point that <command>VACUUM FULL</> is really necessary
+ get bloated to the point that <command>VACUUM FULL</command> is really necessary
to reclaim space. Using the autovacuum daemon alleviates this problem,
since the daemon schedules vacuuming dynamically in response to update
activity. It is unwise to disable the daemon completely unless you
have an extremely predictable workload. One possible compromise is
to set the daemon's parameters so that it will only react to unusually
heavy update activity, thus keeping things from getting out of hand,
- while scheduled <command>VACUUM</>s are expected to do the bulk of the
+ while scheduled <command>VACUUM</command>s are expected to do the bulk of the
work when the load is typical.
</para>
@@ -228,19 +229,19 @@
<tip>
<para>
- Neither form of <command>VACUUM</> is entirely satisfactory when
+ Neither form of <command>VACUUM</command> is entirely satisfactory when
a table contains large numbers of dead row versions as a result of
massive update or delete activity. If you have such a table and
you need to reclaim the excess disk space it occupies, the best
- way is to use <xref linkend="sql-cluster" endterm="sql-cluster-title">
+ way is to use <xref linkend="sql-cluster" endterm="sql-cluster-title"/>
or one of the table-rewriting variants of
- <xref linkend="sql-altertable" endterm="sql-altertable-title">.
+ <xref linkend="sql-altertable" endterm="sql-altertable-title"/>.
These commands rewrite an entire new copy of the table and build
- new indexes for it. Like <command>VACUUM FULL</>, they require
+ new indexes for it. Like <command>VACUUM FULL</command>, they require
exclusive lock. Note that they also temporarily use extra disk
space, since the old copies of the table and indexes can't be
released until the new ones are complete. In the worst case where
- your disk is nearly full, <command>VACUUM FULL</> may be the only
+ your disk is nearly full, <command>VACUUM FULL</command> may be the only
workable alternative.
</para>
</tip>
@@ -248,7 +249,7 @@
<tip>
<para>
Si vous avez une table dont le contenu entier est supprimé sur une base périodique,
- considérez de le faire avec <xref linkend="sql-truncate" endterm="sql-truncate-title"> plutôt qu'avec
+ considérez de le faire avec <xref linkend="sql-truncate" endterm="sql-truncate-title"/> plutôt qu'avec
<command>DELETE</command> suivi par un <command>VACUUM</command>.
<command>TRUNCATE</command> supprime le contenu entier de la table
immédiatement sans nécessiter un <command>VACUUM</command> ou
@@ -285,12 +286,12 @@
<para>
The autovacuum daemon, if enabled, will automatically issue
- <command>ANALYZE</> commands whenever the content of a table has
+ <command>ANALYZE</command> commands whenever the content of a table has
changed sufficiently. However, administrators might prefer to rely
- on manually-scheduled <command>ANALYZE</> operations, particularly
+ on manually-scheduled <command>ANALYZE</command> operations, particularly
if it is known that update activity on a table will not affect the
- statistics of <quote>interesting</> columns. The daemon schedules
- <command>ANALYZE</> strictly as a function of the number of rows
+ statistics of <quote>interesting</quote> columns. The daemon schedules
+ <command>ANALYZE</command> strictly as a function of the number of rows
inserted or updated; it has no knowledge of whether that will lead
to meaningful statistical changes.
</para>
@@ -317,7 +318,7 @@
mettre à jour certaines statistiques plus souvent que les autres en
fonction des besoins de l'application. Quoi qu'il en soit, dans la pratique,
il est généralement mieux de simplement analyser la base entière car il s'agit
- d'une opération rapide. <command>ANALYZE</> utilise un système d'échantillonage des lignes d'une
+ d'une opération rapide. <command>ANALYZE</command> utilise un système d'échantillonage des lignes d'une
table, ce qui lui évite de lire chaque ligne.
</para>
@@ -330,7 +331,7 @@
distribution n'est pas uniforme requièrent des histogrammes plus précis
que les autres colonnes. Voir <command>ALTER TABLE SET STATISTICS</command>,
or change the database-wide default using the <xref
- linkend="guc-default-statistics-target"> configuration parameter.
+ linkend="guc-default-statistics-target"/> configuration parameter.
</para>
</tip>
</sect2>
@@ -384,13 +385,15 @@
<para>
Le comportement du <command>VACUUM</command> est contrôlé par deux paramètres
- de configuration : <xref linkend="guc-vacuum-freeze-min-age"/> and
- <xref linkend="guc-vacuum-freeze-table-age">. .
- <varname>vacuum_freeze_table_age</> controls when <command>VACUUM</>
+ de configuration : <xref linkend="guc-vacuum-freeze-min-age"/> et
+ <xref linkend="guc-vacuum-freeze-table-age"/>.
+ <varname>vacuum_freeze_table_age</varname> controls when
+ <command>VACUUM</command>
performs a full sweep of the table, in order to replace old XID values
- with <literal>FrozenXID</>. <varname>vacuum_freeze_min_age</>
+ with <literal>FrozenXID</literal>.
+ <varname>vacuum_freeze_min_age</varname>
controls how old an XID value has to be before it's replaced with
- <literal>FrozenXID</>. Les valeurs plus importantes de ces deux paramètres
+ <literal>FrozenXID</literal>. Les valeurs plus importantes de ces deux paramètres
préservent l'information
transactionnelles plus longtemps alors que les valeurs plus petites
augmentent le nombre de transactions qui peuvent survenir avant un nouveau
@@ -400,7 +403,7 @@
<para>
Le temps maximum où une table peut rester sans VACUUM est de deux millions
de transactions moins <varname>vacuum_freeze_min_age</varname> quand
- <command>VACUUM</> last scanned the whole table. Si elle devait rester sans
+ <command>VACUUM</command> last scanned the whole table. Si elle devait rester sans
VACUUM après
cela, des pertes de données pourraient survenir. Pour s'assurer que cela
n'arrive pas, autovacuum est appelé sur chaque table qui pourrait
@@ -425,14 +428,14 @@
</para>
<para>
- Le seul inconvénient à augmenter <varname>vacuum_freeze_table_age</> et
+ Le seul inconvénient à augmenter <varname>vacuum_freeze_table_age</varname> et
<varname>autovacuum_freeze_max_age</varname>
est que le sous-répertoire <filename>pg_clog</filename> du cluster prendre
plus de place car il doit stocker le statut du COMMIT pour toutes les
transactions depuis <varname>autovacuum_freeze_max_age</varname>. L'état de
COMMIT utilise deux bits par transaction, donc si
<varname>autovacuum_freeze_max_age</varname> et
- <varname>vacuum_freeze_table_age</> ont une valeur maximum permise
+ <varname>vacuum_freeze_table_age</varname> ont une valeur maximum permise
d'un peu moins que deux billion, <filename>pg_clog</filename> peut grossir
jusqu'à la moitié d'un Go. Si c'est rien comparé à votre taille de base
totale, configurer <varname>autovacuum_freeze_max_age</varname> à son
@@ -478,23 +481,25 @@
SELECT datname, age(datfrozenxid) FROM pg_database;</programlisting>
La colonne <literal>age</literal> mesure le nombre de transactions à partir
- du XID final vers le XID de transaction en cours. When <command>VACUUM</>
- scans the whole table, after it's finished <literal>age(relfrozenxid)</>
- should be a little more than the <varname>vacuum_freeze_min_age</> setting
+ du XID final vers le XID de transaction en cours. When
+ <command>VACUUM</command>
+ scans the whole table, after it's finished
+ <literal>age(relfrozenxid)</literal>
+ should be a little more than the <varname>vacuum_freeze_min_age</varname> setting
that was used (more by the number of transactions started since the
- <command>VACUUM</> started).
+ <command>VACUUM</command> started).
</para>
<para>
- <command>VACUUM</> normally only scans pages that have been modified
- since last vacuum, but <structfield>relfrozenxid</> can only be advanced
+ <command>VACUUM</command> normally only scans pages that have been modified
+ since last vacuum, but <structfield>relfrozenxid</structfield> can only be advanced
when the whole table is scanned. The whole table is scanned when
- <structfield>relfrozenxid</> is more than
- <varname>vacuum_freeze_table_age</> transactions old, if
- <command>VACUUM FREEZE</> command is used, or if all pages happen to
+ <structfield>relfrozenxid</structfield> is more than
+ <varname>vacuum_freeze_table_age</varname> transactions old, if
+ <command>VACUUM FREEZE</command> command is used, or if all pages happen to
require vacuuming to remove dead row versions. If no whole-table-scanning
- <command>VACUUM</> is issued on the table until
- <varname>autovacuum_freeze_max_age</> is reached, an autovacuum will soon
+ <command>VACUUM</command> is issued on the table until
+ <varname>autovacuum_freeze_max_age</varname> is reached, an autovacuum will soon
be forced for the table.
</para>
@@ -509,10 +514,10 @@
HINT: To avoid a database shutdown, execute a database-wide VACUUM in "mydb".
</programlisting>
- (A manual <command>VACUUM</> should fix the problem, as suggested by the
- hint; but note that the <command>VACUUM</> must be performed by a
+ (A manual <command>VACUUM</command> should fix the problem, as suggested by the
+ hint; but note that the <command>VACUUM</command> must be performed by a
superuser, else it will fail to process system catalogs and thus not
- be able to advance the database's <structfield>datfrozenxid</>.)
+ be able to advance the database's <structfield>datfrozenxid</structfield>.)
Si ces avertissements sont ignorés, le système s'arrêtera et refusera
d'exécuter toute nouvelle transaction dès qu'il n'en restera qu'un
million avant la réinitialisation :
@@ -556,7 +561,7 @@
</para>
<para>
- The <quote>autovacuum daemon</> actually consists of multiple processes.
+ The <quote>autovacuum daemon</quote> actually consists of multiple processes.
Un processus démon permanent appelé <firstterm>autovacuum launcher</firstterm>
(autrement dit le lanceur d'autovacuum), qui
est en charge de lancer un processus travailleur (<firstterm>autovacuum
@@ -623,17 +628,18 @@
<filename>postgresql.conf</filename>, mais il est possible de les surcharger
table par table; see
<xref linkend="sql-createtable-storage-parameters"
- endterm="sql-createtable-storage-parameters-title"> for more information.
+ endterm="sql-createtable-storage-parameters-title"/> for more information.
If a setting
has been changed via storage parameters, that value is used; otherwise the
- global settings are used. See <xref linkend="runtime-config-autovacuum"> for
+ global settings are used. See <xref linkend="runtime-config-autovacuum"/> for
more details on the global settings.
</para>
<para>
En plus des valeurs de la limite de base et des facteurs d'échelle, il
existe six autres paramètres autovacuum pouvant être configurés pour chaque table
- via storage parameters.. Le premier paramètre, <literal>autovacuum_enabled</>,
+ via storage parameters.. Le premier paramètre,
+ <literal>autovacuum_enabled</literal>,
peut être configuré à <literal>false</literal> pour instruire le démon
autovacuum de laisser cette table particulière. Dans ce cas, autovacuum
touchera seulement la table quand il devra le faire pour prévenir la
@@ -650,7 +656,7 @@
sont utilisés pour configurer des valeurs par table, respectivement
<xref linkend="guc-vacuum-freeze-min-age"/>,
<xref linkend="guc-autovacuum-freeze-max-age"/> et
- <xref linkend="guc-vacuum-freeze-table-age">.
+ <xref linkend="guc-vacuum-freeze-table-age"/>.
</para>
<para>
Modified: traduc/trunk/postgresql/monitoring.xml
===================================================================
--- traduc/trunk/postgresql/monitoring.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/monitoring.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -154,7 +154,7 @@
</para>
<para>
- The parameter <xref linkend="guc-track-functions"> enables tracking of
+ The parameter <xref linkend="guc-track-functions"/> enables tracking of
usage of user-defined functions.
</para>
@@ -180,7 +180,7 @@
These files are stored in the <filename>pg_stat_tmp</filename> subdirectory.
When the postmaster shuts down, a permanent copy of the statistics
data is stored in the <filename>global</filename> subdirectory. For increased
- performance, the parameter <xref linkend="guc-stats-temp-directory"> can
+ performance, the parameter <xref linkend="guc-stats-temp-directory"/> can
be pointed at a RAM based filesystem, decreasing physical I/O requirements.
</para>
@@ -407,7 +407,7 @@
</row>
<row>
- <entry><structname>pg_stat_user_functions</></entry>
+ <entry><structname>pg_stat_user_functions</structname></entry>
<entry>For all tracked functions, function OID, schema, name, number
of calls, total time, and self time. Self time is the
amount of time spent in the function itself, total time includes the
@@ -1081,7 +1081,7 @@
<ulink url="http://sourceware.org/systemtap/">SystemTap</ulink> project
for Linux also provides a DTrace equivalent. Supporting other dynamic
tracing utilities is theoretically possible by changing the definitions for
- the macros in <filename>src/include/utils/probes.h</>.
+ the macros in <filename>src/include/utils/probes.h</filename>.
</para>
<sect2 id="compiling-for-trace">
@@ -1101,8 +1101,8 @@
<para>
A number of standard probes are provided in the source code,
- as shown in <xref linkend="dtrace-probe-point-table">.
- More can certainly be added to enhance <productname>PostgreSQL</>'s
+ as shown in <xref linkend="dtrace-probe-point-table"/>.
+ More can certainly be added to enhance <productname>PostgreSQL</productname>'s
observability.
</para>
@@ -1118,6 +1118,7 @@
</thead>
<tbody>
+ <row>
<entry>transaction-start</entry>
<entry>(LocalTransactionId)</entry>
<entry>Probe that fires at the start of a new transaction.
@@ -1195,7 +1196,7 @@
<entry>statement-status</entry>
<entry>(const char *)</entry>
<entry>Probe that fires anytime the server process updates its
- <structname>pg_stat_activity</>.<structfield>current_query</> status.
+ <structname>pg_stat_activity</structname>.<structfield>current_query</structfield> status.
arg0 is the new status string.</entry>
</row>
<row>
@@ -1361,7 +1362,7 @@
<entry>(ForkNumber, BlockNumber, Oid, Oid, Oid)</entry>
<entry>Probe that fires when a server process begins to write a dirty
buffer. (If this happens often, it implies that
- <xref linkend="guc-shared-buffers"> is too
+ <xref linkend="guc-shared-buffers"/> is too
small or the bgwriter control parameters need adjustment.)
arg0 and arg1 contain the fork and block numbers of the page.
arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs
@@ -1379,7 +1380,7 @@
<entry>Probe that fires when when a server process begins to write a
dirty WAL buffer because no more WAL buffer space is available.
(If this happens often, it implies that
- <xref linkend="guc-wal-buffers"> is too small.)</entry>
+ <xref linkend="guc-wal-buffers"/> is too small.)</entry>
</row>
<row>
<entry>wal-buffer-write-dirty-done</entry>
@@ -1645,15 +1646,16 @@
<step>
<para>
- Add the probe definitions to <filename>src/backend/utils/probes.d</>
+ Add the probe definitions to
+ <filename>src/backend/utils/probes.d</filename>
</para>
</step>
<step>
<para>
- Include <filename>pg_trace.h</> if it is not already present in the
+ Include <filename>pg_trace.h</filename> if it is not already present in the
module(s) containing the probe points, and insert
- <literal>TRACE_POSTGRESQL</> probe macros at the desired locations
+ <literal>TRACE_POSTGRESQL</literal> probe macros at the desired locations
in the source code
</para>
</step>
@@ -1676,30 +1678,31 @@
<procedure>
<step>
<para>
- Decide that the probe will be named <literal>transaction-start</> and
+ Decide that the probe will be named <literal>transaction-start</literal> and
requires a parameter of type LocalTransactionId
</para>
</step>
<step>
<para>
- Add the probe definition to <filename>src/backend/utils/probes.d</>:
+ Add the probe definition to
+ <filename>src/backend/utils/probes.d</filename>:
<programlisting>
probe transaction__start(LocalTransactionId);
</programlisting>
Note the use of the double underline in the probe name. In a DTrace
script using the probe, the double underline needs to be replaced with a
- hyphen, so <literal>transaction-start</> is the name to document for
+ hyphen, so <literal>transaction-start</literal> is the name to document for
users.
</para>
</step>
<step>
<para>
- At compile time, <literal>transaction__start</> is converted to a macro
- called <literal>TRACE_POSTGRESQL_TRANSACTION_START</> (notice the
+ At compile time, <literal>transaction__start</literal> is converted to a macro
+ called <literal>TRACE_POSTGRESQL_TRANSACTION_START</literal> (notice the
underscores are single here), which is available by including
- <filename>pg_trace.h</>. Add the macro call to the appropriate location
+ <filename>pg_trace.h</filename>. Add the macro call to the appropriate location
in the source code. In this case, it looks like the following:
<programlisting>
@@ -1743,9 +1746,9 @@
<listitem>
<para>
On most platforms, if <productname>PostgreSQL</productname> is
- built with <option>--enable-dtrace</>, the arguments to a trace
+ built with <option>--enable-dtrace</option>, the arguments to a trace
macro will be evaluated whenever control passes through the
- macro, <emphasis>even if no tracing is being done</>. This is
+ macro, <emphasis>even if no tracing is being done</emphasis>. This is
usually not worth worrying about if you are just reporting the
values of a few local variables. But beware of putting expensive
function calls into the arguments. If you need to do that,
@@ -1757,7 +1760,7 @@
TRACE_POSTGRESQL_TRANSACTION_START(some_function(...));
</programlisting>
- Each trace macro has a corresponding <literal>ENABLED</> macro.
+ Each trace macro has a corresponding <literal>ENABLED</literal> macro.
</para>
</listitem>
</itemizedlist>
Modified: traduc/trunk/postgresql/mvcc.xml
===================================================================
--- traduc/trunk/postgresql/mvcc.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/mvcc.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -255,7 +255,7 @@
<firstterm>Read Committed</firstterm> is the default isolation
level in <productname>PostgreSQL</productname>. When a transaction
uses this isolation level, a <command>SELECT</command> query
- (without a <literal>FOR UPDATE/SHARE</> clause) sees only data
+ (without a <literal>FOR UPDATE/SHARE</literal> clause) sees only data
committed before the query began; it never sees either uncommitted
data or changes committed during query execution by concurrent
transactions. In effect, a <command>SELECT</command> query sees
@@ -336,10 +336,10 @@
The <command>DELETE</command> will have no effect even though
there is a <literal>website.hits = 10</literal> row before and
after the <command>UPDATE</command>. This occurs because the
- pre-update row value <literal>9</> is skipped, and when the
+ pre-update row value <literal>9</literal> is skipped, and when the
<command>UPDATE</command> completes and <command>DELETE</command>
- obtains a lock, the new row value is no longer <literal>10</> but
- <literal>11</>, which no longer matches the criteria.
+ obtains a lock, the new row value is no longer <literal>10</literal> but
+ <literal>11</literal>, which no longer matches the criteria.
</para>
<para>
@@ -347,7 +347,7 @@
that includes all transactions committed up to that instant,
subsequent commands in the same transaction will see the effects
of the committed concurrent transaction in any case. The point
- at issue above is whether or not a <emphasis>single</> command
+ at issue above is whether or not a <emphasis>single</emphasis> command
sees an absolutely consistent view of the database.
</para>
Modified: traduc/trunk/postgresql/pageinspect.xml
===================================================================
--- traduc/trunk/postgresql/pageinspect.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/pageinspect.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -202,7 +202,7 @@
next slot to be returned from the page, is also printed.
</para>
<para>
- See <filename>src/backend/storage/freespace/README</> for more
+ See <filename>src/backend/storage/freespace/README</filename> for more
information on the structure of an FSM page.
</para>
</listitem>
Modified: traduc/trunk/postgresql/pgbench.xml
===================================================================
--- traduc/trunk/postgresql/pgbench.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/pgbench.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -108,7 +108,7 @@
Dans la plupart des cas, vous aurez besoin de quelques options pour que
ce test soit réellement intéressant. Les options les plus importantes
sont <literal>-c</literal> (nombre de clients), <literal>-t</literal>
- (nombre de transactions), <literal>-T</> (time limit) et <literal>-f</literal> (pour spécifier un script
+ (nombre de transactions), <literal>-T</literal> (time limit) et <literal>-f</literal> (pour spécifier un script
personnalisé). Voir ci-dessous pour une liste complète.
</para>
@@ -183,28 +183,28 @@
</entry>
</row>
<row>
- <entry><literal>-T</literal> <replaceable>seconds</></entry>
+ <entry><literal>-T</literal> <replaceable>seconds</replaceable></entry>
<entry>
Duration of benchmark test in seconds. <literal>-t</literal> and
<literal>-T</literal> are mutually exclusive.
</entry>
</row>
<row>
- <entry><literal>-M</literal> <replaceable>querymode</></entry>
+ <entry><literal>-M</literal> <replaceable>querymode</replaceable></entry>
<entry>
Protocol to use for submitting queries for the server:
<itemizedlist>
<listitem>
- <para><literal>simple</>: use simple query protocol.</para>
+ <para><literal>simple</literal>: use simple query protocol.</para>
</listitem>
<listitem>
- <para><literal>extended</>: use extended query protocol.</para>
+ <para><literal>extended</literal>: use extended query protocol.</para>
</listitem>
<listitem>
- <para><literal>prepared</>: use extended query protocol with prepared statements.</para>
+ <para><literal>prepared</literal>: use extended query protocol with prepared statements.</para>
</listitem>
</itemizedlist>
- The default is simple query protocol. (See <xref linkend="protocol">
+ The default is simple query protocol. (See <xref linkend="protocol"/>
for more information.)
</entry>
</row>
@@ -544,7 +544,8 @@
<para>
En premier lieu, ne <emphasis>jamais</emphasis> croire tout test qui ne
- s'exécute que pendant quelques secondes. Use the <literal>-t</> or <literal>-T</> option
+ s'exécute que pendant quelques secondes. Use the <literal>-t</literal> or
+ <literal>-T</literal> option
pour que le test dure plusieurs minutes pour rendre
le bruit insignifiant. Dans certains cas, nous avez besoin de quelques
heures pour obtenir des chiffres reproductibles. Exécuter le test plusieurs
Modified: traduc/trunk/postgresql/pgfreespacemap.xml
===================================================================
--- traduc/trunk/postgresql/pgfreespacemap.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/pgfreespacemap.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -8,7 +8,7 @@
</indexterm>
<para>
- The <filename>pg_freespacemap</> module provides a means for examining the
+ The <filename>pg_freespacemap</filename> module provides a means for examining the
free space map (FSM). It provides a function called
<function>pg_freespace</function>, or two overloaded functions, to be
precise. The functions show the value recorded in the free space map for
@@ -32,7 +32,7 @@
<listitem>
<para>
Returns the amount of free space on the page of the relation, specified
- by <literal>blkno</>, according to the FSM.
+ by <literal>blkno</literal>, according to the FSM.
(blkno).
</para>
</listitem>
@@ -47,7 +47,8 @@
<listitem>
<para>
Displays the the amount of free space on each page of the relation,
- according to the FSM. A set of <literal>(blkno bigint, avail int2)</>
+ according to the FSM. A set of <literal>(blkno bigint, avail
+ int2)</literal>
tuples is returned, one tuple for each page in the relation.
</para>
</listitem>
Modified: traduc/trunk/postgresql/pgstandby.xml
===================================================================
--- traduc/trunk/postgresql/pgstandby.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/pgstandby.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -313,11 +313,11 @@
</itemizedlist>
<para>
- The <literal>copy</> command on Windows sets the final file size
+ The <literal>copy</literal> command on Windows sets the final file size
before the file is completely copied, which would ordinarly confuse
<application>pg_standby</application>. Therefore
- <application>pg_standby</application> waits <literal>sleeptime</>
- seconds once it sees the proper file size. GNUWin32's <literal>cp</>
+ <application>pg_standby</application> waits <literal>sleeptime</literal>
+ seconds once it sees the proper file size. GNUWin32's <literal>cp</literal>
sets the file size only after the file copy is complete.
</para>
Modified: traduc/trunk/postgresql/pgstatstatements.xml
===================================================================
--- traduc/trunk/postgresql/pgstatstatements.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/pgstatstatements.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -13,9 +13,9 @@
</para>
<para>
- The module must be loaded by adding <literal>pg_stat_statements</> to
- <xref linkend="guc-shared-preload-libraries"> in
- <filename>postgresql.conf</>, because it requires additional shared memory.
+ The module must be loaded by adding <literal>pg_stat_statements</literal> to
+ <xref linkend="guc-shared-preload-libraries"/> in
+ <filename>postgresql.conf</filename>, because it requires additional shared memory.
This means that a server restart is needed to add or remove the module.
</para>
@@ -24,14 +24,14 @@
<para>
The statistics gathered by the module are made available via a system view
- named <structname>pg_stat_statements</>. This view contains one row for
+ named <structname>pg_stat_statements</structname>. This view contains one row for
each distinct query text, database ID, and user ID (up to the maximum
number of distinct statements that the module can track). The columns
of the view are:
</para>
<table>
- <title><structname>pg_stat_statements</> columns</title>
+ <title><structname>pg_stat_statements</structname> columns</title>
<tgroup cols="4">
<thead>
@@ -61,7 +61,7 @@
<entry><structfield>query</structfield></entry>
<entry><type>text</type></entry>
<entry></entry>
- <entry>Text of the statement (up to <xref linkend="guc-track-activity-query-size"> bytes)</entry>
+ <entry>Text of the statement (up to <xref linkend="guc-track-activity-query-size"/> bytes)</entry>
</row>
<row>
@@ -90,9 +90,9 @@
</table>
<para>
- This view, and the function <function>pg_stat_statements_reset</>,
+ This view, and the function <function>pg_stat_statements_reset</function>,
are available only in databases they have been specifically installed into
- by running the <filename>pg_stat_statements.sql</> install script.
+ by running the <filename>pg_stat_statements.sql</filename> install script.
However, statistics are tracked across all databases of the server
whenever the <filename>pg_stat_statements</filename> module is loaded
into the server, regardless of presence of the view.
@@ -124,7 +124,7 @@
<listitem>
<para>
<function>pg_stat_statements_reset</function> discards all statistics
- gathered so far by <filename>pg_stat_statements</>.
+ gathered so far by <filename>pg_stat_statements</filename>.
By default, this function can only be executed by superusers.
</para>
</listitem>
@@ -146,7 +146,7 @@
<para>
<varname>pg_stat_statements.max</varname> is the maximum number of
statements tracked by the module (i.e., the maximum number of rows
- in the <structname>pg_stat_statements</> view). If more distinct
+ in the <structname>pg_stat_statements</structname> view). If more distinct
statements than that are observed, information about the least-executed
statements is discarded.
The default value is 1000.
@@ -164,11 +164,11 @@
<para>
<varname>pg_stat_statements.track</varname> controls which statements
are counted by the module.
- Specify <literal>top</> to track top-level statements (those issued
- directly by clients), <literal>all</> to also track nested statements
- (such as statements invoked within functions), or <literal>none</> to
+ Specify <literal>top</literal> to track top-level statements (those issued
+ directly by clients), <literal>all</literal> to also track nested statements
+ (such as statements invoked within functions), or <literal>none</literal> to
disable.
- The default value is <literal>top</>.
+ The default value is <literal>top</literal>.
Only superusers can change this setting.
</para>
</listitem>
@@ -183,10 +183,11 @@
<para>
<varname>pg_stat_statements.save</varname> specifies whether to
save statement statistics across server shutdowns.
- If it is <literal>off</> then statistics are not saved at
+ If it is <literal>off</literal> then statistics are not saved at
shutdown nor reloaded at server start.
- The default value is <literal>on</>.
- This parameter can only be set in the <filename>postgresql.conf</>
+ The default value is <literal>on</literal>.
+ This parameter can only be set in the
+ <filename>postgresql.conf</filename>
file or on the server command line.
</para>
</listitem>
@@ -195,17 +196,18 @@
<para>
The module requires additional shared memory amounting to about
- <varname>pg_stat_statements.max</varname> <literal>*</>
- <xref linkend="guc-track-activity-query-size"> bytes. Note that this
+ <varname>pg_stat_statements.max</varname> <literal>*</literal>
+ <xref linkend="guc-track-activity-query-size"/> bytes. Note that this
memory is consumed whenever the module is loaded, even if
- <varname>pg_stat_statements.track</> is set to <literal>none</>.
+ <varname>pg_stat_statements.track</varname> is set to
+ <literal>none</literal>.
</para>
<para>
In order to set any of these parameters in your
- <filename>postgresql.conf</> file,
- you will need to add <literal>pg_stat_statements</> to
- <xref linkend="guc-custom-variable-classes">. Typical usage might be:
+ <filename>postgresql.conf</filename> file,
+ you will need to add <literal>pg_stat_statements</literal> to
+ <xref linkend="guc-custom-variable-classes"/>. Typical usage might be:
</para>
<programlisting>
Modified: traduc/trunk/postgresql/plperl.xml
===================================================================
--- traduc/trunk/postgresql/plperl.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/plperl.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -724,8 +724,9 @@
<term><literal>$_TD->{event}</literal></term>
<listitem>
<para>
- Événement du déclencheur : <literal>INSERT</>, <literal>UPDATE</>,
- <literal>DELETE</>, <literal>TRUNCATE</> ou <literal>UNKNOWN</>
+ Événement du déclencheur : <literal>INSERT</literal>,
+ <literal>UPDATE</literal>, <literal>DELETE</literal>,
+ <literal>TRUNCATE</literal> ou <literal>UNKNOWN</literal>
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/plpgsql.xml
===================================================================
--- traduc/trunk/postgresql/plpgsql.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/plpgsql.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -56,10 +56,10 @@
</para>
<para>
- <application>PL/pgSQL</> functions can be declared to accept a variable
- number of arguments by using the <literal>VARIADIC</> marker. This
+ <application>PL/pgSQL</application> functions can be declared to accept a variable
+ number of arguments by using the <literal>VARIADIC</literal> marker. This
works exactly the same way as for SQL functions, as discussed in
- <xref linkend="xfunc-sql-variadic-functions">.
+ <xref linkend="xfunc-sql-variadic-functions"/>.
</para>
<para>
@@ -168,8 +168,8 @@
du code de retour. Ceci n'ajoute pas de fonctionnalité fondamentale au
langage mais c'est un moyen agréable principalement pour renvoyer
plusieurs valeurs.
- The <literal>RETURNS TABLE</> notation can also be used in place
- of <literal>RETURNS SETOF</>.
+ The <literal>RETURNS TABLE</literal> notation can also be used in place
+ of <literal>RETURNS SETOF</literal>.
</para>
<para>
@@ -309,7 +309,8 @@
dans la section déclaration du bloc.
Les seules exceptions sont que la variable de boucle d'une boucle <literal>FOR</literal>
effectuant une itération sur des valeurs entières est automatiquement déclarée
- comme variable entière (type integer), and likewise the loop variable of a <literal>FOR</> loop
+ comme variable entière (type integer), and likewise the loop variable of
+ a <literal>FOR</literal> loop
iterating over a cursor's result is automatically declared as a
record variable.
</para>
@@ -475,7 +476,7 @@
<para>
Another way to declare a <application>PL/pgSQL</application> function
- is with <literal>RETURNS TABLE</>, for example:
+ is with <literal>RETURNS TABLE</literal>, for example:
<programlisting>
CREATE FUNCTION extended_sales(p_itemno int) RETURNS TABLE(quantity int, total numeric) AS $$
@@ -485,9 +486,10 @@
$$ LANGUAGE plpgsql;
</programlisting>
- This is exactly equivalent to declaring one or more <literal>OUT</>
+ This is exactly equivalent to declaring one or more
+ <literal>OUT</literal>
parameters and specifying <literal>RETURNS SETOF
- <replaceable>sometype</></literal>.
+ <replaceable>sometype</replaceable></literal>.
</para>
<para>
@@ -1024,7 +1026,7 @@
The optional <replaceable>cible</replaceable> est une variable record ou ligne ou
même une liste de variables simples ou de champs de lignes/enregistrements
séparées par des virgules, into which the results of
- the command will be stored. The optional <literal>USING</> expressions
+ the command will be stored. The optional <literal>USING</literal> expressions
supply values to be inserted into the command.
</para>
@@ -1065,8 +1067,8 @@
<para>
The command string can use parameter values, which are referenced
- in the command as <literal>$1</>, <literal>$2</>, etc.
- These symbols refer to values supplied in the <literal>USING</>
+ in the command as <literal>$1</literal>, <literal>$2</literal>, etc.
+ These symbols refer to values supplied in the <literal>USING</literal>
clause. This method is often preferable to inserting data values
into the command string as text: it avoids run-time overhead of
converting the values to text and back, and it is much less prone
@@ -1093,17 +1095,17 @@
</para>
<para>
- An <command>EXECUTE</> with a simple constant command string and some
- <literal>USING</> parameters, as in the first example above, is
+ An <command>EXECUTE</command> with a simple constant command string and some
+ <literal>USING</literal> parameters, as in the first example above, is
functionally equivalent to just writing the command directly in
<application>PL/pgSQL</application> and allowing replacement of
<application>PL/pgSQL</application> variables to happen automatically.
- The important difference is that <command>EXECUTE</> will re-plan
+ The important difference is that <command>EXECUTE</command> will re-plan
the command on each execution, generating a plan that is specific
to the current parameter values; whereas
<application>PL/pgSQL</application> normally creates a generic plan
and caches it for re-use. In situations where the best plan depends
- strongly on the parameter values, <command>EXECUTE</> can be
+ strongly on the parameter values, <command>EXECUTE</command> can be
significantly faster; while when the plan is not sensitive to parameter
values, re-planning will be a waste.
</para>
@@ -1172,7 +1174,7 @@
<para>
Cet exemple démontre l'utilisation des fonctions
<function>quote_ident</function> et <function>quote_literal</function> (see <xref
- linkend="functions-string">).
+ linkend="functions-string"/>).
Pour plus de sûreté, les expressions contenant
les identifiants des colonnes et des tables doivent être passées à la
fonction <function>quote_ident</function> before insertion in a dynamic query. Les expressions contenant des
@@ -1185,12 +1187,13 @@
<para>
Because <function>quote_literal</function> is labelled
<literal>STRICT</literal>, it will always return null when called with a
- null argument. In the above example, if <literal>newvalue</> or
- <literal>keyvalue</> were null, the entire dynamic query string would
+ null argument. In the above example, if <literal>newvalue</literal> or
+ <literal>keyvalue</literal> were null, the entire dynamic query string would
become null, leading to an error from <command>EXECUTE</command>.
- You can avoid this problem by using the <function>quote_nullable</>
- function, which works the same as <function>quote_literal</> except that
- when called with a null argument it returns the string <literal>NULL</>.
+ You can avoid this problem by using the <function>quote_nullable</function>
+ function, which works the same as <function>quote_literal</function> except that
+ when called with a null argument it returns the string
+ <literal>NULL</literal>.
For example,
<programlisting>
EXECUTE 'UPDATE tbl SET '
@@ -1201,26 +1204,27 @@
|| quote_nullable(keyvalue);
</programlisting>
If you are dealing with values that might be null, you should usually
- use <function>quote_nullable</> in place of <function>quote_literal</>.
+ use <function>quote_nullable</function> in place of
+ <function>quote_literal</function>.
</para>
<para>
As always, care must be taken to ensure that null values in a query do
- not deliver unintended results. For example the <literal>WHERE</> clause
+ not deliver unintended results. For example the <literal>WHERE</literal> clause
<programlisting>
'WHERE key = ' || quote_nullable(keyvalue)
</programlisting>
- will never succeed if <literal>keyvalue</> is null, because the
- result of using the equality operator <literal>=</> with a null operand
+ will never succeed if <literal>keyvalue</literal> is null, because the
+ result of using the equality operator <literal>=</literal> with a null operand
is always null. If you wish null to work like an ordinary key value,
you would need to rewrite the above as
<programlisting>
'WHERE key IS NOT DISTINCT FROM ' || quote_nullable(keyvalue)
</programlisting>
- (At present, <literal>IS NOT DISTINCT FROM</> is handled much less
- efficiently than <literal>=</>, so don't do this unless you must.
- See <xref linkend="functions-comparison"> for
- more information on nulls and <literal>IS DISTINCT</>.)
+ (At present, <literal>IS NOT DISTINCT FROM</literal> is handled much less
+ efficiently than <literal>=</literal>, so don't do this unless you must.
+ See <xref linkend="functions-comparison"/> for
+ more information on nulls and <literal>IS DISTINCT</literal>.)
</para>
<para>
@@ -1238,7 +1242,7 @@
que vous pourriez choisir. Donc, pour mettre un texte inconnu entre
guillemets de façon sûr, vous <emphasis>devez</emphasis> utiliser
<function>quote_literal</function>,
- <function>quote_nullable</>, or <function>quote_ident</>, as appropriate.
+ <function>quote_nullable</function>, or <function>quote_ident</function>, as appropriate.
</para>
</example>
@@ -1327,7 +1331,7 @@
<command>FOR</command> (boucles <command>FOR</command> integer,
<command>FOR</command> record-set,
et <command>FOR</command> record-set dynamique and cursor
- <command>FOR</> loops). <literal>FOUND</literal>
+ <command>FOR</command> loops). <literal>FOUND</literal>
n'est positionnée de cette façon que quand la boucle <command>FOR</command>
s'achève ;
dans l'exécution de la chaîne, <literal>FOUND</literal>
@@ -1510,8 +1514,8 @@
<command>RETURN QUERY</command> has a variant
<command>RETURN QUERY EXECUTE</command>, which specifies the
query to be executed dynamically. Parameter expressions can
- be inserted into the computed query string via <literal>USING</>,
- in just the same way as in the <command>EXECUTE</> command.
+ be inserted into the computed query string via <literal>USING</literal>,
+ in just the same way as in the <command>EXECUTE</command> command.
</para>
<para>
@@ -1584,7 +1588,7 @@
<title>Contrôles conditionnels</title>
<para>
- Les instructions <command>IF</> et <command>CASE</> vous permettent d'exécuter des commandes
+ Les instructions <command>IF</command> et <command>CASE</command> vous permettent d'exécuter des commandes
basées sur certaines conditions. <application>PL/pgSQL</application> a trois formes de
<literal>IF</literal> :
<itemizedlist>
@@ -1599,13 +1603,13 @@
</listitem>
</itemizedlist>
- and two forms of <command>CASE</>:
+ and two forms of <command>CASE</command>:
<itemizedlist>
<listitem>
- <para><literal>CASE ... WHEN ... THEN ... ELSE ... END CASE</></>
+ <para><literal>CASE ... WHEN ... THEN ... ELSE ... END CASE</literal></para>
</listitem>
<listitem>
- <para><literal>CASE WHEN ... THEN ... ELSE ... END CASE</></>
+ <para><literal>CASE WHEN ... THEN ... ELSE ... END CASE</literal></para>
</listitem>
</itemizedlist>
</para>
@@ -1690,15 +1694,16 @@
<para>
Sometimes there are more than just two alternatives.
- <literal>IF-THEN-ELSIF</> provides a convenient
+ <literal>IF-THEN-ELSIF</literal> provides a convenient
method of checking several alternatives in turn.
- The <literal>IF</> conditions are tested successively
+ The <literal>IF</literal> conditions are tested successively
until the first one that is true is found. Then the
associated statement(s) are executed, after which control
- passes to the next statement after <literal>END IF</>.
- (Any subsequent <literal>IF</> conditions are <emphasis>not</>
- tested.) If none of the <literal>IF</> conditions is true,
- then the <literal>ELSE</> block (if any) is executed.
+ passes to the next statement after <literal>END IF</literal>.
+ (Any subsequent <literal>IF</literal> conditions are
+ <emphasis>not</emphasis>
+ tested.) If none of the <literal>IF</literal> conditions is true,
+ then the <literal>ELSE</literal> block (if any) is executed.
</para>
<para>
@@ -1718,8 +1723,8 @@
</para>
<para>
- The key word <literal>ELSIF</> can also be spelled
- <literal>ELSEIF</>.
+ The key word <literal>ELSIF</literal> can also be spelled
+ <literal>ELSEIF</literal>.
</para>
<para>
@@ -1739,14 +1744,15 @@
</para>
<para>
- However, this method requires writing a matching <literal>END IF</>
- for each <literal>IF</>, so it is much more cumbersome than
- using <literal>ELSIF</> when there are many alternatives.
+ However, this method requires writing a matching <literal>END
+ IF</literal>
+ for each <literal>IF</literal>, so it is much more cumbersome than
+ using <literal>ELSIF</literal> when there are many alternatives.
</para>
</sect3>
<sect3>
- <title>Simple <literal>CASE</></title>
+ <title>Simple <literal>CASE</literal></title>
<synopsis>
CASE <replaceable>search-expression</replaceable>
@@ -1761,16 +1767,16 @@
</synopsis>
<para>
- The simple form of <command>CASE</> provides conditional execution
- based on equality of operands. The <replaceable>search-expression</>
+ The simple form of <command>CASE</command> provides conditional execution
+ based on equality of operands. The <replaceable>search-expression</replaceable>
is evaluated (once) and successively compared to each
- <replaceable>expression</> in the <literal>WHEN</> clauses.
+ <replaceable>expression</replaceable> in the <literal>WHEN</literal> clauses.
If a match is found, then the corresponding
<replaceable>statements</replaceable> are executed, and then control
- passes to the next statement after <literal>END CASE</>. (Subsequent
- <literal>WHEN</> expressions are not evaluated.) If no match is
- found, the <literal>ELSE</> <replaceable>statements</replaceable> are
- executed; but if <literal>ELSE</> is not present, then a
+ passes to the next statement after <literal>END CASE</literal>. (Subsequent
+ <literal>WHEN</literal> expressions are not evaluated.) If no match is
+ found, the <literal>ELSE</literal> <replaceable>statements</replaceable> are
+ executed; but if <literal>ELSE</literal> is not present, then a
<literal>CASE_NOT_FOUND</literal> exception is raised.
</para>
@@ -1789,7 +1795,7 @@
</sect3>
<sect3>
- <title>Searched <literal>CASE</></title>
+ <title>Searched <literal>CASE</literal></title>
<synopsis>
CASE
@@ -1804,16 +1810,17 @@
</synopsis>
<para>
- The searched form of <command>CASE</> provides conditional execution
- based on truth of boolean expressions. Each <literal>WHEN</> clause's
+ The searched form of <command>CASE</command> provides conditional execution
+ based on truth of boolean expressions. Each <literal>WHEN</literal> clause's
<replaceable>boolean-expression</replaceable> is evaluated in turn,
- until one is found that yields <literal>true</>. Then the
+ until one is found that yields <literal>true</literal>. Then the
corresponding <replaceable>statements</replaceable> are executed, and
- then control passes to the next statement after <literal>END CASE</>.
- (Subsequent <literal>WHEN</> expressions are not evaluated.)
- If no true result is found, the <literal>ELSE</>
+ then control passes to the next statement after <literal>END
+ CASE</literal>.
+ (Subsequent <literal>WHEN</literal> expressions are not evaluated.)
+ If no true result is found, the <literal>ELSE</literal>
<replaceable>statements</replaceable> are executed;
- but if <literal>ELSE</> is not present, then a
+ but if <literal>ELSE</literal> is not present, then a
<literal>CASE_NOT_FOUND</literal> exception is raised.
</para>
@@ -1831,9 +1838,9 @@
</para>
<para>
- This form of <command>CASE</> is entirely equivalent to
- <literal>IF-THEN-ELSIF</>, except for the rule that reaching
- an omitted <literal>ELSE</> clause results in an error rather
+ This form of <command>CASE</command> is entirely equivalent to
+ <literal>IF-THEN-ELSIF</literal>, except for the rule that reaching
+ an omitted <literal>ELSE</literal> clause results in an error rather
than doing nothing.
</para>
@@ -2145,13 +2152,13 @@
flexibilité d'une requête dynamique, uniquement avec l'instruction
<command>EXECUTE</command>.
As with <command>EXECUTE</command>, parameter values can be inserted
- into the dynamic command via <literal>USING</>.
+ into the dynamic command via <literal>USING</literal>.
</para>
<para>
Another way to specify the query whose results should be iterated
through is to declare it as a cursor. This is described in
- <xref linkend="plpgsql-cursor-for-loop">.
+ <xref linkend="plpgsql-cursor-for-loop"/>.
</para>
</sect2>
@@ -2213,7 +2220,7 @@
<literal>QUERY_CANCELED</literal> (il est possible, mais pas recommandé, de
récupérer <literal>QUERY_CANCELED</literal> par son nom). Les noms des
conditions ne sont pas sensibles à la casse. Also, an error condition can be specified
- by <literal>SQLSTATE</> code; for example these are equivalent:
+ by <literal>SQLSTATE</literal> code; for example these are equivalent:
<programlisting>
WHEN division_by_zero THEN ...
WHEN SQLSTATE '22012' THEN ...
@@ -2394,8 +2401,8 @@
<note>
<para>
Bound cursors can also be used without explicitly opening them,
- via the <command>FOR</> statement described in
- <xref linkend="plpgsql-cursor-for-loop">.
+ via the <command>FOR</command> statement described in
+ <xref linkend="plpgsql-cursor-for-loop"/>.
</para>
</note>
@@ -2629,7 +2636,7 @@
peut être mise à jour ou supprimée en utilisant le curseur qui identifie
la ligne. There are
restrictions on what the cursor's query can be (in particular,
- no grouping) and it's best to use <literal>FOR UPDATE</> in the
+ no grouping) and it's best to use <literal>FOR UPDATE</literal> in the
cursor. Pour des informations
supplémentaires, voir la page de référence
<xref linkend="sql-declare" endterm="sql-declare-title"/>.
@@ -2776,7 +2783,7 @@
<title>Looping Through a Cursor's Result</title>
<para>
- There is a variant of the <command>FOR</> statement that allows
+ There is a variant of the <command>FOR</command> statement that allows
iterating through the rows returned by a cursor. The syntax is:
<synopsis>
@@ -2787,14 +2794,14 @@
</synopsis>
The cursor variable must have been bound to some query when it was
- declared, and it <emphasis>cannot</> be open already. The
- <command>FOR</> statement automatically opens the cursor, and it closes
+ declared, and it <emphasis>cannot</emphasis> be open already. The
+ <command>FOR</command> statement automatically opens the cursor, and it closes
the cursor again when the loop exits. A list of actual argument value
expressions must appear if and only if the cursor was declared to take
arguments. These values will be substituted in the query, in just
- the same way as during an <command>OPEN</>.
+ the same way as during an <command>OPEN</command>.
The variable <replaceable>recordvar</replaceable> is automatically
- defined as type <type>record</> and exists only inside the loop (any
+ defined as type <type>record</type> and exists only inside the loop (any
existing definition of the variable name is ignored within the loop).
Each row returned by the cursor is successively assigned to this
record variable and the loop body is executed.
@@ -2820,8 +2827,8 @@
lever des erreurs.
<synopsis>RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> '<replaceable class="parameter">format</replaceable>' <optional>, <replaceable class="parameter">expression</replaceable> <optional>, ...</optional></optional> <optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional> </optional>;
-RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> <replaceable class="parameter">condition_name</> <optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional> </optional>;
-RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> SQLSTATE '<replaceable class="parameter">sqlstate</>' <optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional> </optional>;
+RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> <replaceable class="parameter">condition_name</replaceable> <optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional> </optional>;
+RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> SQLSTATE '<replaceable class="parameter">sqlstate</replaceable>' <optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional> </optional>;
RAISE <optional> <replaceable class="parameter">level</replaceable> </optional> USING <replaceable class="parameter">option</replaceable> = <replaceable class="parameter">expression</replaceable> <optional>, ... </optional>;
RAISE ;
</synopsis>
@@ -2861,21 +2868,22 @@
<para>
You can attach additional information to the error report by writing
- <literal>USING</> followed by <replaceable
+ <literal>USING</literal> followed by <replaceable
class="parameter">option</replaceable> = <replaceable
class="parameter">expression</replaceable> items. The allowed
<replaceable class="parameter">option</replaceable> keywords are
- <literal>MESSAGE</>, <literal>DETAIL</>, <literal>HINT</>, and
- <literal>ERRCODE</>, while each <replaceable
+ <literal>MESSAGE</literal>, <literal>DETAIL</literal>,
+ <literal>HINT</literal>, and
+ <literal>ERRCODE</literal>, while each <replaceable
class="parameter">expression</replaceable> can be any string-valued
expression.
- <literal>MESSAGE</> sets the error message text (this option can't
- be used in the form of <command>RAISE</> that includes a format
- string before <literal>USING</>).
- <literal>DETAIL</> supplies an error detail message, while
- <literal>HINT</> supplies a hint message.
- <literal>ERRCODE</> specifies the error code (SQLSTATE) to report,
- either by condition name as shown in <xref linkend="errcodes-appendix">,
+ <literal>MESSAGE</literal> sets the error message text (this option can't
+ be used in the form of <command>RAISE</command> that includes a format
+ string before <literal>USING</literal>).
+ <literal>DETAIL</literal> supplies an error detail message, while
+ <literal>HINT</literal> supplies a hint message.
+ <literal>ERRCODE</literal> specifies the error code (SQLSTATE) to report,
+ either by condition name as shown in <xref linkend="errcodes-appendix"/>,
or directly as a five-character SQLSTATE code.
</para>
@@ -2896,13 +2904,13 @@
</para>
<para>
- There is a second <command>RAISE</> syntax in which the main argument
+ There is a second <command>RAISE</command> syntax in which the main argument
is the condition name or SQLSTATE to be reported, for example:
<programlisting>
RAISE division_by_zero;
RAISE SQLSTATE '22012';
</programlisting>
- In this syntax, <literal>USING</> can be used to supply a custom
+ In this syntax, <literal>USING</literal> can be used to supply a custom
error message, detail, or hint. Another way to do the earlier
example is
<programlisting>
@@ -2911,15 +2919,15 @@
</para>
<para>
- Still another variant is to write <literal>RAISE USING</> or <literal>RAISE
- <replaceable class="parameter">level</replaceable> USING</> and put
- everything else into the <literal>USING</> list.
+ Still another variant is to write <literal>RAISE USING</literal> or <literal>RAISE
+ <replaceable class="parameter">level</replaceable> USING</literal> and put
+ everything else into the <literal>USING</literal> list.
</para>
<para>
- The last variant of <command>RAISE</> has no parameters at all.
- This form can only be used inside a <literal>BEGIN</> block's
- <literal>EXCEPTION</> clause;
+ The last variant of <command>RAISE</command> has no parameters at all.
+ This form can only be used inside a <literal>BEGIN</literal> block's
+ <literal>EXCEPTION</literal> clause;
it causes the error currently being handled to be re-thrown to the
next enclosing block.
</para>
@@ -2927,7 +2935,7 @@
<para>
If no condition name nor SQLSTATE is specified in a
<command>RAISE EXCEPTION</command> command, the default is to use
- <literal>RAISE_EXCEPTION</> (<literal>P0001</>). If no message
+ <literal>RAISE_EXCEPTION</literal> (<literal>P0001</literal>). If no message
text is specified, the default is to use the condition name or
SQLSTATE as message text.
</para>
@@ -2937,7 +2945,7 @@
When specifying an error code by SQLSTATE code, you are not
limited to the predefined error codes, but can select any
error code consisting of five digits and/or upper-case ASCII
- letters, other than <literal>00000</>. It is recommended that
+ letters, other than <literal>00000</literal>. It is recommended that
you avoid throwing error codes that end in three zeroes, because
these are category codes and can only be trapped by trapping
the whole category.
@@ -3030,7 +3038,8 @@
<listitem>
<para>
Type de données <type>text</type> ; une chaîne, <literal>INSERT</literal>,
- <literal>UPDATE</literal>, <literal>DELETE</literal> ou <literal>TRUNCATE</>,
+ <literal>UPDATE</literal>, <literal>DELETE</literal> ou
+ <literal>TRUNCATE</literal>
indiquant pour quelle opération le trigger a été lancé.
</para>
</listitem>
@@ -4037,9 +4046,9 @@
<listitem>
<para>
- <command>FOR</> loops over queries (other than cursors) also work
+ <command>FOR</command> loops over queries (other than cursors) also work
differently: the target variable(s) must have been declared,
- whereas <application>PL/SQL</> always declares them implicitly.
+ whereas <application>PL/SQL</application> always declares them implicitly.
An advantage of this is that the variable values are still accessible
after the loop exits.
</para>
@@ -4448,7 +4457,8 @@
<callout arearefs="co.plpgsql-porting-raise">
<para>
La syntaxe de <literal>RAISE</literal> est considérablement différente de
- l'instruction Oracle similaire., although the basic case <literal>RAISE</>
+ l'instruction Oracle similaire., although the basic case
+ <literal>RAISE</literal>
<replaceable class="parameter">exception_name</replaceable> works
similarly.
</para>
Modified: traduc/trunk/postgresql/plpython.xml
===================================================================
--- traduc/trunk/postgresql/plpython.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/plpython.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -383,13 +383,13 @@
<literal>TD</literal> contient des valeurs relatives au déclencheur.
<literal>TD["event"]</literal> contient l'événement en tant que chaîne
(<literal>INSERT</literal>, <literal>UPDATE</literal>,
- <literal>DELETE</literal>, <literal>TRUNCATE</> ou <literal>UNKNOWN</literal>).
+ <literal>DELETE</literal>, <literal>TRUNCATE</literal> ou <literal>UNKNOWN</literal>).
<literal>TD["when"]</literal> contient soit <literal>BEFORE</literal>, soit
<literal>AFTER</literal> soit <literal>UNKNOWN</literal>.
<literal>TD["level"]</literal> contient une valeur parmi <literal>ROW</literal>,
<literal>STATEMENT</literal> et <literal>UNKNOWN</literal>.
For a row-level trigger, the trigger
- rows are in <literal>TD["new"]</> and/or <literal>TD["old"]</>
+ rows are in <literal>TD["new"]</literal> and/or <literal>TD["old"]</literal>
depending on the trigger event.
<literal>TD["name"]</literal> contient le nom du déclencheur,
<literal>TD["table_name"]</literal> contient le nom de la table pour laquelle
@@ -405,7 +405,7 @@
<para>
Si <literal>TD["when"]</literal> vaut <literal>BEFORE</literal> and
- <literal>TD["level"]</literal> is <literal>ROW</>, vous pourriez
+ <literal>TD["level"]</literal> is <literal>ROW</literal>, vous pourriez
renvoyer <literal>None</literal> ou <literal>"OK"</literal> à partir de la
fonction Python pour indiquer que la ligne n'est pas modifiée,
<literal>"SKIP"</literal> pour annuler l'événement ou <literal>"MODIFY"</literal> pour
Modified: traduc/trunk/postgresql/pltcl.xml
===================================================================
--- traduc/trunk/postgresql/pltcl.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/pltcl.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -588,7 +588,7 @@
<term><varname>$TG_op</varname></term>
<listitem>
<para>
- La chaîne <literal>INSERT<literal/>, <literal>UPDATE</literal>,
+ La chaîne <literal>INSERT</literal>, <literal>UPDATE</literal>,
<literal>DELETE</literal> ou <literal>TRUNCATE</literal> suivant le
type de l'événement du déclencheur.
</para>
Modified: traduc/trunk/postgresql/queries.xml
===================================================================
--- traduc/trunk/postgresql/queries.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/queries.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -35,7 +35,7 @@
<optional>WITH <replaceable>with_requêtes</replaceable></optional> SELECT <replaceable>liste_select</replaceable> FROM <replaceable>expression_table</replaceable> <optional><replaceable>specification_tri</replaceable></optional>
</synopsis>
Les sections suivantes décrivent le détail de la liste de sélection,
- l'expression des tables et la spécification du tri. <literal>WITH</>
+ l'expression des tables et la spécification du tri. <literal>WITH</literal>
queries are treated last since they are an advanced feature.
</para>
@@ -935,53 +935,55 @@
</para>
<para>
- If a query contains aggregate function calls, but no <literal>GROUP BY</>
+ If a query contains aggregate function calls, but no <literal>GROUP
+ BY</literal>
clause, grouping still occurs: the result is a single group row (or
perhaps no rows at all, if the single row is then eliminated by
- <literal>HAVING</>).
- The same is true if it contains a <literal>HAVING</> clause, even
- without any aggregate function calls or <literal>GROUP BY</> clause.
+ <literal>HAVING</literal>).
+ The same is true if it contains a <literal>HAVING</literal> clause, even
+ without any aggregate function calls or <literal>GROUP BY</literal> clause.
</para>
</sect2>
<sect2 id="queries-window">
- <title>Window Function Processing</>
+ <title>Window Function Processing</title>
<indexterm zone="queries-window">
<primary>window function</primary>
- <secondary>order of execution</>
+ <secondary>order of execution</secondary>
</indexterm>
<para>
If the query contains any window functions (see
- <xref linkend="tutorial-window"> and
- <xref linkend="syntax-window-functions">), these functions are evaluated
- after any grouping, aggregation, and <literal>HAVING</> filtering is
+ <xref linkend="tutorial-window"/> and
+ <xref linkend="syntax-window-functions"/>), these functions are evaluated
+ after any grouping, aggregation, and <literal>HAVING</literal> filtering is
performed. That is, if the query uses any aggregates, <literal>GROUP
- BY</>, or <literal>HAVING</>, then the rows seen by the window functions
+ BY</literal>, or <literal>HAVING</literal>, then the rows seen by the window functions
are the group rows instead of the original table rows from
- <literal>FROM</>/<literal>WHERE</>.
+ <literal>FROM</literal>/<literal>WHERE</literal>.
</para>
<para>
When multiple window functions are used, all the window functions having
- syntactically equivalent <literal>PARTITION BY</> and <literal>ORDER BY</>
+ syntactically equivalent <literal>PARTITION BY</literal> and
+ <literal>ORDER BY</literal>
clauses in their window definitions are guaranteed to be evaluated in a
single pass over the data. Therefore they will see the same sort ordering,
- even if the <literal>ORDER BY</> does not uniquely determine an ordering.
+ even if the <literal>ORDER BY</literal> does not uniquely determine an ordering.
However, no guarantees are made about the evaluation of functions having
- different <literal>PARTITION BY</> or <literal>ORDER BY</> specifications.
+ different <literal>PARTITION BY</literal> or <literal>ORDER BY</literal> specifications.
(In such cases a sort step is typically required between the passes of
window function evaluations, and the sort is not guaranteed to preserve
- ordering of rows that its <literal>ORDER BY</> sees as equivalent.)
+ ordering of rows that its <literal>ORDER BY</literal> sees as equivalent.)
</para>
<para>
Currently, window functions always require presorted data, and so the
query output will be ordered according to one or another of the window
- functions' <literal>PARTITION BY</>/<literal>ORDER BY</> clauses.
+ functions' <literal>PARTITION BY</literal>/<literal>ORDER BY</literal> clauses.
It is not recommendable to rely on this, however. Use an explicit
- top-level <literal>ORDER BY</> clause if you want to be sure the
+ top-level <literal>ORDER BY</literal> clause if you want to be sure the
results are sorted in a particular way.
</para>
</sect2>
@@ -1078,12 +1080,12 @@
</para>
<para>
- The <literal>AS</> keyword is optional, but only if the new column
+ The <literal>AS</literal> keyword is optional, but only if the new column
name does not match any
<productname>PostgreSQL</productname> keyword (see <xref
- linkend="sql-keywords-appendix">). To avoid an accidental match to
+ linkend="sql-keywords-appendix"/>). To avoid an accidental match to
a keyword, you can double-quote the column name. For example,
- <literal>VALUE</> is a keyword, so this does not work:
+ <literal>VALUE</literal> is a keyword, so this does not work:
<programlisting>
SELECT a value, b + c AS sum FROM ...
</programlisting>
@@ -1373,8 +1375,8 @@
<para>
<literal>OFFSET</literal> indique de passer ce nombre de lignes avant de renvoyer
les lignes restantes. <literal>OFFSET 0</literal> revient à oublier la clause
- <literal>OFFSET</literal>, and <literal>LIMIT NULL</> is the same
- as omitting the <literal>LIMIT</> clause. Si à la fois <literal>OFFSET</literal> et <literal>LIMIT</literal>
+ <literal>OFFSET</literal>, and <literal>LIMIT NULL</literal> is the same
+ as omitting the <literal>LIMIT</literal> clause. Si à la fois <literal>OFFSET</literal> et <literal>LIMIT</literal>
apparaissent, alors les <literal>OFFSET</literal> lignes sont laissées avant de
commencer le renvoi des <literal>LIMIT</literal> lignes.
</para>
@@ -1491,8 +1493,8 @@
</indexterm>
<para>
- <literal>WITH</> provides a way to write subqueries for use in a larger
- <literal>SELECT</> query. The subqueries can be thought of as defining
+ <literal>WITH</literal> provides a way to write subqueries for use in a larger
+ <literal>SELECT</literal> query. The subqueries can be thought of as defining
temporary tables that exist just for this query. One use of this feature
is to break down complicated queries into simpler parts. An example is:
@@ -1516,16 +1518,17 @@
</programlisting>
which displays per-product sales totals in only the top sales regions.
- This example could have been written without <literal>WITH</>,
+ This example could have been written without <literal>WITH</literal>,
but we'd have needed two levels of nested sub-SELECTs. It's a bit
easier to follow this way.
</para>
<para>
- The optional <literal>RECURSIVE</> modifier changes <literal>WITH</>
+ The optional <literal>RECURSIVE</literal> modifier changes
+ <literal>WITH</literal>
from a mere syntactic convenience into a feature that accomplishes
things not otherwise possible in standard SQL. Using
- <literal>RECURSIVE</>, a <literal>WITH</> query can refer to its own
+ <literal>RECURSIVE</literal>, a <literal>WITH</literal> query can refer to its own
output. A very simple example is this query to sum the integers from 1
through 100:
@@ -1538,10 +1541,10 @@
SELECT sum(n) FROM t;
</programlisting>
- The general form of a recursive <literal>WITH</> query is always a
- <firstterm>non-recursive term</>, then <literal>UNION</> (or
- <literal>UNION ALL</>), then a
- <firstterm>recursive term</>, where only the recursive term can contain
+ The general form of a recursive <literal>WITH</literal> query is always a
+ <firstterm>non-recursive term</firstterm>, then <literal>UNION</literal> (or
+ <literal>UNION ALL</literal>), then a
+ <firstterm>recursive term</firstterm>, where only the recursive term can contain
a reference to the query's own output. Such a query is executed as
follows:
</para>
@@ -1551,10 +1554,10 @@
<step performance="required">
<para>
- Evaluate the non-recursive term. For <literal>UNION</> (but not
- <literal>UNION ALL</>), discard duplicate rows. Include all remaining
+ Evaluate the non-recursive term. For <literal>UNION</literal> (but not
+ <literal>UNION ALL</literal>), discard duplicate rows. Include all remaining
rows in the result of the recursive query, and also place them in a
- temporary <firstterm>working table</>.
+ temporary <firstterm>working table</firstterm>.
</para>
</step>
@@ -1567,10 +1570,10 @@
<para>
Evaluate the recursive term, substituting the current contents of
the working table for the recursive self-reference.
- For <literal>UNION</> (but not <literal>UNION ALL</>), discard
+ For <literal>UNION</literal> (but not <literal>UNION ALL</literal>), discard
duplicate rows and rows that duplicate any previous result row.
Include all remaining rows in the result of the recursive query, and
- also place them in a temporary <firstterm>intermediate table</>.
+ also place them in a temporary <firstterm>intermediate table</firstterm>.
</para>
</step>
@@ -1587,7 +1590,7 @@
<note>
<para>
Strictly speaking, this process is iteration not recursion, but
- <literal>RECURSIVE</> is the terminology chosen by the SQL standards
+ <literal>RECURSIVE</literal> is the terminology chosen by the SQL standards
committee.
</para>
</note>
@@ -1595,7 +1598,7 @@
<para>
In the example above, the working table has just a single row in each step,
and it takes on the values from 1 through 100 in successive steps. In
- the 100th step, there is no output because of the <literal>WHERE</>
+ the 100th step, there is no output because of the <literal>WHERE</literal>
clause, and so the query terminates.
</para>
@@ -1623,14 +1626,14 @@
When working with recursive queries it is important to be sure that
the recursive part of the query will eventually return no tuples,
or else the query will loop indefinitely. Sometimes, using
- <literal>UNION</> instead of <literal>UNION ALL</> can accomplish this
+ <literal>UNION</literal> instead of <literal>UNION ALL</literal> can accomplish this
by discarding rows that duplicate previous output rows. However, often a
cycle does not involve output rows that are completely duplicate: it may be
necessary to check just one or a few fields to see if the same point has
been reached before. The standard method for handling such situations is
to compute an array of the already-visited values. For example, consider
- the following query that searches a table <structname>graph</> using a
- <structfield>link</> field:
+ the following query that searches a table <structname>graph</structname> using a
+ <structfield>link</structfield> field:
<programlisting>
WITH RECURSIVE search_graph(id, link, data, depth) AS (
@@ -1644,12 +1647,12 @@
SELECT * FROM search_graph;
</programlisting>
- This query will loop if the <structfield>link</> relationships contain
- cycles. Because we require a <quote>depth</> output, just changing
- <literal>UNION ALL</> to <literal>UNION</> would not eliminate the looping.
+ This query will loop if the <structfield>link</structfield> relationships contain
+ cycles. Because we require a <quote>depth</quote> output, just changing
+ <literal>UNION ALL</literal> to <literal>UNION</literal> would not eliminate the looping.
Instead we need to recognize whether we have reached the same row again
while following a particular path of links. We add two columns
- <structfield>path</> and <structfield>cycle</> to the loop-prone query:
+ <structfield>path</structfield> and <structfield>cycle</structfield> to the loop-prone query:
<programlisting>
WITH RECURSIVE search_graph(id, link, data, depth, path, cycle) AS (
@@ -1668,13 +1671,14 @@
</programlisting>
Aside from preventing cycles, the array value is often useful in its own
- right as representing the <quote>path</> taken to reach any particular row.
+ right as representing the <quote>path</quote> taken to reach any particular row.
</para>
<para>
In the general case where more than one field needs to be checked to
recognize a cycle, use an array of rows. For example, if we needed to
- compare fields <structfield>f1</> and <structfield>f2</>:
+ compare fields <structfield>f1</structfield> and
+ <structfield>f2</structfield>:
<programlisting>
WITH RECURSIVE search_graph(id, link, data, depth, path, cycle) AS (
@@ -1695,7 +1699,7 @@
<tip>
<para>
- Omit the <literal>ROW()</> syntax in the common case where only one field
+ Omit the <literal>ROW()</literal> syntax in the common case where only one field
needs to be checked to recognize a cycle. This allows a simple array
rather than a composite-type array to be used, gaining efficiency.
</para>
@@ -1705,16 +1709,17 @@
<para>
The recursive query evaluation algorithm produces its output in
breadth-first search order. You can display the results in depth-first
- search order by making the outer query <literal>ORDER BY</> a
- <quote>path</> column constructed in this way.
+ search order by making the outer query <literal>ORDER BY</literal> a
+ <quote>path</quote> column constructed in this way.
</para>
</tip>
<para>
A helpful trick for testing queries
- when you are not certain if they might loop is to place a <literal>LIMIT</>
+ when you are not certain if they might loop is to place a
+ <literal>LIMIT</literal>
in the parent query. For example, this query would loop forever without
- the <literal>LIMIT</>:
+ the <literal>LIMIT</literal>:
<programlisting>
WITH RECURSIVE t(n) AS (
@@ -1726,7 +1731,7 @@
</programlisting>
This works because <productname>PostgreSQL</productname>'s implementation
- evaluates only as many rows of a <literal>WITH</> query as are actually
+ evaluates only as many rows of a <literal>WITH</literal> query as are actually
fetched by the parent query. Using this trick in production is not
recommended, because other systems might work differently. Also, it
usually won't work if you make the outer query sort the recursive query's
@@ -1734,16 +1739,16 @@
</para>
<para>
- A useful property of <literal>WITH</> queries is that they are evaluated
+ A useful property of <literal>WITH</literal> queries is that they are evaluated
only once per execution of the parent query, even if they are referred to
- more than once by the parent query or sibling <literal>WITH</> queries.
+ more than once by the parent query or sibling <literal>WITH</literal> queries.
Thus, expensive calculations that are needed in multiple places can be
- placed within a <literal>WITH</> query to avoid redundant work. Another
+ placed within a <literal>WITH</literal> query to avoid redundant work. Another
possible application is to prevent unwanted multiple evaluations of
functions with side-effects.
However, the other side of this coin is that the optimizer is less able to
- push restrictions from the parent query down into a <literal>WITH</> query
- than an ordinary sub-query. The <literal>WITH</> query will generally be
+ push restrictions from the parent query down into a <literal>WITH</literal> query
+ than an ordinary sub-query. The <literal>WITH</literal> query will generally be
evaluated as stated, without suppression of rows that the parent query
might discard afterwards. (But, as mentioned above, evaluation might stop
early if the reference(s) to the query demand only a limited number of
Modified: traduc/trunk/postgresql/ref/allfiles.xml
===================================================================
--- traduc/trunk/postgresql/ref/allfiles.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/allfiles.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -5,164 +5,164 @@
révision $Revision$ -->
<!-- SQL commands -->
-<!ENTITY abort SYSTEM "abort.xml">
-<!ENTITY alterAggregate SYSTEM "alter_aggregate.xml">
-<!ENTITY alterConversion SYSTEM "alter_conversion.xml">
-<!ENTITY alterDatabase SYSTEM "alter_database.xml">
-<!ENTITY alterDomain SYSTEM "alter_domain.xml">
-<!entity alterForeignDataWrapper system "alter_foreign_data_wrapper.sgml">
-<!ENTITY alterFunction SYSTEM "alter_function.xml">
-<!ENTITY alterGroup SYSTEM "alter_group.xml">
-<!ENTITY alterIndex SYSTEM "alter_index.xml">
-<!ENTITY alterLanguage SYSTEM "alter_language.xml">
-<!ENTITY alterOperator SYSTEM "alter_operator.xml">
-<!ENTITY alterOperatorClass SYSTEM "alter_opclass.xml">
-<!ENTITY alterOperatorFamily SYSTEM "alter_opfamily.xml">
-<!ENTITY alterRole SYSTEM "alter_role.xml">
-<!ENTITY alterSchema SYSTEM "alter_schema.xml">
-<!entity alterServer system "alter_server.sgml">
-<!ENTITY alterSequence SYSTEM "alter_sequence.xml">
-<!ENTITY alterTable SYSTEM "alter_table.xml">
-<!ENTITY alterTableSpace SYSTEM "alter_tablespace.xml">
-<!ENTITY alterTSConfig SYSTEM "alter_tsconfig.xml">
-<!ENTITY alterTSDictionary SYSTEM "alter_tsdictionary.xml">
-<!ENTITY alterTSParser SYSTEM "alter_tsparser.xml">
-<!ENTITY alterTSTemplate SYSTEM "alter_tstemplate.xml">
-<!ENTITY alterTrigger SYSTEM "alter_trigger.xml">
-<!ENTITY alterType SYSTEM "alter_type.xml">
-<!ENTITY alterUser SYSTEM "alter_user.xml">
-<!entity alterUserMapping system "alter_user_mapping.sgml">
-<!ENTITY alterView SYSTEM "alter_view.xml">
-<!ENTITY analyze SYSTEM "analyze.xml">
-<!ENTITY begin SYSTEM "begin.xml">
-<!ENTITY checkpoint SYSTEM "checkpoint.xml">
-<!ENTITY close SYSTEM "close.xml">
-<!ENTITY cluster SYSTEM "cluster.xml">
-<!ENTITY commentOn SYSTEM "comment.xml">
-<!ENTITY commit SYSTEM "commit.xml">
-<!ENTITY commitPrepared SYSTEM "commit_prepared.xml">
-<!ENTITY copyTable SYSTEM "copy.xml">
-<!ENTITY createAggregate SYSTEM "create_aggregate.xml">
-<!ENTITY createCast SYSTEM "create_cast.xml">
-<!ENTITY createConstraint SYSTEM "create_constraint.xml">
-<!ENTITY createConversion SYSTEM "create_conversion.xml">
-<!ENTITY createDatabase SYSTEM "create_database.xml">
-<!ENTITY createDomain SYSTEM "create_domain.xml">
-<!entity createForeignDataWrapper system "create_foreign_data_wrapper.sgml">
-<!ENTITY createFunction SYSTEM "create_function.xml">
-<!ENTITY createGroup SYSTEM "create_group.xml">
-<!ENTITY createIndex SYSTEM "create_index.xml">
-<!ENTITY createLanguage SYSTEM "create_language.xml">
-<!ENTITY createOperator SYSTEM "create_operator.xml">
-<!ENTITY createOperatorClass SYSTEM "create_opclass.xml">
-<!ENTITY createOperatorFamily SYSTEM "create_opfamily.xml">
-<!ENTITY createRole SYSTEM "create_role.xml">
-<!ENTITY createRule SYSTEM "create_rule.xml">
-<!ENTITY createSchema SYSTEM "create_schema.xml">
-<!ENTITY createSequence SYSTEM "create_sequence.xml">
-<!entity createServer system "create_server.sgml">
-<!ENTITY createTable SYSTEM "create_table.xml">
-<!ENTITY createTableAs SYSTEM "create_table_as.xml">
-<!ENTITY createTableSpace SYSTEM "create_tablespace.xml">
-<!ENTITY createTrigger SYSTEM "create_trigger.xml">
-<!ENTITY createTSConfig SYSTEM "create_tsconfig.xml">
-<!ENTITY createTSDictionary SYSTEM "create_tsdictionary.xml">
-<!ENTITY createTSParser SYSTEM "create_tsparser.xml">
-<!ENTITY createTSTemplate SYSTEM "create_tstemplate.xml">
-<!ENTITY createType SYSTEM "create_type.xml">
-<!ENTITY createUser SYSTEM "create_user.xml">
-<!entity createUserMapping system "create_user_mapping.sgml">
-<!ENTITY createView SYSTEM "create_view.xml">
-<!ENTITY deallocate SYSTEM "deallocate.xml">
-<!ENTITY declare SYSTEM "declare.xml">
-<!ENTITY delete SYSTEM "delete.xml">
-<!ENTITY discard SYSTEM "discard.xml">
-<!ENTITY dropAggregate SYSTEM "drop_aggregate.xml">
-<!ENTITY dropCast SYSTEM "drop_cast.xml">
-<!ENTITY dropConversion SYSTEM "drop_conversion.xml">
-<!ENTITY dropDatabase SYSTEM "drop_database.xml">
-<!ENTITY dropDomain SYSTEM "drop_domain.xml">
-<!entity dropForeignDataWrapper system "drop_foreign_data_wrapper.sgml">
-<!ENTITY dropFunction SYSTEM "drop_function.xml">
-<!ENTITY dropGroup SYSTEM "drop_group.xml">
-<!ENTITY dropIndex SYSTEM "drop_index.xml">
-<!ENTITY dropLanguage SYSTEM "drop_language.xml">
-<!ENTITY dropOperator SYSTEM "drop_operator.xml">
-<!ENTITY dropOperatorClass SYSTEM "drop_opclass.xml">
-<!ENTITY dropOperatorFamily SYSTEM "drop_opfamily.xml">
-<!ENTITY dropOwned SYSTEM "drop_owned.xml">
-<!ENTITY dropRole SYSTEM "drop_role.xml">
-<!ENTITY dropRule SYSTEM "drop_rule.xml">
-<!ENTITY dropSchema SYSTEM "drop_schema.xml">
-<!ENTITY dropSequence SYSTEM "drop_sequence.xml">
-<!entity dropServer system "drop_server.sgml">
-<!ENTITY dropTable SYSTEM "drop_table.xml">
-<!ENTITY dropTableSpace SYSTEM "drop_tablespace.xml">
-<!ENTITY dropTrigger SYSTEM "drop_trigger.xml">
-<!ENTITY dropTSConfig SYSTEM "drop_tsconfig.xml">
-<!ENTITY dropTSDictionary SYSTEM "drop_tsdictionary.xml">
-<!ENTITY dropTSParser SYSTEM "drop_tsparser.xml">
-<!ENTITY dropTSTemplate SYSTEM "drop_tstemplate.xml">
-<!ENTITY dropType SYSTEM "drop_type.xml">
-<!ENTITY dropUser SYSTEM "drop_user.xml">
-<!entity dropUserMapping system "drop_user_mapping.sgml">
-<!ENTITY dropView SYSTEM "drop_view.xml">
-<!ENTITY end SYSTEM "end.xml">
-<!ENTITY execute SYSTEM "execute.xml">
-<!ENTITY explain SYSTEM "explain.xml">
-<!ENTITY fetch SYSTEM "fetch.xml">
-<!ENTITY grant SYSTEM "grant.xml">
-<!ENTITY insert SYSTEM "insert.xml">
-<!ENTITY listen SYSTEM "listen.xml">
-<!ENTITY load SYSTEM "load.xml">
-<!ENTITY lock SYSTEM "lock.xml">
-<!ENTITY move SYSTEM "move.xml">
-<!ENTITY notify SYSTEM "notify.xml">
-<!ENTITY prepare SYSTEM "prepare.xml">
-<!ENTITY prepareTransaction SYSTEM "prepare_transaction.xml">
-<!ENTITY reassignOwned SYSTEM "reassign_owned.xml">
-<!ENTITY reindex SYSTEM "reindex.xml">
-<!ENTITY releaseSavepoint SYSTEM "release_savepoint.xml">
-<!ENTITY reset SYSTEM "reset.xml">
-<!ENTITY revoke SYSTEM "revoke.xml">
-<!ENTITY rollback SYSTEM "rollback.xml">
-<!ENTITY rollbackPrepared SYSTEM "rollback_prepared.xml">
-<!ENTITY rollbackTo SYSTEM "rollback_to.xml">
-<!ENTITY savepoint SYSTEM "savepoint.xml">
-<!ENTITY select SYSTEM "select.xml">
-<!ENTITY selectInto SYSTEM "select_into.xml">
-<!ENTITY set SYSTEM "set.xml">
-<!ENTITY setConstraints SYSTEM "set_constraints.xml">
-<!ENTITY setRole SYSTEM "set_role.xml">
-<!ENTITY setSessionAuth SYSTEM "set_session_auth.xml">
-<!ENTITY setTransaction SYSTEM "set_transaction.xml">
-<!ENTITY show SYSTEM "show.xml">
-<!ENTITY startTransaction SYSTEM "start_transaction.xml">
-<!ENTITY truncate SYSTEM "truncate.xml">
-<!ENTITY unlisten SYSTEM "unlisten.xml">
-<!ENTITY update SYSTEM "update.xml">
-<!ENTITY vacuum SYSTEM "vacuum.xml">
-<!ENTITY values SYSTEM "values.xml">
+<!ENTITY abort SYSTEM "abort.xml">
+<!ENTITY alterAggregate SYSTEM "alter_aggregate.xml">
+<!ENTITY alterConversion SYSTEM "alter_conversion.xml">
+<!ENTITY alterDatabase SYSTEM "alter_database.xml">
+<!ENTITY alterDomain SYSTEM "alter_domain.xml">
+<!ENTITY alterForeignDataWrapper SYSTEM "alter_foreign_data_wrapper.xml">
+<!ENTITY alterFunction SYSTEM "alter_function.xml">
+<!ENTITY alterGroup SYSTEM "alter_group.xml">
+<!ENTITY alterIndex SYSTEM "alter_index.xml">
+<!ENTITY alterLanguage SYSTEM "alter_language.xml">
+<!ENTITY alterOperator SYSTEM "alter_operator.xml">
+<!ENTITY alterOperatorClass SYSTEM "alter_opclass.xml">
+<!ENTITY alterOperatorFamily SYSTEM "alter_opfamily.xml">
+<!ENTITY alterRole SYSTEM "alter_role.xml">
+<!ENTITY alterSchema SYSTEM "alter_schema.xml">
+<!ENTITY alterServer SYSTEM "alter_server.xml">
+<!ENTITY alterSequence SYSTEM "alter_sequence.xml">
+<!ENTITY alterTable SYSTEM "alter_table.xml">
+<!ENTITY alterTableSpace SYSTEM "alter_tablespace.xml">
+<!ENTITY alterTSConfig SYSTEM "alter_tsconfig.xml">
+<!ENTITY alterTSDictionary SYSTEM "alter_tsdictionary.xml">
+<!ENTITY alterTSParser SYSTEM "alter_tsparser.xml">
+<!ENTITY alterTSTemplate SYSTEM "alter_tstemplate.xml">
+<!ENTITY alterTrigger SYSTEM "alter_trigger.xml">
+<!ENTITY alterType SYSTEM "alter_type.xml">
+<!ENTITY alterUser SYSTEM "alter_user.xml">
+<!ENTITY alterUserMapping SYSTEM "alter_user_mapping.xml">
+<!ENTITY alterView SYSTEM "alter_view.xml">
+<!ENTITY analyze SYSTEM "analyze.xml">
+<!ENTITY begin SYSTEM "begin.xml">
+<!ENTITY checkpoint SYSTEM "checkpoint.xml">
+<!ENTITY close SYSTEM "close.xml">
+<!ENTITY cluster SYSTEM "cluster.xml">
+<!ENTITY commentOn SYSTEM "comment.xml">
+<!ENTITY commit SYSTEM "commit.xml">
+<!ENTITY commitPrepared SYSTEM "commit_prepared.xml">
+<!ENTITY copyTable SYSTEM "copy.xml">
+<!ENTITY createAggregate SYSTEM "create_aggregate.xml">
+<!ENTITY createCast SYSTEM "create_cast.xml">
+<!ENTITY createConstraint SYSTEM "create_constraint.xml">
+<!ENTITY createConversion SYSTEM "create_conversion.xml">
+<!ENTITY createDatabase SYSTEM "create_database.xml">
+<!ENTITY createDomain SYSTEM "create_domain.xml">
+<!ENTITY createForeignDataWrapper SYSTEM "create_foreign_data_wrapper.xml">
+<!ENTITY createFunction SYSTEM "create_function.xml">
+<!ENTITY createGroup SYSTEM "create_group.xml">
+<!ENTITY createIndex SYSTEM "create_index.xml">
+<!ENTITY createLanguage SYSTEM "create_language.xml">
+<!ENTITY createOperator SYSTEM "create_operator.xml">
+<!ENTITY createOperatorClass SYSTEM "create_opclass.xml">
+<!ENTITY createOperatorFamily SYSTEM "create_opfamily.xml">
+<!ENTITY createRole SYSTEM "create_role.xml">
+<!ENTITY createRule SYSTEM "create_rule.xml">
+<!ENTITY createSchema SYSTEM "create_schema.xml">
+<!ENTITY createSequence SYSTEM "create_sequence.xml">
+<!ENTITY createServer SYSTEM "create_server.xml">
+<!ENTITY createTable SYSTEM "create_table.xml">
+<!ENTITY createTableAs SYSTEM "create_table_as.xml">
+<!ENTITY createTableSpace SYSTEM "create_tablespace.xml">
+<!ENTITY createTrigger SYSTEM "create_trigger.xml">
+<!ENTITY createTSConfig SYSTEM "create_tsconfig.xml">
+<!ENTITY createTSDictionary SYSTEM "create_tsdictionary.xml">
+<!ENTITY createTSParser SYSTEM "create_tsparser.xml">
+<!ENTITY createTSTemplate SYSTEM "create_tstemplate.xml">
+<!ENTITY createType SYSTEM "create_type.xml">
+<!ENTITY createUser SYSTEM "create_user.xml">
+<!ENTITY createUserMapping SYSTEM "create_user_mapping.xml">
+<!ENTITY createView SYSTEM "create_view.xml">
+<!ENTITY deallocate SYSTEM "deallocate.xml">
+<!ENTITY declare SYSTEM "declare.xml">
+<!ENTITY delete SYSTEM "delete.xml">
+<!ENTITY discard SYSTEM "discard.xml">
+<!ENTITY dropAggregate SYSTEM "drop_aggregate.xml">
+<!ENTITY dropCast SYSTEM "drop_cast.xml">
+<!ENTITY dropConversion SYSTEM "drop_conversion.xml">
+<!ENTITY dropDatabase SYSTEM "drop_database.xml">
+<!ENTITY dropDomain SYSTEM "drop_domain.xml">
+<!ENTITY dropForeignDataWrapper SYSTEM "drop_foreign_data_wrapper.xml">
+<!ENTITY dropFunction SYSTEM "drop_function.xml">
+<!ENTITY dropGroup SYSTEM "drop_group.xml">
+<!ENTITY dropIndex SYSTEM "drop_index.xml">
+<!ENTITY dropLanguage SYSTEM "drop_language.xml">
+<!ENTITY dropOperator SYSTEM "drop_operator.xml">
+<!ENTITY dropOperatorClass SYSTEM "drop_opclass.xml">
+<!ENTITY dropOperatorFamily SYSTEM "drop_opfamily.xml">
+<!ENTITY dropOwned SYSTEM "drop_owned.xml">
+<!ENTITY dropRole SYSTEM "drop_role.xml">
+<!ENTITY dropRule SYSTEM "drop_rule.xml">
+<!ENTITY dropSchema SYSTEM "drop_schema.xml">
+<!ENTITY dropSequence SYSTEM "drop_sequence.xml">
+<!ENTITY dropServer SYSTEM "drop_server.xml">
+<!ENTITY dropTable SYSTEM "drop_table.xml">
+<!ENTITY dropTableSpace SYSTEM "drop_tablespace.xml">
+<!ENTITY dropTrigger SYSTEM "drop_trigger.xml">
+<!ENTITY dropTSConfig SYSTEM "drop_tsconfig.xml">
+<!ENTITY dropTSDictionary SYSTEM "drop_tsdictionary.xml">
+<!ENTITY dropTSParser SYSTEM "drop_tsparser.xml">
+<!ENTITY dropTSTemplate SYSTEM "drop_tstemplate.xml">
+<!ENTITY dropType SYSTEM "drop_type.xml">
+<!ENTITY dropUser SYSTEM "drop_user.xml">
+<!ENTITY dropUserMapping SYSTEM "drop_user_mapping.xml">
+<!ENTITY dropView SYSTEM "drop_view.xml">
+<!ENTITY end SYSTEM "end.xml">
+<!ENTITY execute SYSTEM "execute.xml">
+<!ENTITY explain SYSTEM "explain.xml">
+<!ENTITY fetch SYSTEM "fetch.xml">
+<!ENTITY grant SYSTEM "grant.xml">
+<!ENTITY insert SYSTEM "insert.xml">
+<!ENTITY listen SYSTEM "listen.xml">
+<!ENTITY load SYSTEM "load.xml">
+<!ENTITY lock SYSTEM "lock.xml">
+<!ENTITY move SYSTEM "move.xml">
+<!ENTITY notify SYSTEM "notify.xml">
+<!ENTITY prepare SYSTEM "prepare.xml">
+<!ENTITY prepareTransaction SYSTEM "prepare_transaction.xml">
+<!ENTITY reassignOwned SYSTEM "reassign_owned.xml">
+<!ENTITY reindex SYSTEM "reindex.xml">
+<!ENTITY releaseSavepoint SYSTEM "release_savepoint.xml">
+<!ENTITY reset SYSTEM "reset.xml">
+<!ENTITY revoke SYSTEM "revoke.xml">
+<!ENTITY rollback SYSTEM "rollback.xml">
+<!ENTITY rollbackPrepared SYSTEM "rollback_prepared.xml">
+<!ENTITY rollbackTo SYSTEM "rollback_to.xml">
+<!ENTITY savepoint SYSTEM "savepoint.xml">
+<!ENTITY select SYSTEM "select.xml">
+<!ENTITY selectInto SYSTEM "select_into.xml">
+<!ENTITY set SYSTEM "set.xml">
+<!ENTITY setConstraints SYSTEM "set_constraints.xml">
+<!ENTITY setRole SYSTEM "set_role.xml">
+<!ENTITY setSessionAuth SYSTEM "set_session_auth.xml">
+<!ENTITY setTransaction SYSTEM "set_transaction.xml">
+<!ENTITY show SYSTEM "show.xml">
+<!ENTITY startTransaction SYSTEM "start_transaction.xml">
+<!ENTITY truncate SYSTEM "truncate.xml">
+<!ENTITY unlisten SYSTEM "unlisten.xml">
+<!ENTITY update SYSTEM "update.xml">
+<!ENTITY vacuum SYSTEM "vacuum.xml">
+<!ENTITY values SYSTEM "values.xml">
<!-- applications and utilities -->
-<!ENTITY clusterdb SYSTEM "clusterdb.xml">
-<!ENTITY createdb SYSTEM "createdb.xml">
-<!ENTITY createlang SYSTEM "createlang.xml">
-<!ENTITY createuser SYSTEM "createuser.xml">
-<!ENTITY dropdb SYSTEM "dropdb.xml">
-<!ENTITY droplang SYSTEM "droplang.xml">
-<!ENTITY dropuser SYSTEM "dropuser.xml">
-<!ENTITY ecpgRef SYSTEM "ecpg-ref.xml">
-<!ENTITY initdb SYSTEM "initdb.xml">
-<!ENTITY pgConfig SYSTEM "pg_config-ref.xml">
-<!ENTITY pgControldata SYSTEM "pg_controldata.xml">
-<!ENTITY pgCtl SYSTEM "pg_ctl-ref.xml">
-<!ENTITY pgDump SYSTEM "pg_dump.xml">
-<!ENTITY pgDumpall SYSTEM "pg_dumpall.xml">
-<!ENTITY pgResetxlog SYSTEM "pg_resetxlog.xml">
-<!ENTITY pgRestore SYSTEM "pg_restore.xml">
-<!ENTITY postgres SYSTEM "postgres-ref.xml">
-<!ENTITY postmaster SYSTEM "postmaster.xml">
-<!ENTITY psqlRef SYSTEM "psql-ref.xml">
-<!ENTITY reindexdb SYSTEM "reindexdb.xml">
-<!ENTITY vacuumdb SYSTEM "vacuumdb.xml">
+<!ENTITY clusterdb SYSTEM "clusterdb.xml">
+<!ENTITY createdb SYSTEM "createdb.xml">
+<!ENTITY createlang SYSTEM "createlang.xml">
+<!ENTITY createuser SYSTEM "createuser.xml">
+<!ENTITY dropdb SYSTEM "dropdb.xml">
+<!ENTITY droplang SYSTEM "droplang.xml">
+<!ENTITY dropuser SYSTEM "dropuser.xml">
+<!ENTITY ecpgRef SYSTEM "ecpg-ref.xml">
+<!ENTITY initdb SYSTEM "initdb.xml">
+<!ENTITY pgConfig SYSTEM "pg_config-ref.xml">
+<!ENTITY pgControldata SYSTEM "pg_controldata.xml">
+<!ENTITY pgCtl SYSTEM "pg_ctl-ref.xml">
+<!ENTITY pgDump SYSTEM "pg_dump.xml">
+<!ENTITY pgDumpall SYSTEM "pg_dumpall.xml">
+<!ENTITY pgResetxlog SYSTEM "pg_resetxlog.xml">
+<!ENTITY pgRestore SYSTEM "pg_restore.xml">
+<!ENTITY postgres SYSTEM "postgres-ref.xml">
+<!ENTITY postmaster SYSTEM "postmaster.xml">
+<!ENTITY psqlRef SYSTEM "psql-ref.xml">
+<!ENTITY reindexdb SYSTEM "reindexdb.xml">
+<!ENTITY vacuumdb SYSTEM "vacuumdb.xml">
Modified: traduc/trunk/postgresql/ref/alter_database.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_database.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_database.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -27,7 +27,7 @@
ALTER DATABASE <replaceable class="parameter">nom</replaceable> RENAME TO <replaceable>nouveau_nom</replaceable>
ALTER DATABASE <replaceable class="parameter">nom</replaceable> OWNER TO <replaceable>nouveau_propriétaire</replaceable>
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> SET TABLESPACE <replaceable class="PARAMETER">new_tablespace</replaceable>
+ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> SET TABLESPACE <replaceable class="PARAMETER">nouveau_tablespace</replaceable>
ALTER DATABASE <replaceable class="parameter">nom</replaceable> SET <replaceable>paramètre</replaceable> { TO | = } { <replaceable>valeur</replaceable> | DEFAULT }
ALTER DATABASE <replaceable class="parameter">nom</replaceable> SET <replaceable>paramètre</replaceable> FROM CURRENT
@@ -71,12 +71,13 @@
</para>
<para>
- The fourth form changes the default tablespace of the database.
- Only the database owner or a superuser can do this; you must also have
- create privilege for the new tablespace.
- This command physically moves any tables or indexes in the database's old
- default tablespace to the new tablespace. Note that tables and indexes
- in non-default tablespaces are not affected.
+ La quatrième forme change le tablespace par défaut de la base de données.
+ Seuls le propriétaire de la base de données et un superutilisateur peuvent
+ le faire ; vous devez aussi avoir le droit CREATE pour le nouveau
+ tablespace. Cette commande déplace physiquement toutes tables et index
+ actuellement dans l'ancien tablespace par défaut de la base de données vers
+ le nouveau tablespace. Notez que les tables et index placés dans d'autres
+ tablespaces ne sont pas affectés.
</para>
<para>
@@ -103,7 +104,7 @@
<term><replaceable class="parameter">nom</replaceable></term>
<listitem>
<para>
- Le nom de la base dont les attributs sont à modifier.
+ Le nom de la base dont les attributs sont à modifier.
</para>
</listitem>
</varlistentry>
@@ -126,24 +127,23 @@
</listitem>
</varlistentry>
- <varlistentry>
- <term><replaceable
- class="parameter">nouveau_propriétaire</replaceable></term>
- <listitem>
- <para>
- Le nouveau propriétaire de la base.
- </para>
- </listitem>
- </varlistentry>
+ <varlistentry>
+ <term><replaceable class="parameter">nouveau_propriétaire</replaceable></term>
+ <listitem>
+ <para>
+ Le nouveau propriétaire de la base.
+ </para>
+ </listitem>
+ </varlistentry>
- <varlistentry>
- <term><replaceable class="parameter">new_tablespace</replaceable></term>
- <listitem>
- <para>
- The new default tablespace of the database.
- </para>
- </listitem>
- </varlistentry>
+ <varlistentry>
+ <term><replaceable class="parameter">new_tablespace</replaceable></term>
+ <listitem>
+ <para>
+ Le nouveau tablespace par défaut de la base de données.
+ </para>
+ </listitem>
+ </varlistentry>
<varlistentry>
<term><replaceable>paramètre</replaceable></term>
@@ -209,7 +209,7 @@
<member><xref linkend="sql-createdatabase" endterm="sql-createdatabase-title"/></member>
<member><xref linkend="sql-dropdatabase" endterm="sql-dropdatabase-title"/></member>
<member><xref linkend="sql-set" endterm="sql-set-title"/></member>
- <member><xref linkend="sql-createtablespace" endterm="sql-createtablespace-title"></member>
+ <member><xref linkend="sql-createtablespace" endterm="sql-createtablespace-title"/></member>
</simplelist>
</refsect1>
</refentry>
Modified: traduc/trunk/postgresql/ref/alter_domain.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_domain.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_domain.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -141,7 +141,7 @@
<term><replaceable class="parameter">nom</replaceable></term>
<listitem>
<para>
- Le nom du domaine à modifier.
+ Le nom du domaine à modifier.
</para>
</listitem>
</varlistentry>
@@ -150,7 +150,7 @@
<term><replaceable class="parameter">contrainte_de_domaine</replaceable></term>
<listitem>
<para>
- Nouvelle contrainte de domaine pour le domaine.
+ Nouvelle contrainte de domaine pour le domaine.
</para>
</listitem>
</varlistentry>
@@ -159,7 +159,7 @@
<term><replaceable class="parameter">nom_de_contrainte</replaceable></term>
<listitem>
<para>
- Le nom d'une contrainte à supprimer.
+ Le nom d'une contrainte à supprimer.
</para>
</listitem>
</varlistentry>
@@ -187,7 +187,7 @@
<term><replaceable class="parameter">nouveau_propriétaire</replaceable></term>
<listitem>
<para>
- Le nom de l'utilisateur nouveau propriétaire du domaine.
+ Le nom de l'utilisateur nouveau propriétaire du domaine.
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/ref/alter_foreign_data_wrapper.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_foreign_data_wrapper.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_foreign_data_wrapper.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1,17 +1,18 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_foreign_data_wrapper.sgml,v 1.2 2009-02-24 10:06:32 petere Exp $
-PostgreSQL documentation
--->
+<?xml version="1.0" encoding="ISO-8859-15"?>
+<!-- Dernière modification
+ le $Date: 2009-04-13 17:20:17 +0200 (lun 13 avr 2009) $
+ par $Author: gleu $
+ révision $Revision: 1293 $ -->
-<refentry id="SQL-ALTERFOREIGNDATAWRAPPER">
+<refentry id="sql-alterforeigndatawrapper">
<refmeta>
<refentrytitle id="sql-alterforeigndatawrapper-title">ALTER FOREIGN DATA WRAPPER</refentrytitle>
- <refmiscinfo>SQL - Language Statements</refmiscinfo>
+ <refmiscinfo>SQL - Instructions du langage</refmiscinfo>
</refmeta>
<refnamediv>
<refname>ALTER FOREIGN DATA WRAPPER</refname>
- <refpurpose>change the definition of a foreign-data wrapper</refpurpose>
+ <refpurpose>modifier la définition d'un wrapper de données distantes</refpurpose>
</refnamediv>
<indexterm zone="sql-alterforeigndatawrapper">
@@ -20,10 +21,10 @@
<refsynopsisdiv>
<synopsis>
-ALTER FOREIGN DATA WRAPPER <replaceable class="parameter">name</replaceable>
- [ VALIDATOR <replaceable class="parameter">valfunction</replaceable> | NO VALIDATOR ]
- [ OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ]) ]
-ALTER FOREIGN DATA WRAPPER <replaceable class="parameter">name</replaceable> OWNER TO <replaceable>new_owner</replaceable>
+ALTER FOREIGN DATA WRAPPER <replaceable class="parameter">nom</replaceable>
+ [ VALIDATOR <replaceable class="parameter">fonction_validation</replaceable> | NO VALIDATOR ]
+ [ OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">valeur</replaceable>'] [, ... ]) ]
+ALTER FOREIGN DATA WRAPPER <replaceable class="parameter">nom</replaceable> OWNER TO <replaceable>nouveau_propriétaire</replaceable>
</synopsis>
</refsynopsisdiv>
@@ -31,45 +32,46 @@
<title>Description</title>
<para>
- <command>ALTER FOREIGN DATA WRAPPER</command> changes the
- definition of a foreign-data wrapper. The first form of the
- command changes the library or the generic options of the
- foreign-data wrapper (at least one clause is required). The second
- form changes the owner of the foreign-data wrapper.
+ <command>ALTER FOREIGN DATA WRAPPER</command> modifie la définition d'un
+ wrapper de données distantes. La première forme de la commande modifie la
+ bibliothèque ou les options génériques du wrapper de données distantes
+ (au moins une clause est nécessaire). La seconde forme modifie le
+ propriétaire du wrapper de données distantes.
</para>
<para>
- Only superusers can alter foreign-data wrappers. Additionally,
- only superusers can own foreign-data wrappers.
+ Seuls les superutilisateurs peuvent modifier les wrappers de données
+ distantes. De plus, seuls les superutilisateurs peuvent être propriétaire
+ de wrappers de données distantes.
</para>
</refsect1>
<refsect1>
- <title>Parameters</title>
+ <title>Paramètres</title>
<variablelist>
<varlistentry>
- <term><replaceable class="parameter">name</replaceable></term>
+ <term><replaceable class="parameter">nom</replaceable></term>
<listitem>
<para>
- The name of an existing foreign-data wrapper.
+ Le nom d'un wrapper existant de données distantes.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>VALIDATOR <replaceable class="parameter">valfunction</replaceable></literal></term>
+ <term><literal>VALIDATOR <replaceable class="parameter">fonction_validation</replaceable></literal></term>
<listitem>
<para>
- Specifies a new foreign-data wrapper validator function.
+ Indique une fonction de validation pour le wrapper de données distantes.
</para>
<para>
- Note that it is possible that after changing the validator the
- options to the foreign-data wrapper, servers, and user mappings
- have become invalid. It is up to the user to make sure that
- these options are correct before using the foreign-data
- wrapper.
+ Notez qu'il est possible que les options des wrappers de données
+ distantes, des serveurs et des correspondances utilisateur peuvent
+ devenir invalides une fois le validateur changé. C'est à l'utilisateur
+ de s'assurer que ces options sont correctes avant d'utiliser le wrapper
+ de données distantes.
</para>
</listitem>
</varlistentry>
@@ -78,22 +80,22 @@
<term><literal>NO VALIDATOR</literal></term>
<listitem>
<para>
- This is used to specify that the foreign-data wrapper should no
- longer have a validator function.
+ Cette option est utilisée pour spécifier que le wrapper de données
+ distantes ne devrait pas avoir une fonction de validation.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">value</replaceable>'] [, ... ] )</literal></term>
+ <term><literal>OPTIONS ( [ ADD | SET | DROP ] <replaceable class="PARAMETER">option</replaceable> ['<replaceable class="PARAMETER">valeur</replaceable>'] [, ... ] )</literal></term>
<listitem>
<para>
- Change options for the foreign-data
- wrapper. <literal>ADD</>, <literal>SET</>, and <literal>DROP</>
- specify the action to be performed. <literal>ADD</> is assumed
- if no operation is explicitly specified. Option names must be
- unique; names and values are also validated using the foreign
- data wrapper library.
+ Modifie les options du wrapper de données distantes.
+ <literal>ADD</literal>, <literal>SET</literal> et <literal>DROP</literal>
+ spécifient l'action à réaliser. <literal>ADD</literal> est pris par défaut
+ si aucune opération n'est explicitement spécifiée. Les noms des options
+ doivent être uniques ; les noms et valeurs sont validées en utilisant
+ la bibliothèque de wrapper de données distantes.
</para>
</listitem>
</varlistentry>
@@ -101,19 +103,19 @@
</refsect1>
<refsect1>
- <title>Examples</title>
+ <title>Exemples</title>
<para>
- Change a foreign-data wrapper <literal>dbi</>, add
- option <literal>foo</>, drop <literal>bar</>:
+ Modifier wrapper de données distantes <literal>dbi</literal>, ajouter
+ l'option <literal>foo</literal>, supprimer <literal>bar</literal> :
<programlisting>
ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo '1', DROP 'bar');
</programlisting>
</para>
<para>
- Change the foreign-data wrapper <literal>dbi</> validator
- to <literal>bob.myvalidator</>:
+ Modifier la fonction de validation du wrapper de données distantes
+ <literal>dbi</literal> en <literal>bob.myvalidator</literal> :
<programlisting>
ALTER FOREIGN DATA WRAPPER dbi VALIDATOR bob.myvalidator;
</programlisting>
@@ -121,22 +123,21 @@
</refsect1>
<refsect1>
- <title>Compatibility</title>
+ <title>Compatibilité</title>
<para>
- <command>ALTER FOREIGN DATA WRAPPER</command> conforms to ISO/IEC
- 9075-9 (SQL/MED). The standard does not specify the <literal>
- VALIDATOR</literal> and <literal>OWNER TO</> variants of the
- command.
+ <command>ALTER FOREIGN DATA WRAPPER</command> se conforme à ISO/IEC
+ 9075-9 (SQL/MED). Le standard ne spécifie pas les variantes
+ <literal>VALIDATOR</literal> et <literal>OWNER TO</literal> de la commande.
</para>
</refsect1>
<refsect1>
- <title>See Also</title>
+ <title>Voir aussi</title>
<simplelist type="inline">
- <member><xref linkend="sql-createforeigndatawrapper" endterm="sql-createforeigndatawrapper-title"></member>
- <member><xref linkend="sql-dropforeigndatawrapper" endterm="sql-dropforeigndatawrapper-title"></member>
+ <member><xref linkend="sql-createforeigndatawrapper" endterm="sql-createforeigndatawrapper-title"/></member>
+ <member><xref linkend="sql-dropforeigndatawrapper" endterm="sql-dropforeigndatawrapper-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/alter_function.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_function.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_function.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -84,7 +84,7 @@
<listitem>
<para>
Le mode d'un argument : <literal>IN</literal>, <literal>OUT</literal>,
- <literal>INOUT</literal> ou <literal>VARIADIC</>. En cas d'omission, la
+ <literal>INOUT</literal> ou <literal>VARIADIC</literal>. En cas d'omission, la
valeur par défaut est <literal>IN</literal>. <command>ALTER
FUNCTION</command> ne tient pas compte des arguments <literal>OUT</literal>,
car seuls les arguments en entrée sont nécessaire pour déterminer
Modified: traduc/trunk/postgresql/ref/alter_opfamily.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_opfamily.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_opfamily.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -241,9 +241,10 @@
</para>
<para>
- Before <productname>PostgreSQL</productname> 8.4, the <literal>OPERATOR</>
- clause could include a <literal>RECHECK</> option. This is no longer
- supported because whether an index operator is <quote>lossy</> is now
+ Before <productname>PostgreSQL</productname> 8.4, the
+ <literal>OPERATOR</literal>
+ clause could include a <literal>RECHECK</literal> option. This is no longer
+ supported because whether an index operator is <quote>lossy</quote> is now
determined on-the-fly at runtime. This allows efficient handling of
cases where an operator might or might not be lossy.
</para>
Modified: traduc/trunk/postgresql/ref/alter_role.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_role.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_role.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -89,7 +89,7 @@
<filename>postgresql.conf</filename> ou provenant de la ligne de
commande de postgres. This only happens at login time, so configuration
settings associated with a role to which you've <xref
- linkend="sql-set-role" endterm="sql-set-role-title"> will be ignored.
+ linkend="sql-set-role" endterm="sql-set-role-title"/> will be ignored.
Les superutilisateurs peuvent modifier les valeurs de session de
n'importe quel utilisateur. Les rôles disposant du droit <literal>CREATEROLE</literal>
peuvent modifier les valeurs par défaut pour les rôles ordinaires (non
@@ -167,7 +167,7 @@
<para>
Role-specific variable setting take effect only at login;
- <xref linkend="sql-set-role" endterm="sql-set-role-title">
+ <xref linkend="sql-set-role" endterm="sql-set-role-title"/>
does not process role-specific variable settings.
</para>
Modified: traduc/trunk/postgresql/ref/alter_sequence.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_sequence.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_sequence.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -122,8 +122,8 @@
The optional clause <literal>START WITH <replaceable
class="parameter">start</replaceable></literal> changes the
recorded start value of the sequence. This has no effect on the
- <emphasis>current</> sequence value; it simply sets the value
- that future <command>ALTER SEQUENCE RESTART</> commands will use.
+ <emphasis>current</emphasis> sequence value; it simply sets the value
+ that future <command>ALTER SEQUENCE RESTART</command> commands will use.
</para>
</listitem>
</varlistentry>
@@ -135,13 +135,13 @@
The optional clause <literal>RESTART [ WITH <replaceable
class="parameter">restart</replaceable> ]</literal> changes the
current value of the sequence. This is equivalent to calling the
- <function>setval</> function with <literal>is_called</literal> =
- <literal>false</>: the specified value will be returned by the
- <emphasis>next</> call of <function>nextval</>.
- Writing <literal>RESTART</> with no <replaceable
- class="parameter">restart</> value is equivalent to supplying
- the start value that was recorded by <command>CREATE SEQUENCE</>
- or last set by <command>ALTER SEQUENCE START WITH</>.
+ <function>setval</function> function with <literal>is_called</literal> =
+ <literal>false</literal>: the specified value will be returned by the
+ <emphasis>next</emphasis> call of <function>nextval</function>.
+ Writing <literal>RESTART</literal> with no <replaceable
+ class="parameter">restart</replaceable> value is equivalent to supplying
+ the start value that was recorded by <command>CREATE SEQUENCE</command>
+ or last set by <command>ALTER SEQUENCE START WITH</command>.
</para>
</listitem>
</varlistentry>
@@ -242,8 +242,8 @@
numéros issus de la même séquence, les effets d'<command>ALTER SEQUENCE</command>
sur les paramètres de génération de la séquence ne sont jamais annulables.
Ces changements prennent effet immédiatement et ne sont pas réversibles.
- Néanmoins, les clauses <literal>OWNED BY</literal>, <literal>OWNER TO</>,
- <literal>RENAME TO</> et
+ Néanmoins, les clauses <literal>OWNED BY</literal>, <literal>OWNER
+ TO</literal>, <literal>RENAME TO</literal> et
<literal>SET SCHEMA</literal> sont des modifications ordinaires du catalogue
et, de ce fait, peuvent être annulées.
</para>
Modified: traduc/trunk/postgresql/ref/alter_server.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_server.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_server.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1,9 +1,10 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_server.sgml,v 1.1 2008-12-19 16:25:16 petere Exp $
-PostgreSQL documentation
--->
+<?xml version="1.0" encoding="ISO-8859-15"?>
+<!-- Dernière modification
+ le $Date: 2009-04-13 17:20:17 +0200 (lun 13 avr 2009) $
+ par $Author: gleu $
+ révision $Revision: 1293 $ -->
-<refentry id="SQL-ALTERSERVER">
+<refentry id="sql-alterserver">
<refmeta>
<refentrytitle id="sql-alterserver-title">ALTER SERVER</refentrytitle>
<refmiscinfo>SQL - Language Statements</refmiscinfo>
@@ -40,7 +41,7 @@
To alter the server you must be the owner of the server.
Additionally to alter the owner, you must own the server and also
be a direct or indirect member of the new owning role, and you must
- have <literal>USAGE</> privilege on the server's foreign-data
+ have <literal>USAGE</literal> privilege on the server's foreign-data
wrapper. (Note that superusers satisfy all these criteria
automatically.)
</para>
@@ -73,8 +74,9 @@
<listitem>
<para>
Change options for the
- server. <literal>ADD</>, <literal>SET</>, and <literal>DROP</>
- specify the action to be performed. <literal>ADD</> is assumed
+ server. <literal>ADD</literal>, <literal>SET</literal>, and
+ <literal>DROP</literal>
+ specify the action to be performed. <literal>ADD</literal> is assumed
if no operation is explicitly specified. Option names must be
unique; names and values are also validated using the server's
foreign-data wrapper library.
@@ -88,15 +90,15 @@
<title>Examples</title>
<para>
- Alter server <literal>foo</>, add connection options:
+ Alter server <literal>foo</literal>, add connection options:
<programlisting>
ALTER SERVER foo OPTIONS (host 'foo', dbname 'foodb');
</programlisting>
</para>
<para>
- Alter server <literal>foo</>, change version,
- change <literal>host</> option:
+ Alter server <literal>foo</literal>, change version,
+ change <literal>host</literal> option:
<programlisting>
ALTER SERVER foo VERSION '8.4' OPTIONS (SET host 'baz');
</programlisting>
@@ -115,8 +117,8 @@
<title>See Also</title>
<simplelist type="inline">
- <member><xref linkend="sql-createserver" endterm="sql-createserver-title"></member>
- <member><xref linkend="sql-dropserver" endterm="sql-dropserver-title"></member>
+ <member><xref linkend="sql-createserver" endterm="sql-createserver-title"/></member>
+ <member><xref linkend="sql-dropserver" endterm="sql-dropserver-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/alter_table.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_table.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_table.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -276,14 +276,14 @@
<listitem>
<para>
This form adds an <literal>oid</literal> system column to the
- table (see <xref linkend="ddl-system-columns">).
+ table (see <xref linkend="ddl-system-columns"/>).
It does nothing if the table already has OIDs.
</para>
<para>
- Note that this is not equivalent to <literal>ADD COLUMN oid oid</>;
+ Note that this is not equivalent to <literal>ADD COLUMN oid oid</literal>;
that would add a normal column that happened to be named
- <literal>oid</>, not a system column.
+ <literal>oid</literal>, not a system column.
</para>
</listitem>
</varlistentry>
@@ -320,8 +320,9 @@
<literal>OIDS</literal> avec la syntaxe <literal>WITH (<replaceable
class="parameter">paramètre_stockage</replaceable>)</literal>,
<command>ALTER TABLE</command> ne traite pas les <literal>OIDS</literal>
- comme un paramètre de stockage. Instead use the <literal>SET WITH OIDS</>
- and <literal>SET WITHOUT OIDS</> forms to change OID status.
+ comme un paramètre de stockage. Instead use the <literal>SET WITH
+ OIDS</literal>
+ and <literal>SET WITHOUT OIDS</literal> forms to change OID status.
</para>
</note>
</listitem>
@@ -669,7 +670,7 @@
réécrite. Cela peut prendre un temps considérable pour une grande
table ; et cela demande temporairement le double d'espace disque.
Adding or removing a system
- <literal>oid</> column likewise requires rewriting the entire table.
+ <literal>oid</literal> column likewise requires rewriting the entire table.
</para>
<para>
@@ -693,7 +694,7 @@
table sur disque car l'espace occupé par la colonne n'est pas
récupéré. Cet espace est récupéré au fur et à mesure des
mises à jour des lignes de la table. (These statements do
- not apply when dropping the system <literal>oid</> column; that is done
+ not apply when dropping the system <literal>oid</literal> column; that is done
with an immediate rewrite.)
</para>
Modified: traduc/trunk/postgresql/ref/alter_user_mapping.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_user_mapping.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_user_mapping.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1,9 +1,10 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_user_mapping.sgml,v 1.2 2009-01-20 09:10:20 petere Exp $
-PostgreSQL documentation
--->
+<?xml version="1.0" encoding="ISO-8859-15"?>
+<!-- Dernière modification
+ le $Date: 2009-04-13 17:20:17 +0200 (lun 13 avr 2009) $
+ par $Author: gleu $
+ révision $Revision: 1293 $ -->
-<refentry id="SQL-ALTERUSERMAPPING">
+<refentry id="sql-alterusermapping">
<refmeta>
<refentrytitle id="sql-alterusermapping-title">ALTER USER MAPPING</refentrytitle>
<refmiscinfo>SQL - Language Statements</refmiscinfo>
@@ -37,7 +38,7 @@
<para>
The owner of a foreign server can alter user mappings for that
server for any user. Also, a user can alter a user mapping for
- his own user name if <literal>USAGE</> privilege on the server has
+ his own user name if <literal>USAGE</literal> privilege on the server has
been granted to the user.
</para>
</refsect1>
@@ -50,9 +51,9 @@
<term><replaceable class="parameter">username</replaceable></term>
<listitem>
<para>
- User name of the mapping. <literal>CURRENT_USER</>
- and <literal>USER</> match the name of the current
- user. <literal>PUBLIC</> is used to match all present and future
+ User name of the mapping. <literal>CURRENT_USER</literal>
+ and <literal>USER</literal> match the name of the current
+ user. <literal>PUBLIC</literal> is used to match all present and future
user names in the system.
</para>
</listitem>
@@ -73,8 +74,9 @@
<para>
Change options for the user mapping. The new options override
any previously specified
- options. <literal>ADD</>, <literal>SET</>, and <literal>DROP</>
- specify the action to be performed. <literal>ADD</> is assumed
+ options. <literal>ADD</literal>, <literal>SET</literal>, and
+ <literal>DROP</literal>
+ specify the action to be performed. <literal>ADD</literal> is assumed
if no operation is explicitly specified. Option names must be
unique; options are also validated by the server's foreign-data
wrapper.
@@ -88,7 +90,8 @@
<title>Examples</title>
<para>
- Change the password for user mapping <literal>bob</>, server<literal> foo</>:
+ Change the password for user mapping <literal>bob</literal>,
+ server<literal> foo</literal>:
<programlisting>
ALTER USER MAPPING FOR bob SERVER foo OPTIONS (user 'bob', password 'public');
</programlisting>
@@ -116,8 +119,8 @@
<title>See Also</title>
<simplelist type="inline">
- <member><xref linkend="sql-createusermapping" endterm="sql-createusermapping-title"></member>
- <member><xref linkend="sql-dropusermapping" endterm="sql-dropusermapping-title"></member>
+ <member><xref linkend="sql-createusermapping" endterm="sql-createusermapping-title"/></member>
+ <member><xref linkend="sql-dropusermapping" endterm="sql-dropusermapping-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/alter_view.xml
===================================================================
--- traduc/trunk/postgresql/ref/alter_view.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/alter_view.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -36,12 +36,12 @@
<para>
<command>ALTER VIEW</command> modifie various auxiliary properties
of a view. (If you want to modify the view's defining query,
- use <command>CREATE OR REPLACE VIEW</>.)
+ use <command>CREATE OR REPLACE VIEW</command>.)
</para>
<para>
- You must own the view to use <command>ALTER VIEW</>.
- To change a view's schema, you must also have <literal>CREATE</>
+ You must own the view to use <command>ALTER VIEW</command>.
+ To change a view's schema, you must also have <literal>CREATE</literal>
privilege on the new schema.
To alter the owner, you must also be a direct or indirect member of the new
owning role, and that role must have <literal>CREATE</literal> privilege on
@@ -70,9 +70,9 @@
<para>
These forms set or remove the default value for a column.
A default value associated with a view column is
- inserted into <command>INSERT</> statements on the view before
+ inserted into <command>INSERT</command> statements on the view before
the view's <literal>ON INSERT</literal> rule is applied, if
- the <command>INSERT</> does not specify a value for the column.
+ the <command>INSERT</command> does not specify a value for the column.
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/ref/clusterdb.xml
===================================================================
--- traduc/trunk/postgresql/ref/clusterdb.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/clusterdb.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -122,8 +122,8 @@
</varlistentry>
<varlistentry>
- <term><option>-v</></term>
- <term><option>--verbose</></term>
+ <term><option>-v</option></term>
+ <term><option>--verbose</option></term>
<listitem>
<para>
Print detailed information during processing.
@@ -173,8 +173,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
Modified: traduc/trunk/postgresql/ref/copy.xml
===================================================================
--- traduc/trunk/postgresql/ref/copy.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/copy.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -355,7 +355,7 @@
par défaut, il est préférable de configurer <varname>datestyle</varname> en
<literal>ISO</literal> avant d'utiliser <command>COPY TO</command>. It is also a good idea to avoid dumping
data with <varname>IntervalStyle</varname> set to
- <literal>sql_standard</>, because negative interval values might be
+ <literal>sql_standard</literal>, because negative interval values might be
misinterpreted by a server that has a different setting for
<varname>IntervalStyle</varname>.
</para>
Modified: traduc/trunk/postgresql/ref/create_cast.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_cast.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_cast.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -65,7 +65,7 @@
</para>
<para>
- You can define a cast as an <firstterm>I/O conversion cast</> using
+ You can define a cast as an <firstterm>I/O conversion cast</firstterm> using
the <literal>WITH INOUT</literal> syntax. An I/O conversion cast is
performed by invoking the output function of the source data type, and
passing the result to the input function of the target data type.
@@ -152,9 +152,9 @@
Sometimes it is necessary for usability or standards-compliance reasons
to provide multiple implicit casts among a set of types, resulting in
ambiguity that cannot be avoided as above. The parser has a fallback
- heuristic based on <firstterm>type categories</> and <firstterm>preferred
- types</> that can help to provide desired behavior in such cases. See
- <xref linkend="sql-createtype" endterm="sql-createtype-title"> for
+ heuristic based on <firstterm>type categories</firstterm> and <firstterm>preferred
+ types</firstterm> that can help to provide desired behavior in such cases. See
+ <xref linkend="sql-createtype" endterm="sql-createtype-title"/> for
more information.
</para>
</note>
Modified: traduc/trunk/postgresql/ref/create_database.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_database.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_database.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -121,7 +121,7 @@
<term><replaceable class="parameter">collate</replaceable></term>
<listitem>
<para>
- Collation order (<literal>LC_COLLATE</>) to use in the new database.
+ Collation order (<literal>LC_COLLATE</literal>) to use in the new database.
This affects the sort order applied to strings, e.g in queries with
ORDER BY, as well as the order used in indexes on text columns.
The default is to use the collation order of the template database.
@@ -133,7 +133,7 @@
<term><replaceable class="parameter">ctype</replaceable></term>
<listitem>
<para>
- Character classification (<literal>LC_CTYPE</>) to use in the new
+ Character classification (<literal>LC_CTYPE</literal>) to use in the new
database. This affects the categorization of characters, e.g. lower,
upper and digit. The default is to use the character classification of
the template database. See below for additional restrictions.
@@ -226,9 +226,10 @@
</para>
<para>
- The <literal>LC_COLLATE</> and <literal>LC_CTYPE</> settings must match
+ The <literal>LC_COLLATE</literal> and <literal>LC_CTYPE</literal> settings must match
those of the template database, except when template0 is used as
- template. This is because <literal>LC_COLLATE</> and <literal>LC_CTYPE</>
+ template. This is because <literal>LC_COLLATE</literal> and
+ <literal>LC_CTYPE</literal>
affects the ordering in indexes, so that any indexes copied from the
template database would be invalid in the new database with different
settings. <literal>template0</literal>, however, is known to not
Modified: traduc/trunk/postgresql/ref/create_domain.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_domain.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_domain.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -202,10 +202,8 @@
<title>Voir aussi</title>
<simplelist type="inline">
- <member><xref linkend="sql-alterdomain"
- endterm="sql-alterdomain-title"/></member>
- <member><xref linkend="sql-dropdomain"
- endterm="sql-dropdomain-title"/></member>
+ <member><xref linkend="sql-alterdomain" endterm="sql-alterdomain-title"/></member>
+ <member><xref linkend="sql-dropdomain" endterm="sql-dropdomain-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/create_foreign_data_wrapper.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_foreign_data_wrapper.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_foreign_data_wrapper.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1,9 +1,10 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_foreign_data_wrapper.sgml,v 1.3 2009-02-27 07:20:00 petere Exp $
-PostgreSQL documentation
--->
+<?xml version="1.0" encoding="ISO-8859-15"?>
+<!-- Dernière modification
+ le $Date: 2009-04-13 17:20:17 +0200 (lun 13 avr 2009) $
+ par $Author: gleu $
+ révision $Revision: 1293 $ -->
-<refentry id="SQL-CREATEFOREIGNDATAWRAPPER">
+<refentry id="sql-createforeigndatawrapper">
<refmeta>
<refentrytitle id="sql-createforeigndatawrapper-title">CREATE FOREIGN DATA WRAPPER</refentrytitle>
<refmiscinfo>SQL - Language Statements</refmiscinfo>
@@ -111,7 +112,7 @@
There is currently one foreign-data wrapper validator function
provided:
<filename>postgresql_fdw_validator</filename>, which accepts
- options corresponding to <application>libpq</> connection
+ options corresponding to <application>libpq</application> connection
parameters.
</para>
</refsect1>
@@ -120,22 +121,22 @@
<title>Examples</title>
<para>
- Create a foreign-data wrapper <literal>dummy</>:
+ Create a foreign-data wrapper <literal>dummy</literal>:
<programlisting>
CREATE FOREIGN DATA WRAPPER dummy;
</programlisting>
</para>
<para>
- Create a foreign-data wrapper <literal>postgresql</> with
- validator function <literal>postgresql_fdw_validator</>:
+ Create a foreign-data wrapper <literal>postgresql</literal> with
+ validator function <literal>postgresql_fdw_validator</literal>:
<programlisting>
CREATE FOREIGN DATA WRAPPER postgresql VALIDATOR postgresql_fdw_validator;
</programlisting>
</para>
<para>
- Create a foreign-data wrapper <literal>mywrapper</> with some
+ Create a foreign-data wrapper <literal>mywrapper</literal> with some
options:
<programlisting>
CREATE FOREIGN DATA WRAPPER mywrapper
@@ -165,10 +166,10 @@
<title>See Also</title>
<simplelist type="inline">
- <member><xref linkend="sql-alterforeigndatawrapper" endterm="sql-alterforeigndatawrapper-title"></member>
- <member><xref linkend="sql-dropforeigndatawrapper" endterm="sql-dropforeigndatawrapper-title"></member>
- <member><xref linkend="sql-createserver" endterm="sql-createserver-title"></member>
- <member><xref linkend="sql-createusermapping" endterm="sql-createusermapping-title"></member>
+ <member><xref linkend="sql-alterforeigndatawrapper" endterm="sql-alterforeigndatawrapper-title"/></member>
+ <member><xref linkend="sql-dropforeigndatawrapper" endterm="sql-dropforeigndatawrapper-title"/></member>
+ <member><xref linkend="sql-createserver" endterm="sql-createserver-title"/></member>
+ <member><xref linkend="sql-createusermapping" endterm="sql-createusermapping-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/create_function.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_function.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_function.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -110,9 +110,10 @@
<literal>OUT</literal>, <literal>INOUT</literal> ou
<literal>VARIADIC</literal>. En cas d'omission, la valeur par défaut est
<literal>IN</literal>.
- Only <literal>OUT</> arguments can follow a <literal>VARIADIC</> one.
- Also, <literal>OUT</> and <literal>INOUT</> arguments cannot be used
- together with the <literal>RETURNS TABLE</> notation.
+ Only <literal>OUT</literal> arguments can follow a
+ <literal>VARIADIC</literal> one.
+ Also, <literal>OUT</literal> and <literal>INOUT</literal> arguments cannot be used
+ together with the <literal>RETURNS TABLE</literal> notation.
</para>
</listitem>
</varlistentry>
@@ -167,7 +168,7 @@
An expression to be used as default value if the parameter is
not specified. The expression has to be coercible to the
argument type of the parameter.
- Only input (including <literal>INOUT</>) parameters can have a default
+ Only input (including <literal>INOUT</literal>) parameters can have a default
value. All input parameters following a
parameter with a default value must have default values as well.
</para>
@@ -210,10 +211,11 @@
<listitem>
<para>
- The name of an output column in the <literal>RETURNS TABLE</>
+ The name of an output column in the <literal>RETURNS TABLE</literal>
syntax. This is effectively another way of declaring a named
- <literal>OUT</> parameter, except that <literal>RETURNS TABLE</>
- also implies <literal>RETURNS SETOF</>.
+ <literal>OUT</literal> parameter, except that <literal>RETURNS
+ TABLE</literal>
+ also implies <literal>RETURNS SETOF</literal>.
</para>
</listitem>
</varlistentry>
@@ -223,7 +225,8 @@
<listitem>
<para>
- The data type of an output column in the <literal>RETURNS TABLE</>
+ The data type of an output column in the <literal>RETURNS
+ TABLE</literal>
syntax.
</para>
</listitem>
@@ -249,9 +252,9 @@
<listitem>
<para>
<literal>WINDOW</literal> indicates that the function is a
- <firstterm>window function</> rather than a plain function.
+ <firstterm>window function</firstterm> rather than a plain function.
This is currently only useful for functions written in C.
- The <literal>WINDOW</> attribute cannot be changed when
+ The <literal>WINDOW</literal> attribute cannot be changed when
replacing an existing function definition.
</para>
</listitem>
@@ -518,7 +521,7 @@
CREATE FUNCTION foo(int) ...
CREATE FUNCTION foo(int, int default 42) ...
</programlisting>
- A call <literal>foo(10)</> will fail due to the ambiguity about which
+ A call <literal>foo(10)</literal> will fail due to the ambiguity about which
function should be called.
</para>
@@ -606,7 +609,7 @@
SELECT * FROM dup(42);
</programlisting>
- Another way to return multiple columns is to use a <literal>TABLE</>
+ Another way to return multiple columns is to use a <literal>TABLE</literal>
function:
<programlisting>
CREATE FUNCTION dup(int) RETURNS TABLE(f1 int, f2 text)
@@ -615,8 +618,8 @@
SELECT * FROM dup(42);
</programlisting>
- However, a <literal>TABLE</> function is different from the
- preceding examples, because it actually returns a <emphasis>set</>
+ However, a <literal>TABLE</literal> function is different from the
+ preceding examples, because it actually returns a <emphasis>set</emphasis>
of records, not just one record.
</para>
</refsect1>
@@ -720,15 +723,12 @@
<title>Voir aussi</title>
<simplelist type="inline">
- <member><xref linkend="sql-alterfunction"
- endterm="sql-alterfunction-title"/></member>
- <member><xref linkend="sql-dropfunction"
- endterm="sql-dropfunction-title"/></member>
+ <member><xref linkend="sql-alterfunction" endterm="sql-alterfunction-title"/></member>
+ <member><xref linkend="sql-dropfunction" endterm="sql-dropfunction-title"/></member>
<member><xref linkend="sql-grant" endterm="sql-grant-title"/></member>
<member><xref linkend="sql-load" endterm="sql-load-title"/></member>
<member><xref linkend="sql-revoke" endterm="sql-revoke-title"/></member>
- <member><xref linkend="app-createlang"
- endterm="app-createlang-title"/></member>
+ <member><xref linkend="app-createlang" endterm="app-createlang-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/create_index.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_index.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_index.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -239,7 +239,7 @@
<para>
Le nom d'un paramètre de stockage spécifique à la méthode d'indexage.
Voir <xref linkend="sql-createindex-storage-parameters"
- endterm="sql-createindex-storage-parameters-title"> pour les détails.
+ endterm="sql-createindex-storage-parameters-title"/> pour les détails.
</para>
</listitem>
</varlistentry>
@@ -301,6 +301,8 @@
</para>
</listitem>
</varlistentry>
+ </variablelist>
+
<para>
<literal>GIN</literal> indexes accept a different parameter:
</para>
@@ -308,23 +310,24 @@
<variablelist>
<varlistentry>
- <term><literal>FASTUPDATE</></term>
+ <term><literal>FASTUPDATE</literal></term>
<listitem>
<para>
This setting controls usage of the fast update technique described in
- <xref linkend="gin-fast-update">. It is a Boolean parameter:
- <literal>ON</> enables fast update, <literal>OFF</> disables it.
- (Alternative spellings of <literal>ON</> and <literal>OFF</> are
- allowed as described in <xref linkend="config-setting">.) The
- default is <literal>ON</>.
+ <xref linkend="gin-fast-update"/>. It is a Boolean parameter:
+ <literal>ON</literal> enables fast update, <literal>OFF</literal> disables it.
+ (Alternative spellings of <literal>ON</literal> and <literal>OFF</literal> are
+ allowed as described in <xref linkend="config-setting"/>.) The
+ default is <literal>ON</literal>.
</para>
<note>
<para>
- Turning <literal>FASTUPDATE</> off via <command>ALTER INDEX</> prevents
+ Turning <literal>FASTUPDATE</literal> off via <command>ALTER
+ INDEX</command> prevents
future insertions from going into the list of pending index entries,
but does not in itself flush previous entries. You might want to
- <command>VACUUM</> the table afterward to ensure the pending list is
+ <command>VACUUM</command> the table afterward to ensure the pending list is
emptied.
</para>
</note>
@@ -495,17 +498,19 @@
<para>
For most index methods, the speed of creating an index is
- dependent on the setting of <xref linkend="guc-maintenance-work-mem">.
+ dependent on the setting of <xref linkend="guc-maintenance-work-mem"/>.
Larger values will reduce the time needed for index creation, so long
as you don't make it larger than the amount of memory really available,
which would drive the machine into swapping. For hash indexes, the
- value of <xref linkend="guc-effective-cache-size"> is also relevant to
+ value of <xref linkend="guc-effective-cache-size"/> is also relevant to
index creation time: <productname>PostgreSQL</productname> will use one
of two different hash index creation methods depending on whether the
- estimated index size is more or less than <varname>effective_cache_size</>.
+ estimated index size is more or less than
+ <varname>effective_cache_size</varname>.
For best results, make sure that this parameter is also set to something
reflective of available memory, and be careful that the sum of
- <varname>maintenance_work_mem</> and <varname>effective_cache_size</> is
+ <varname>maintenance_work_mem</varname> and
+ <varname>effective_cache_size</varname> is
less than the machine's RAM less whatever space is needed by other
programs.
</para>
@@ -557,7 +562,7 @@
</para>
<para>
- To create a <acronym>GIN</> index with fast updates disabled:
+ To create a <acronym>GIN</acronym> index with fast updates disabled:
<programlisting>
CREATE INDEX gin_idx ON documents_table (locations) WITH (fastupdate = off);
</programlisting>
@@ -610,8 +615,7 @@
<title>Voir aussi</title>
<simplelist type="inline">
- <member><xref linkend="sql-alterindex"
- endterm="sql-alterindex-title"/></member>
+ <member><xref linkend="sql-alterindex" endterm="sql-alterindex-title"/></member>
<member><xref linkend="sql-dropindex" endterm="sql-dropindex-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/create_opclass.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_opclass.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_opclass.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -249,9 +249,10 @@
</para>
<para>
- Before <productname>PostgreSQL</productname> 8.4, the <literal>OPERATOR</>
- clause could include a <literal>RECHECK</> option. This is no longer
- supported because whether an index operator is <quote>lossy</> is now
+ Before <productname>PostgreSQL</productname> 8.4, the
+ <literal>OPERATOR</literal>
+ clause could include a <literal>RECHECK</literal> option. This is no longer
+ supported because whether an index operator is <quote>lossy</quote> is now
determined on-the-fly at runtime. This allows efficient handling of
cases where an operator might or might not be lossy.
</para>
Modified: traduc/trunk/postgresql/ref/create_server.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_server.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_server.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1,9 +1,10 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_server.sgml,v 1.3 2009-02-27 07:20:00 petere Exp $
-PostgreSQL documentation
--->
+<?xml version="1.0" encoding="ISO-8859-15"?>
+<!-- Dernière modification
+ le $Date: 2009-04-13 17:20:17 +0200 (lun 13 avr 2009) $
+ par $Author: gleu $
+ révision $Revision: 1293 $ -->
-<refentry id="SQL-CREATESERVER">
+<refentry id="sql-createserver">
<refmeta>
<refentrytitle id="sql-createserver-title">CREATE SERVER</refentrytitle>
<refmiscinfo>SQL - Language Statements</refmiscinfo>
@@ -39,7 +40,7 @@
</para>
<para>
- Creating a server requires <literal>USAGE</> privilege on the
+ Creating a server requires <literal>USAGE</literal> privilege on the
foreign-data wrapper being used.
</para>
</refsect1>
@@ -102,16 +103,16 @@
<title>Examples</title>
<para>
- Create a server <literal>foo</> that uses the built-in foreign-data
- wrapper <literal>default</>:
+ Create a server <literal>foo</literal> that uses the built-in foreign-data
+ wrapper <literal>default</literal>:
<programlisting>
CREATE SERVER foo FOREIGN DATA WRAPPER "default";
</programlisting>
</para>
<para>
- Create a server <literal>myserver</> that uses the
- foreign-data wrapper <literal>pgsql</>:
+ Create a server <literal>myserver</literal> that uses the
+ foreign-data wrapper <literal>pgsql</literal>:
<programlisting>
CREATE SERVER myserver FOREIGN DATA WRAPPER pgsql OPTIONS (host 'foo', dbname 'foodb', port '5432');
</programlisting>
@@ -130,10 +131,10 @@
<title>See Also</title>
<simplelist type="inline">
- <member><xref linkend="sql-alterserver" endterm="sql-alterserver-title"></member>
- <member><xref linkend="sql-dropserver" endterm="sql-dropserver-title"></member>
- <member><xref linkend="sql-createforeigndatawrapper" endterm="sql-createforeigndatawrapper-title"></member>
- <member><xref linkend="sql-createusermapping" endterm="sql-createusermapping-title"></member>
+ <member><xref linkend="sql-alterserver" endterm="sql-alterserver-title"/></member>
+ <member><xref linkend="sql-dropserver" endterm="sql-dropserver-title"/></member>
+ <member><xref linkend="sql-createforeigndatawrapper" endterm="sql-createforeigndatawrapper-title"/></member>
+ <member><xref linkend="sql-createusermapping" endterm="sql-createusermapping-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/create_table.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_table.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_table.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -219,12 +219,12 @@
</para>
<para>
- <literal>CHECK</> constraints are merged in essentially the same way as
+ <literal>CHECK</literal> constraints are merged in essentially the same way as
columns: if multiple parent tables and/or the new table definition
- contain identically-named <literal>CHECK</> constraints, these
+ contain identically-named <literal>CHECK</literal> constraints, these
constraints must all have the same check expression, or an error will be
reported. Constraints having the same name and expression will
- be merged into one copy. Notice that an unnamed <literal>CHECK</>
+ be merged into one copy. Notice that an unnamed <literal>CHECK</literal>
constraint in the new table will never be merged, since a unique name
will always be chosen for it.
</para>
@@ -701,7 +701,7 @@
available for tables are listed below. For each parameter, there is an
additional, identically named parameter, prefixed with
<literal>toast.</literal> which can be used to control the behavior of the
- supplementary storage table, if any; see <xref linkend="storage-toast">.
+ supplementary storage table, if any; see <xref linkend="storage-toast"/>.
Note that the supplementary storage table inherits the
<literal>autovacuum</literal> values from its parent table, if there are
no <literal>toast.autovacuum_*</literal> settings set.
@@ -710,7 +710,8 @@
<variablelist>
<varlistentry>
- <term><literal>fillfactor</>, <literal>toast.fillfactor</literal> (<type>integer</>)</term>
+ <term><literal>fillfactor</literal>, <literal>toast.fillfactor</literal>
+ (<type>integer</type>)</term>
<listitem>
<para>
Le facteur de remplissage d'une table est un pourcentage entre 10 et 100.
@@ -729,108 +730,117 @@
</varlistentry>
<varlistentry>
- <term><literal>autovacuum_enabled</>, <literal>toast.autovacuum_enabled</literal> (<type>boolean</>)</term>
+ <term><literal>autovacuum_enabled</literal>,
+ <literal>toast.autovacuum_enabled</literal> (<type>boolean</type>)</term>
<listitem>
<para>
Enables or disables the autovacuum daemon on a particular table.
- If true, the autovacuum daemon will initiate a <command>VACUUM</> operation
+ If true, the autovacuum daemon will initiate a <command>VACUUM</command> operation
on a particular table when the number of updated or deleted tuples exceeds
- <literal>autovacuum_vacuum_threshold</> plus
- <literal>autovacuum_vacuum_scale_factor</> times the number of live tuples
+ <literal>autovacuum_vacuum_threshold</literal> plus
+ <literal>autovacuum_vacuum_scale_factor</literal> times the number of live tuples
currently estimated to be in the relation.
- Similarly, it will initiate an <command>ANALYZE</> operation when the
+ Similarly, it will initiate an <command>ANALYZE</command> operation when the
number of inserted, updated or deleted tuples exceeds
- <literal>autovacuum_analyze_threshold</> plus
- <literal>autovacuum_analyze_scale_factor</> times the number of live tuples
+ <literal>autovacuum_analyze_threshold</literal> plus
+ <literal>autovacuum_analyze_scale_factor</literal> times the number of live tuples
currently estimated to be in the relation.
If false, this table will not be autovacuumed, except to prevent
- transaction Id wraparound. See <xref linkend="vacuum-for-wraparound"> for
+ transaction Id wraparound. See <xref linkend="vacuum-for-wraparound"/> for
more about wraparound prevention.
Observe that this variable inherits its value from the <xref
- linkend="guc-autovacuum"> setting.
+ linkend="guc-autovacuum"/> setting.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>autovacuum_vacuum_threshold</>, <literal>toast.autovacuum_vacuum_threshold</literal> (<type>integer</>)</term>
+ <term><literal>autovacuum_vacuum_threshold</literal>,
+ <literal>toast.autovacuum_vacuum_threshold</literal> (<type>integer</type>)</term>
<listitem>
<para>
Minimum number of updated or deleted tuples before initiate a
- <command>VACUUM</> operation on a particular table.
+ <command>VACUUM</command> operation on a particular table.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>autovacuum_vacuum_scale_factor</>, <literal>toast.autovacuum_vacuum_scale_factor</literal> (<type>float4</>)</term>
+ <term><literal>autovacuum_vacuum_scale_factor</literal>,
+ <literal>toast.autovacuum_vacuum_scale_factor</literal> (<type>float4</type>)</term>
<listitem>
<para>
- Multiplier for <structfield>reltuples</> to add to
- <literal>autovacuum_vacuum_threshold</>.
+ Multiplier for <structfield>reltuples</structfield> to add to
+ <literal>autovacuum_vacuum_threshold</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>autovacuum_analyze_threshold</>, <literal>toast.autovacuum_analyze_threshold</literal> (<type>integer</>)</term>
+ <term><literal>autovacuum_analyze_threshold</literal>,
+ <literal>toast.autovacuum_analyze_threshold</literal> (<type>integer</type>)</term>
<listitem>
<para>
Minimum number of inserted, updated, or deleted tuples before initiate an
- <command>ANALYZE</> operation on a particular table.
+ <command>ANALYZE</command> operation on a particular table.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>autovacuum_analyze_scale_factor</>, <literal>toast.autovacuum_analyze_scale_factor</literal> (<type>float4</>)</term>
+ <term><literal>autovacuum_analyze_scale_factor</literal>,
+ <literal>toast.autovacuum_analyze_scale_factor</literal> (<type>float4</type>)</term>
<listitem>
<para>
- Multiplier for <structfield>reltuples</> to add to
- <literal>autovacuum_analyze_threshold</>.
+ Multiplier for <structfield>reltuples</structfield> to add to
+ <literal>autovacuum_analyze_threshold</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>autovacuum_vacuum_cost_delay</>, <literal>toast.autovacuum_vacuum_cost_delay</literal> (<type>integer</>)</term>
+ <term><literal>autovacuum_vacuum_cost_delay</literal>,
+ <literal>toast.autovacuum_vacuum_cost_delay</literal> (<type>integer</type>)</term>
<listitem>
<para>
- Custom <xref linkend="guc-autovacuum-vacuum-cost-delay"> parameter.
+ Custom <xref linkend="guc-autovacuum-vacuum-cost-delay"/> parameter.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>autovacuum_vacuum_cost_limit</>, <literal>toast.autovacuum_vacuum_cost_limit</literal> (<type>integer</>)</term>
+ <term><literal>autovacuum_vacuum_cost_limit</literal>,
+ <literal>toast.autovacuum_vacuum_cost_limit</literal> (<type>integer</type>)</term>
<listitem>
<para>
- Custom <xref linkend="guc-autovacuum-vacuum-cost-limit"> parameter.
+ Custom <xref linkend="guc-autovacuum-vacuum-cost-limit"/> parameter.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>autovacuum_freeze_min_age</>, <literal>toast.autovacuum_freeze_min_age</literal> (<type>integer</>)</term>
+ <term><literal>autovacuum_freeze_min_age</literal>,
+ <literal>toast.autovacuum_freeze_min_age</literal> (<type>integer</type>)</term>
<listitem>
<para>
- Custom <xref linkend="guc-vacuum-freeze-min-age"> parameter. Note that
+ Custom <xref linkend="guc-vacuum-freeze-min-age"/> parameter. Note that
autovacuum will ignore attempts to set a per-table
- <literal>autovacuum_freeze_min_age</> larger than the half system-wide
- <xref linkend="guc-autovacuum-freeze-max-age"> setting.
+ <literal>autovacuum_freeze_min_age</literal> larger than the half system-wide
+ <xref linkend="guc-autovacuum-freeze-max-age"/> setting.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>autovacuum_freeze_max_age</>, <literal>toast.autovacuum_freeze_max_age</literal> (<type>integer</>)</term>
+ <term><literal>autovacuum_freeze_max_age</literal>,
+ <literal>toast.autovacuum_freeze_max_age</literal> (<type>integer</type>)</term>
<listitem>
<para>
- Custom <xref linkend="guc-autovacuum-freeze-max-age"> parameter. Note that
+ Custom <xref linkend="guc-autovacuum-freeze-max-age"/> parameter. Note that
autovacuum will ignore attempts to set a per-table
- <literal>autovacuum_freeze_max_age</> larger than the system-wide setting
+ <literal>autovacuum_freeze_max_age</literal> larger than the system-wide setting
(it can only be set smaller). Note that while you can set
- <literal>autovacuum_freeze_max_age</> very small, or even zero, this is
+ <literal>autovacuum_freeze_max_age</literal> very small, or even zero, this is
usually unwise since it will force frequent vacuuming.
</para>
</listitem>
@@ -840,7 +850,7 @@
<term><literal>autovacuum_freeze_table_age</literal> (<type>integer</type>)</term>
<listitem>
<para>
- Custom <xref linkend="guc-vacuum-freeze-table-age"> parameter.
+ Custom <xref linkend="guc-vacuum-freeze-table-age"/> parameter.
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/ref/create_table_as.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_table_as.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_table_as.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -194,13 +194,13 @@
<link linkend="sql-table">TABLE</link> ou
<xref linkend="sql-values" endterm="sql-values-title"/>, voire une commande
<xref linkend="sql-execute" endterm="sql-execute-title"/> qui exécute un
- <command>SELECT</command> préparé, <command>TABLE</> ou une requête <command>VALUES</command>.
+ <command>SELECT</command> préparé, <command>TABLE</command> ou une requête <command>VALUES</command>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>WITH [ NO ] DATA</></term>
+ <term><literal>WITH [ NO ] DATA</literal></term>
<listitem>
<para>
This clause specifies whether or not the data produced by the query
Modified: traduc/trunk/postgresql/ref/create_trigger.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_trigger.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_trigger.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -277,7 +277,7 @@
<para>
The ability to fire triggers for <command>TRUNCATE</command> is a
- <productname>PostgreSQL</> extension of the SQL standard.
+ <productname>PostgreSQL</productname> extension of the SQL standard.
</para>
</refsect1>
Modified: traduc/trunk/postgresql/ref/create_type.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_type.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_type.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -302,9 +302,10 @@
<replaceable class="parameter">alignment</replaceable>, and
<replaceable class="parameter">storage</replaceable> are copied from the
named type. (It is possible, though usually undesirable, to override
- some of these values by specifying them along with the <literal>LIKE</>
+ some of these values by specifying them along with the
+ <literal>LIKE</literal>
clause.) Specifying representation this way is especially useful when
- the low-level implementation of the new type <quote>piggybacks</> on an
+ the low-level implementation of the new type <quote>piggybacks</quote> on an
existing type in some fashion.
</para>
@@ -313,15 +314,15 @@
<replaceable class="parameter">preferred</replaceable> parameters can be
used to help control which implicit cast will be applied in ambiguous
situations. Each data type belongs to a category named by a single ASCII
- character, and each type is either <quote>preferred</> or not within its
+ character, and each type is either <quote>preferred</quote> or not within its
category. The parser will prefer casting to preferred types (but only from
other types within the same category) when this rule is helpful in
resolving overloaded functions or operators. For more details see <xref
- linkend="typeconv">. For types that have no implicit casts to or from any
+ linkend="typeconv"/>. For types that have no implicit casts to or from any
other types, it is sufficient to leave these settings at the defaults.
However, for a group of related types that have implicit casts, it is often
helpful to mark them all as belonging to a category and select one or two
- of the <quote>most general</> types as being preferred within the category.
+ of the <quote>most general</quote> types as being preferred within the category.
The <replaceable class="parameter">category</replaceable> parameter is
especially useful when adding a user-defined type to an existing built-in
category, such as the numeric or string types. However, it is also
@@ -555,7 +556,7 @@
<replaceable class="parameter">alignment</replaceable>, and
<replaceable class="parameter">storage</replaceable>
are copied from that type, unless overridden by explicit
- specification elsewhere in this <command>CREATE TYPE</> command.
+ specification elsewhere in this <command>CREATE TYPE</command> command.
</para>
</listitem>
</varlistentry>
@@ -565,9 +566,10 @@
<listitem>
<para>
The category code (a single ASCII character) for this type.
- The default is <literal>'U'</> for <quote>user-defined type</>.
+ The default is <literal>'U'</literal> for <quote>user-defined
+ type</quote>.
Other standard category codes can be found in
- <xref linkend="catalog-typcategory-table">. You may also choose
+ <xref linkend="catalog-typcategory-table"/>. You may also choose
other ASCII characters in order to create custom categories.
</para>
</listitem>
Modified: traduc/trunk/postgresql/ref/create_user_mapping.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_user_mapping.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/create_user_mapping.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1,9 +1,10 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_user_mapping.sgml,v 1.4 2009-02-27 07:20:00 petere Exp $
-PostgreSQL documentation
--->
+<?xml version="1.0" encoding="ISO-8859-15"?>
+<!-- Dernière modification
+ le $Date: 2009-04-13 17:20:17 +0200 (lun 13 avr 2009) $
+ par $Author: gleu $
+ révision $Revision: 1293 $ -->
-<refentry id="SQL-CREATEUSERMAPPING">
+<refentry id="sql-createusermapping">
<refmeta>
<refentrytitle id="sql-createusermapping-title">CREATE USER MAPPING</refentrytitle>
<refmiscinfo>SQL - Language Statements</refmiscinfo>
@@ -37,7 +38,7 @@
<para>
The owner of a foreign server can create user mappings for that
server for any user. Also, a user can create a user mapping for
- his own user name if <literal>USAGE</> privilege on the server has
+ his own user name if <literal>USAGE</literal> privilege on the server has
been granted to the user.
</para>
</refsect1>
@@ -51,8 +52,8 @@
<listitem>
<para>
The name of an existing user that is mapped to foreign server.
- <literal>CURRENT_USER</> and <literal>USER</> match the name of
- the current user. <literal>PUBLIC</> is used to match all
+ <literal>CURRENT_USER</literal> and <literal>USER</literal> match the name of
+ the current user. <literal>PUBLIC</literal> is used to match all
present and future user names in the system.
</para>
</listitem>
@@ -86,7 +87,8 @@
<title>Examples</title>
<para>
- Create a user mapping for user <literal>bob</>, server <literal>foo</>:
+ Create a user mapping for user <literal>bob</literal>, server
+ <literal>foo</literal>:
<programlisting>
CREATE USER MAPPING FOR bob SERVER foo OPTIONS (user 'bob', password 'secret');
</programlisting>
@@ -106,10 +108,10 @@
<title>See Also</title>
<simplelist type="inline">
- <member><xref linkend="sql-alterusermapping" endterm="sql-alterusermapping-title"></member>
- <member><xref linkend="sql-dropusermapping" endterm="sql-dropusermapping-title"></member>
- <member><xref linkend="sql-createforeigndatawrapper" endterm="sql-createforeigndatawrapper-title"></member>
- <member><xref linkend="sql-createserver" endterm="sql-createserver-title"></member>
+ <member><xref linkend="sql-alterusermapping" endterm="sql-alterusermapping-title"/></member>
+ <member><xref linkend="sql-dropusermapping" endterm="sql-dropusermapping-title"/></member>
+ <member><xref linkend="sql-createforeigndatawrapper" endterm="sql-createforeigndatawrapper-title"/></member>
+ <member><xref linkend="sql-createserver" endterm="sql-createserver-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/createdb.xml
===================================================================
--- traduc/trunk/postgresql/ref/createdb.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/createdb.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -106,8 +106,10 @@
</varlistentry>
<varlistentry>
- <term><option>-l <replaceable class="parameter">locale</replaceable></></term>
- <term><option>--locale <replaceable class="parameter">locale</replaceable></></term>
+ <term><option>-l <replaceable
+ class="parameter">locale</replaceable></option></term>
+ <term><option>--locale <replaceable
+ class="parameter">locale</replaceable></option></term>
<listitem>
<para>
Specifies the locale to be used in this database. This is equivalent
@@ -117,7 +119,8 @@
</varlistentry>
<varlistentry>
- <term><option>--lc-collate <replaceable class="parameter">locale</replaceable></></term>
+ <term><option>--lc-collate <replaceable
+ class="parameter">locale</replaceable></option></term>
<listitem>
<para>
Specifies the LC_COLLATE setting to be used in this database.
@@ -126,7 +129,8 @@
</varlistentry>
<varlistentry>
- <term><option>--lc-ctype <replaceable class="parameter">locale</replaceable></></term>
+ <term><option>--lc-ctype <replaceable
+ class="parameter">locale</replaceable></option></term>
<listitem>
<para>
Specifies the LC_CTYPE setting to be used in this database.
@@ -216,8 +220,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
Modified: traduc/trunk/postgresql/ref/createlang.xml
===================================================================
--- traduc/trunk/postgresql/ref/createlang.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/createlang.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -140,8 +140,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
Modified: traduc/trunk/postgresql/ref/createuser.xml
===================================================================
--- traduc/trunk/postgresql/ref/createuser.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/createuser.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -296,8 +296,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
Modified: traduc/trunk/postgresql/ref/declare.xml
===================================================================
--- traduc/trunk/postgresql/ref/declare.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/declare.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -216,7 +216,7 @@
<para>
Backward fetches are also disallowed when the query
- includes <literal>FOR UPDATE</> or <literal>FOR SHARE</>; therefore
+ includes <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal>; therefore
<literal>SCROLL</literal> may not be specified in this case.
</para>
@@ -228,35 +228,38 @@
options.
De plus, les lignes renvoyées seront les versions les plus à jour ; du
coup, ces options fournissent l'équivalent de ce que le standard SQL appelle
- un <quote>curseur sensible</quote>. (Specifying <literal>INSENSITIVE</>
- together with <literal>FOR UPDATE</> or <literal>FOR SHARE</> is an error.)
+ un <quote>curseur sensible</quote>. (Specifying
+ <literal>INSENSITIVE</literal>
+ together with <literal>FOR UPDATE</literal> or <literal>FOR SHARE</literal> is an error.)
</para>
<caution>
<para>
- It is generally recommended to use <literal>FOR UPDATE</> if the cursor
- is intended to be used with <command>UPDATE ... WHERE CURRENT OF</> or
- <command>DELETE ... WHERE CURRENT OF</>. Using <literal>FOR UPDATE</>
+ It is generally recommended to use <literal>FOR UPDATE</literal> if the cursor
+ is intended to be used with <command>UPDATE ... WHERE CURRENT OF</command> or
+ <command>DELETE ... WHERE CURRENT OF</command>. Using <literal>FOR
+ UPDATE</literal>
prevents other sessions from changing the rows between the time they are
- fetched and the time they are updated. Without <literal>FOR UPDATE</>,
- a subsequent <literal>WHERE CURRENT OF</> command will have no effect if
+ fetched and the time they are updated. Without <literal>FOR
+ UPDATE</literal>,
+ a subsequent <literal>WHERE CURRENT OF</literal> command will have no effect if
the row was changed since the cursor was created.
</para>
<para>
- Another reason to use <literal>FOR UPDATE</> is that without it, a
- subsequent <literal>WHERE CURRENT OF</> might fail if the cursor query
+ Another reason to use <literal>FOR UPDATE</literal> is that without it, a
+ subsequent <literal>WHERE CURRENT OF</literal> might fail if the cursor query
does not meet the SQL standard's rules for being <quote>simply
- updatable</> (in particular, the cursor must reference just one table
- and not use grouping or <literal>ORDER BY</>). Cursors
+ updatable</quote> (in particular, the cursor must reference just one table
+ and not use grouping or <literal>ORDER BY</literal>). Cursors
that are not simply updatable might work, or might not, depending on plan
choice details; so in the worst case, an application might work in testing
and then fail in production.
</para>
<para>
- The main reason not to use <literal>FOR UPDATE</> with <literal>WHERE
- CURRENT OF</> is if you need the cursor to be scrollable, or to be
+ The main reason not to use <literal>FOR UPDATE</literal> with <literal>WHERE
+ CURRENT OF</literal> is if you need the cursor to be scrollable, or to be
insensitive to the subsequent updates (that is, continue to show the old
data). If this is a requirement, pay close heed to the caveats shown
above.
Modified: traduc/trunk/postgresql/ref/delete.xml
===================================================================
--- traduc/trunk/postgresql/ref/delete.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/delete.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -153,9 +153,9 @@
sur la table cible du <command>DELETE</command>.
Notez que <literal>WHERE CURRENT OF</literal> ne peut pas se voir ajouter
de condition booléenne. See
- <xref linkend="sql-declare" endterm="sql-declare-title">
+ <xref linkend="sql-declare" endterm="sql-declare-title"/>
for more information about using cursors with
- <literal>WHERE CURRENT OF</>.
+ <literal>WHERE CURRENT OF</literal>.
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/ref/drop_foreign_data_wrapper.xml
===================================================================
--- traduc/trunk/postgresql/ref/drop_foreign_data_wrapper.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/drop_foreign_data_wrapper.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1,9 +1,10 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/drop_foreign_data_wrapper.sgml,v 1.1 2008-12-19 16:25:16 petere Exp $
-PostgreSQL documentation
--->
+<?xml version="1.0" encoding="ISO-8859-15"?>
+<!-- Dernière modification
+ le $Date: 2009-04-13 17:20:17 +0200 (lun 13 avr 2009) $
+ par $Author: gleu $
+ révision $Revision: 1293 $ -->
-<refentry id="SQL-DROPFOREIGNDATAWRAPPER">
+<refentry id="sql-dropforeigndatawrapper">
<refmeta>
<refentrytitle id="sql-dropforeigndatawrapper-title">DROP FOREIGN DATA WRAPPER</refentrytitle>
<refmiscinfo>SQL - Language Statements</refmiscinfo>
@@ -83,7 +84,7 @@
<title>Examples</title>
<para>
- Drop the foreign-data wrapper <literal>dbi</>:
+ Drop the foreign-data wrapper <literal>dbi</literal>:
<programlisting>
DROP FOREIGN DATA WRAPPER dbi;
</programlisting>
@@ -95,8 +96,8 @@
<para>
<command>DROP FOREIGN DATA WRAPPER</command> conforms to ISO/IEC
- 9075-9 (SQL/MED). The <literal>IF EXISTS</> clause is
- a <productname>PostgreSQL</> extension.
+ 9075-9 (SQL/MED). The <literal>IF EXISTS</literal> clause is
+ a <productname>PostgreSQL</productname> extension.
</para>
</refsect1>
@@ -104,8 +105,8 @@
<title>See Also</title>
<simplelist type="inline">
- <member><xref linkend="sql-createforeigndatawrapper" endterm="sql-createforeigndatawrapper-title"></member>
- <member><xref linkend="sql-alterforeigndatawrapper" endterm="sql-alterforeigndatawrapper-title"></member>
+ <member><xref linkend="sql-createforeigndatawrapper" endterm="sql-createforeigndatawrapper-title"/></member>
+ <member><xref linkend="sql-alterforeigndatawrapper" endterm="sql-alterforeigndatawrapper-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/drop_function.xml
===================================================================
--- traduc/trunk/postgresql/ref/drop_function.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/drop_function.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -67,13 +67,13 @@
<listitem>
<para>
Le mode d'un argument : <literal>IN</literal>, <literal>OUT</literal>,
- <literal>INOUT</literal> ou <literal>VARIADIC</>. Sans précision, la valeur
+ <literal>INOUT</literal> ou <literal>VARIADIC</literal>. Sans précision, la valeur
par défaut est
<literal>IN</literal>. <command>DROP FUNCTION</command> ne s'intéresse pas
aux arguments <literal>OUT</literal> car seuls ceux
en entrée déterminent l'identité de la fonction.
Il est ainsi suffisant de lister les arguments <literal>IN</literal>,
- <literal>INOUT</literal> et <literal>VARIADIC</>.
+ <literal>INOUT</literal> et <literal>VARIADIC</literal>.
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/ref/drop_server.xml
===================================================================
--- traduc/trunk/postgresql/ref/drop_server.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/drop_server.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1,9 +1,10 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/drop_server.sgml,v 1.1 2008-12-19 16:25:16 petere Exp $
-PostgreSQL documentation
--->
+<?xml version="1.0" encoding="ISO-8859-15"?>
+<!-- Dernière modification
+ le $Date: 2009-04-13 17:20:17 +0200 (lun 13 avr 2009) $
+ par $Author: gleu $
+ révision $Revision: 1293 $ -->
-<refentry id="SQL-DROPSERVER">
+<refentry id="sql-dropserver">
<refmeta>
<refentrytitle id="sql-dropserver-title">DROP SERVER</refentrytitle>
<refmiscinfo>SQL - Language Statements</refmiscinfo>
@@ -83,7 +84,7 @@
<title>Examples</title>
<para>
- Drop a server <literal>foo</> if it exists:
+ Drop a server <literal>foo</literal> if it exists:
<programlisting>
DROP SERVER IF EXISTS foo;
</programlisting>
@@ -95,8 +96,8 @@
<para>
<command>DROP SERVER</command> conforms to ISO/IEC 9075-9
- (SQL/MED). The <literal>IF EXISTS</> clause is
- a <productname>PostgreSQL</> extension.
+ (SQL/MED). The <literal>IF EXISTS</literal> clause is
+ a <productname>PostgreSQL</productname> extension.
</para>
</refsect1>
@@ -104,8 +105,8 @@
<title>See Also</title>
<simplelist type="inline">
- <member><xref linkend="sql-createserver" endterm="sql-createserver-title"></member>
- <member><xref linkend="sql-alterserver" endterm="sql-alterserver-title"></member>
+ <member><xref linkend="sql-createserver" endterm="sql-createserver-title"/></member>
+ <member><xref linkend="sql-alterserver" endterm="sql-alterserver-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/drop_user_mapping.xml
===================================================================
--- traduc/trunk/postgresql/ref/drop_user_mapping.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/drop_user_mapping.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -1,9 +1,10 @@
-<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/drop_user_mapping.sgml,v 1.2 2009-01-20 09:10:20 petere Exp $
-PostgreSQL documentation
--->
+<?xml version="1.0" encoding="ISO-8859-15"?>
+<!-- Dernière modification
+ le $Date: 2009-04-13 17:20:17 +0200 (lun 13 avr 2009) $
+ par $Author: gleu $
+ révision $Revision: 1293 $ -->
-<refentry id="SQL-DROPUSERMAPPING">
+<refentry id="sql-dropusermapping">
<refmeta>
<refentrytitle id="sql-dropusermapping-title">DROP USER MAPPING</refentrytitle>
<refmiscinfo>SQL - Language Statements</refmiscinfo>
@@ -35,7 +36,7 @@
<para>
The owner of a foreign server can drop user mappings for that server
for any user. Also, a user can drop a user mapping for his own
- user name if <literal>USAGE</> privilege on the server has been
+ user name if <literal>USAGE</literal> privilege on the server has been
granted to the user.
</para>
</refsect1>
@@ -58,9 +59,9 @@
<term><replaceable class="parameter">username</replaceable></term>
<listitem>
<para>
- User name of the mapping. <literal>CURRENT_USER</>
- and <literal>USER</> match the name of the current
- user. <literal>PUBLIC</> is used to match all present and
+ User name of the mapping. <literal>CURRENT_USER</literal>
+ and <literal>USER</literal> match the name of the current
+ user. <literal>PUBLIC</literal> is used to match all present and
future user names in the system.
</para>
</listitem>
@@ -81,7 +82,7 @@
<title>Examples</title>
<para>
- Drop a user mapping <literal>bob</>, server <literal>foo</> if it exists:
+ Drop a user mapping <literal>bob</literal>, server <literal>foo</literal> if it exists:
<programlisting>
DROP USER MAPPING IF EXISTS FOR bob SERVER foo;
</programlisting>
@@ -93,8 +94,8 @@
<para>
<command>DROP USER MAPPING</command> conforms to ISO/IEC 9075-9
- (SQL/MED). The <literal>IF EXISTS</> clause is
- a <productname>PostgreSQL</> extension.
+ (SQL/MED). The <literal>IF EXISTS</literal> clause is
+ a <productname>PostgreSQL</productname> extension.
</para>
</refsect1>
@@ -102,8 +103,8 @@
<title>See Also</title>
<simplelist type="inline">
- <member><xref linkend="sql-createusermapping" endterm="sql-createusermapping-title"></member>
- <member><xref linkend="sql-alterusermapping" endterm="sql-alterusermapping-title"></member>
+ <member><xref linkend="sql-createusermapping" endterm="sql-createusermapping-title"/></member>
+ <member><xref linkend="sql-alterusermapping" endterm="sql-alterusermapping-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/dropdb.xml
===================================================================
--- traduc/trunk/postgresql/ref/dropdb.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/dropdb.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -131,8 +131,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
Modified: traduc/trunk/postgresql/ref/droplang.xml
===================================================================
--- traduc/trunk/postgresql/ref/droplang.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/droplang.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -149,8 +149,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
Modified: traduc/trunk/postgresql/ref/dropuser.xml
===================================================================
--- traduc/trunk/postgresql/ref/dropuser.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/dropuser.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -133,8 +133,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
Modified: traduc/trunk/postgresql/ref/grant.xml
===================================================================
--- traduc/trunk/postgresql/ref/grant.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/grant.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -38,11 +38,11 @@
TO { [ GROUP ] <replaceable class="PARAMETER">nomrole</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
GRANT { USAGE | ALL [ PRIVILEGES ] }
- ON FOREIGN DATA WRAPPER <replaceable>fdwname</> [, ...]
+ ON FOREIGN DATA WRAPPER <replaceable>fdwname</replaceable> [, ...]
TO { [ GROUP ] <replaceable class="PARAMETER">rolename</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
GRANT { USAGE | ALL [ PRIVILEGES ] }
- ON FOREIGN SERVER <replaceable>servername</> [, ...]
+ ON FOREIGN SERVER <replaceable>servername</replaceable> [, ...]
TO { [ GROUP ] <replaceable class="PARAMETER">rolename</replaceable> | PUBLIC } [, ...] [ WITH GRANT OPTION ]
GRANT { EXECUTE | ALL [ PRIVILEGES ] }
@@ -167,7 +167,7 @@
<para>
Autorise <xref linkend="sql-insert" endterm="sql-insert-title"/> d'une
nouvelle ligne dans la table indiquée. If specific columns are listed,
- only those columns may be assigned to in the <command>INSERT</>
+ only those columns may be assigned to in the <command>INSERT</command>
command (other columns will therefore receive default values). Autorise aussi
<xref linkend="sql-copy" endterm="sql-copy-title"/> FROM.
</para>
@@ -209,7 +209,7 @@
<term>TRUNCATE</term>
<listitem>
<para>
- Allows <xref linkend="sql-truncate" endterm="sql-truncate-title"> on
+ Allows <xref linkend="sql-truncate" endterm="sql-truncate-title"/> on
the specified table.
</para>
</listitem>
@@ -381,7 +381,7 @@
</para>
<para>
- A user may perform <command>SELECT</>, <command>INSERT</>, etc. on a
+ A user may perform <command>SELECT</command>, <command>INSERT</command>, etc. on a
column if he holds that privilege for either the specific column or
its whole table. Granting the privilege at the table level and then
revoking it for one column will not do what you might wish: the
@@ -496,7 +496,7 @@
</para>
<para>
- For non-table objects there are other <command>\d</> commands
+ For non-table objects there are other <command>\d</command> commands
that can display their privileges.
</para>
@@ -510,7 +510,7 @@
droits par défaut (produisant, par exemple,
<literal>{=,miriam=arwdDxt/miriam}</literal>) puis les modifie en fonction de la requête
spécifiée. Entries are shown in <quote>Column access
- privileges</> only for columns with nondefault privileges.
+ privileges</quote> only for columns with nondefault privileges.
</para>
<para>
@@ -565,8 +565,9 @@
<productname>PostgreSQL</productname> autorise un propriétaire d'objet
à révoquer ses propres droits ordinaires : par exemple, le
propriétaire d'un objet peut le placer en lecture seule pour lui-même en
- révoquant ses propres droits <literal>INSERT</>,
- <literal>UPDATE</>, <literal>DELETE</>, and <literal>TRUNCATE</>. Le standard SQL
+ révoquant ses propres droits <literal>INSERT</literal>,
+ <literal>UPDATE</literal>, <literal>DELETE</literal>, and
+ <literal>TRUNCATE</literal>. Le standard SQL
ne l'autorise pas. La raison en est que
<productname>PostgreSQL</productname> traite les droits du propriétaire
comme ayant été donnés par le propriétaire ; il peut, de ce fait, aussi les
Modified: traduc/trunk/postgresql/ref/initdb.xml
===================================================================
--- traduc/trunk/postgresql/ref/initdb.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/initdb.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -96,8 +96,8 @@
<para>
<command>initdb</command> initializes the database cluster's default
locale and character set encoding. The character set encoding,
- collation order (<literal>LC_COLLATE</>) and character set classes
- (<literal>LC_CTYPE</>, e.g. upper, lower, digit) can be set separately
+ collation order (<literal>LC_COLLATE</literal>) and character set classes
+ (<literal>LC_CTYPE</literal>, e.g. upper, lower, digit) can be set separately
for a database when it is created. <command>initdb</command> determines
those settings for the <literal>template1</literal> database, which will
serve as the default for all other databases.
@@ -106,7 +106,7 @@
<para>
To alter the default collation order or character set classes, use the
<option>--lc-collate</option> and <option>--lc-ctype</option> options.
- Collation orders other than <literal>C</> or <literal>POSIX</> also have
+ Collation orders other than <literal>C</literal> or <literal>POSIX</literal> also have
a performance penalty. For these reasons it is important to choose the
right locale when running <command>initdb</command>.
</para>
@@ -115,14 +115,14 @@
The remaining locale categories can be changed later when the server
is started. You can also use <option>--locale</option> to set the
default for all locale categories, including collation order and
- character set classes. All server locale values (<literal>lc_*</>) can
- be displayed via <command>SHOW ALL</>.
- More details can be found in <xref linkend="locale">.
+ character set classes. All server locale values (<literal>lc_*</literal>) can
+ be displayed via <command>SHOW ALL</command>.
+ More details can be found in <xref linkend="locale"/>.
</para>
<para>
To alter the default encoding, use the <option>--encoding</option>.
- More details can be found in <xref linkend="multibyte">.
+ More details can be found in <xref linkend="multibyte"/>.
</para>
</refsect1>
Modified: traduc/trunk/postgresql/ref/insert.xml
===================================================================
--- traduc/trunk/postgresql/ref/insert.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/insert.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -74,8 +74,9 @@
Le droit <literal>INSERT</literal> sur une table est requis pour
pouvoir y insérer des lignes. If a column list is specified, you only
need <literal>INSERT</literal> privilege on the listed columns.
- Use of the <literal>RETURNING</> clause requires <literal>SELECT</>
- privilege on all columns mentioned in <literal>RETURNING</>. Si la clause <replaceable
+ Use of the <literal>RETURNING</literal> clause requires
+ <literal>SELECT</literal>
+ privilege on all columns mentioned in <literal>RETURNING</literal>. Si la clause <replaceable
class="parameter">requête</replaceable> est utilisée pour insérer des
lignes, le droit <literal>SELECT</literal> sur toute table ou colonne
utilisée dans la requête est également requis.
Modified: traduc/trunk/postgresql/ref/lock.xml
===================================================================
--- traduc/trunk/postgresql/ref/lock.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/lock.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -113,8 +113,8 @@
<listitem>
<para>
Le nom d'une table à verrouiller (éventuellement qualifié du nom du
- schéma). If <literal>ONLY</> is specified, only that table is
- locked. If <literal>ONLY</> is not specified, the table and all
+ schéma). If <literal>ONLY</literal> is specified, only that table is
+ locked. If <literal>ONLY</literal> is not specified, the table and all
its descendant tables (if any) are locked.
</para>
@@ -161,18 +161,20 @@
<literal>LOCK TABLE ... IN ACCESS SHARE MODE</literal> requiert les droits
<literal>SELECT</literal> sur la table cible. Toutes les autres formes de
<command>LOCK</command> requièrent au moins un des droits
- <literal>UPDATE</literal>, <literal>DELETE</literal> et <literal>TRUNCATE</>.
+ <literal>UPDATE</literal>, <literal>DELETE</literal> et
+ <literal>TRUNCATE</literal>.
</para>
<para>
- <command>LOCK TABLE</> is useless outside a transaction block: the lock
+ <command>LOCK TABLE</command> is useless outside a transaction block: the lock
would remain held only to the completion of the statement. Therefore
- <productname>PostgreSQL</productname> reports an error if <command>LOCK</>
+ <productname>PostgreSQL</productname> reports an error if
+ <command>LOCK</command>
is used outside a transaction block.
Use
- <xref linkend="sql-begin" endterm="sql-begin-title"> and
- <xref linkend="sql-commit" endterm="sql-commit-title">
- (or <xref linkend="sql-rollback" endterm="sql-rollback-title">)
+ <xref linkend="sql-begin" endterm="sql-begin-title"/> and
+ <xref linkend="sql-commit" endterm="sql-commit-title"/>
+ (or <xref linkend="sql-rollback" endterm="sql-rollback-title"/>)
to define a transaction block.
</para>
Modified: traduc/trunk/postgresql/ref/pg_config-ref.xml
===================================================================
--- traduc/trunk/postgresql/ref/pg_config-ref.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/pg_config-ref.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -69,7 +69,7 @@
</varlistentry>
<varlistentry>
- <term><option>--htmldir</option></>
+ <term><option>--htmldir</option></term>
<listitem>
<para>
Print the location of HTML documentation files.
@@ -309,7 +309,8 @@
<option>--ldflags</option>, <option>--ldflags_sl</option>
et <option>--libs</option> sont apparues avec <productname>PostgreSQL</productname>
8.1.
- The option <option>--htmldir</option> is new in <productname>PostgreSQL</> 8.4.
+ The option <option>--htmldir</option> is new in
+ <productname>PostgreSQL</productname> 8.4.
</para>
<para>
Modified: traduc/trunk/postgresql/ref/pg_dump.xml
===================================================================
--- traduc/trunk/postgresql/ref/pg_dump.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/pg_dump.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -585,7 +585,7 @@
</varlistentry>
<varlistentry>
- <term><option>--disable-dollar-quoting</></term>
+ <term><option>--disable-dollar-quoting</option></term>
<listitem>
<para>
This option disables the use of dollar quoting for function bodies,
@@ -595,7 +595,7 @@
</varlistentry>
<varlistentry>
- <term><option>--disable-triggers</></term>
+ <term><option>--disable-triggers</option></term>
<listitem>
<para>
This option is only relevant when creating a data-only dump.
@@ -607,9 +607,9 @@
</para>
<para>
- Presently, the commands emitted for <option>--disable-triggers</>
+ Presently, the commands emitted for <option>--disable-triggers</option>
must be done as superuser. So, you should also specify
- a superuser name with <option>-S</>, or preferably be careful to
+ a superuser name with <option>-S</option>, or preferably be careful to
start the resulting script as a superuser.
</para>
@@ -627,9 +627,9 @@
<para>
Do not wait forever to acquire shared table locks at the beginning of
the dump. Instead fail if unable to lock a table within the specified
- <replaceable class="parameter">timeout</>. The timeout may be
+ <replaceable class="parameter">timeout</replaceable>. The timeout may be
specified in any of the formats accepted by <command>SET
- statement_timeout</>. (Allowed values vary depending on the server
+ statement_timeout</command>. (Allowed values vary depending on the server
version you are dumping from, but an integer number of milliseconds
is accepted by all versions since 7.3. This option is ignored when
dumping from a pre-7.3 server.)
@@ -655,16 +655,17 @@
</varlistentry>
<varlistentry>
- <term><option>--use-set-session-authorization</></term>
+ <term><option>--use-set-session-authorization</option></term>
<listitem>
<para>
- Output SQL-standard <command>SET SESSION AUTHORIZATION</> commands
- instead of <command>ALTER OWNER</> commands to determine object
+ Output SQL-standard <command>SET SESSION AUTHORIZATION</command> commands
+ instead of <command>ALTER OWNER</command> commands to determine object
ownership. This makes the dump more standards compatible, but
depending on the history of the objects in the dump, might not restore
- properly. Also, a dump using <command>SET SESSION AUTHORIZATION</>
+ properly. Also, a dump using <command>SET SESSION
+ AUTHORIZATION</command>
will certainly require superuser privileges to restore correctly,
- whereas <command>ALTER OWNER</> requires lesser privileges.
+ whereas <command>ALTER OWNER</command> requires lesser privileges.
</para>
</listitem>
</varlistentry>
@@ -715,8 +716,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
@@ -755,11 +756,12 @@
<listitem>
<para>
Specifies a role name to be used to create the dump.
- This option causes <application>pg_dump</> to issue a
- <command>SET ROLE</> <replaceable class="parameter">rolename</>
+ This option causes <application>pg_dump</application> to issue a
+ <command>SET ROLE</command> <replaceable
+ class="parameter">rolename</replaceable>
command after connecting to the database. It is useful when the
- authenticated user (specified by <option>-U</>) lacks privileges
- needed by <application>pg_dump</>, but can switch to a role with
+ authenticated user (specified by <option>-U</option>) lacks privileges
+ needed by <application>pg_dump</application>, but can switch to a role with
the required rights. Some installations have a policy against
logging in directly as a superuser, and use of this option allows
dumps to be made without violating the policy.
@@ -868,16 +870,17 @@
<para>
Because <application>pg_dump</application> is used to transfer data
- to newer versions of <productname>PostgreSQL</>, the output of
+ to newer versions of <productname>PostgreSQL</productname>, the output of
<application>pg_dump</application> can be expected to load into
- <productname>PostgreSQL</> server versions newer than
- <application>pg_dump</>'s version. <application>pg_dump</> can also
- dump from <productname>PostgreSQL</> servers older than its own version.
+ <productname>PostgreSQL</productname> server versions newer than
+ <application>pg_dump</application>'s version.
+ <application>pg_dump</application> can also
+ dump from <productname>PostgreSQL</productname> servers older than its own version.
(Currently, servers back to version 7.0 are supported.)
- However, <application>pg_dump</> cannot dump from
- <productname>PostgreSQL</> servers newer than its own major version;
+ However, <application>pg_dump</application> cannot dump from
+ <productname>PostgreSQL</productname> servers newer than its own major version;
it will refuse to even try, rather than risk making an invalid dump.
- Also, it is not guaranteed that <application>pg_dump</>'s output can
+ Also, it is not guaranteed that <application>pg_dump</application>'s output can
be loaded into a server of an older major version — not even if the
dump was taken from a server of that version. Loading a dump file
into an older server may require manual editing of the dump file
Modified: traduc/trunk/postgresql/ref/pg_dumpall.xml
===================================================================
--- traduc/trunk/postgresql/ref/pg_dumpall.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/pg_dumpall.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -199,9 +199,9 @@
<para>
Do not wait forever to acquire shared table locks at the beginning of
the dump. Instead fail if unable to lock a table within the specified
- <replaceable class="parameter">timeout</>. The timeout may be
+ <replaceable class="parameter">timeout</replaceable>. The timeout may be
specified in any of the formats accepted by <command>SET
- statement_timeout</>. (Allowed values vary depending on the server
+ statement_timeout</command>. (Allowed values vary depending on the server
version you are dumping from, but an integer number of milliseconds
is accepted by all versions since 7.3. This option is ignored when
dumping from a pre-7.3 server.)
@@ -441,8 +441,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
@@ -488,11 +488,12 @@
<listitem>
<para>
Specifies a role name to be used to create the dump.
- This option causes <application>pg_dumpall</> to issue a
- <command>SET ROLE</> <replaceable class="parameter">rolename</>
+ This option causes <application>pg_dumpall</application> to issue a
+ <command>SET ROLE</command> <replaceable
+ class="parameter">rolename</replaceable>
command after connecting to the database. It is useful when the
- authenticated user (specified by <option>-U</>) lacks privileges
- needed by <application>pg_dumpall</>, but can switch to a role with
+ authenticated user (specified by <option>-U</option>) lacks privileges
+ needed by <application>pg_dumpall</application>, but can switch to a role with
the required rights. Some installations have a policy against
logging in directly as a superuser, and use of this option allows
dumps to be made without violating the policy.
Modified: traduc/trunk/postgresql/ref/pg_restore.xml
===================================================================
--- traduc/trunk/postgresql/ref/pg_restore.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/pg_restore.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -226,7 +226,7 @@
<listitem>
<para>
Run the most time-consuming parts
- of <application>pg_restore</> — those which load data,
+ of <application>pg_restore</application> — those which load data,
create indexes, or create constraints — using multiple
concurrent jobs. This option can dramatically reduce the time
to restore a large database to a server running on a
@@ -490,10 +490,10 @@
<listitem>
<para>
Execute the restore as a single transaction (that is, wrap the
- emitted commands in <command>BEGIN</>/<command>COMMIT</>). This
+ emitted commands in <command>BEGIN</command>/<command>COMMIT</command>). This
ensures that either all the commands complete successfully, or no
changes are applied. This option implies
- <option>--exit-on-error</>.
+ <option>--exit-on-error</option>.
</para>
</listitem>
</varlistentry>
@@ -547,8 +547,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
@@ -587,11 +587,12 @@
<listitem>
<para>
Specifies a role name to be used to perform the restore.
- This option causes <application>pg_restore</> to issue a
- <command>SET ROLE</> <replaceable class="parameter">rolename</>
+ This option causes <application>pg_restore</application> to issue a
+ <command>SET ROLE</command> <replaceable
+ class="parameter">rolename</replaceable>
command after connecting to the database. It is useful when the
- authenticated user (specified by <option>-U</>) lacks privileges
- needed by <application>pg_restore</>, but can switch to a role with
+ authenticated user (specified by <option>-U</option>) lacks privileges
+ needed by <application>pg_restore</application>, but can switch to a role with
the required rights. Some installations have a policy against
logging in directly as a superuser, and use of this option allows
restores to be performed without violating the policy.
Modified: traduc/trunk/postgresql/ref/prepare.xml
===================================================================
--- traduc/trunk/postgresql/ref/prepare.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/prepare.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -199,8 +199,7 @@
<title>Voir aussi</title>
<simplelist type="inline">
- <member><xref linkend="sql-deallocate"
- endterm="sql-deallocate-title"/></member>
+ <member><xref linkend="sql-deallocate" endterm="sql-deallocate-title"/></member>
<member><xref linkend="sql-execute" endterm="sql-execute-title"/></member>
</simplelist>
</refsect1>
Modified: traduc/trunk/postgresql/ref/psql-ref.xml
===================================================================
--- traduc/trunk/postgresql/ref/psql-ref.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/psql-ref.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -431,8 +431,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires password
@@ -1193,7 +1193,7 @@
stand for index, sequence, table, and view, respectively.
You can specify any or all of
these letters, in any order, to obtain a listing of all the
- matching objects. For example, <literal>\dit</> lists indexes
+ matching objects. For example, <literal>\dit</literal> lists indexes
and tables. If <literal>+</literal> is
appended to the command name, each object is listed with its
physical size on disk and its associated description, if any.
@@ -1283,7 +1283,7 @@
specified, only types whose names match the pattern are listed.
If <literal>+</literal> is appended to the command name, each type is
listed with its internal name and size, as well as its allowed values
- if it is an <type>enum</> type.
+ if it is an <type>enum</type> type.
By default, only user-created objects are shown; supply a
pattern or the <literal>S</literal> modifier to include system
objects.
@@ -1347,23 +1347,23 @@
<listitem>
<para>
This command fetches and edits the definition of the named function,
- in the form of a <command>CREATE OR REPLACE FUNCTION</> command.
- Editing is done in the same way as for <literal>\e</>.
+ in the form of a <command>CREATE OR REPLACE FUNCTION</command> command.
+ Editing is done in the same way as for <literal>\e</literal>.
After the editor exits, the updated command waits in the query buffer;
- type semicolon or <literal>\g</> to send it, or <literal>\r</>
- to cancel.
+ type semicolon or <literal>\g</literal> to send it, or
+ <literal>\r</literal> to cancel.
</para>
<para>
The target function can be specified by name alone, or by name
- and arguments, for example <literal>foo(integer, text)</>.
+ and arguments, for example <literal>foo(integer, text)</literal>.
The argument types must be given if there is more
than one function of the same name.
</para>
<para>
- If no function is specified, a blank <command>CREATE FUNCTION</>
- template is presented for editing.
+ If no function is specified, a blank <command>CREATE
+ FUNCTION</command> template is presented for editing.
</para>
</listitem>
</varlistentry>
@@ -1720,12 +1720,12 @@
</para>
<para>
- <quote>Wrapped</quote> is like <literal>aligned</> but wraps
- output to the specified width. If <literal>\pset columns</> is
- zero (the default), <literal>wrapped</> mode only affects screen
+ <quote>Wrapped</quote> is like <literal>aligned</literal> but wraps
+ output to the specified width. If <literal>\pset columns</literal> is
+ zero (the default), <literal>wrapped</literal> mode only affects screen
output and wrapped width is controlled by the environment
- variable <envar>COLUMNS</> or the detected screen width. If
- <literal>\pset columns</> is set to a non-zero value, all output
+ variable <envar>COLUMNS</envar> or the detected screen width. If
+ <literal>\pset columns</literal> is set to a non-zero value, all output
is wrapped, including file and pipe output.
</para>
@@ -1758,9 +1758,9 @@
<term><literal>columns</literal></term>
<listitem>
<para>
- Controls the target width for the <literal>wrapped</> format,
+ Controls the target width for the <literal>wrapped</literal> format,
and width for determining if wide output requires the pager.
- Zero (the default) causes the <literal>wrapped</> format to
+ Zero (the default) causes the <literal>wrapped</literal> format to
affect only screen output.
</para>
</listitem>
@@ -1910,8 +1910,8 @@
</para>
<para>
- Lorsque le paginateur est désactivé (<literal>off</>), il n'est pas utilisé. Quand le
- paginateur est activé (<literal>on</>), il est utilisé seulement si nécessaire,
+ Lorsque le paginateur est désactivé (<literal>off</literal>), il n'est pas utilisé. Quand le
+ paginateur est activé (<literal>on</literal>), il est utilisé seulement si nécessaire,
c'est-à-dire si l'affichage se fait sur un terminal et qu'il ne tient
pas sur l'écran. <literal>\pset pager</literal>
active et désactive le paginateur. Ce dernier peut aussi être
@@ -2958,8 +2958,8 @@
<listitem>
<para>
- If <literal>\pset columns</> is zero, controls the
- width for the <literal>wrapped</> format and width for determining
+ If <literal>\pset columns</literal> is zero, controls the
+ width for the <literal>wrapped</literal> format and width for determining
if wide output requires the pager.
</para>
</listitem>
@@ -2987,7 +2987,7 @@
<listitem>
<para>
- Paramètres de connexion par défaut (see <xref linkend="libpq-envars">).
+ Paramètres de connexion par défaut (see <xref linkend="libpq-envars"/>).
</para>
</listitem>
</varlistentry>
@@ -3096,10 +3096,10 @@
with servers of the same version. That does not mean other combinations
will fail outright, but subtle and not-so-subtle problems might come
up. Backslash commands are particularly likely to fail if the
- server is of a newer version than <application>psql</> itself. However,
- backslash commands of the <literal>\d</> family should work with
+ server is of a newer version than <application>psql</application> itself. However,
+ backslash commands of the <literal>\d</literal> family should work with
servers of versions back to 7.4, though not necessarily with servers
- newer than <application>psql</> itself.
+ newer than <application>psql</application> itself.
</para>
</listitem>
Modified: traduc/trunk/postgresql/ref/reindexdb.xml
===================================================================
--- traduc/trunk/postgresql/ref/reindexdb.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/reindexdb.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -201,8 +201,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
Modified: traduc/trunk/postgresql/ref/revoke.xml
===================================================================
--- traduc/trunk/postgresql/ref/revoke.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/revoke.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -115,9 +115,9 @@
n'a le droit de faire de <literal>SELECT</literal> sur l'objet : ceux qui en
avaient obtenu le droit directement ou via un autre rôle l'ont toujours.
Similarly, revoking
- <literal>SELECT</> from a user might not prevent that user from using
- <literal>SELECT</> if <literal>PUBLIC</literal> or another membership
- role still has <literal>SELECT</> rights.
+ <literal>SELECT</literal> from a user might not prevent that user from using
+ <literal>SELECT</literal> if <literal>PUBLIC</literal> or another membership
+ role still has <literal>SELECT</literal> rights.
</para>
<para>
@@ -160,8 +160,8 @@
<para>
Utilisez la commande <command>\dp</command> de <xref linkend="app-psql"/>
pour afficher les droits donnés sur des tables and columns. See <xref
- linkend="sql-grant" endterm="sql-grant-title"> for information about the
- format. For non-table objects there are other <command>\d</> commands
+ linkend="sql-grant" endterm="sql-grant-title"/> for information about the
+ format. For non-table objects there are other <command>\d</command> commands
that can display their privileges.
</para>
Modified: traduc/trunk/postgresql/ref/select.xml
===================================================================
--- traduc/trunk/postgresql/ref/select.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/select.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -85,7 +85,7 @@
in the <literal>FROM</literal> list. A <literal>WITH</literal> query
that is referenced more than once in <literal>FROM</literal> is
computed only once.
- (See <xref linkend="sql-with" endterm="sql-with-title"> below.)
+ (See <xref linkend="sql-with" endterm="sql-with-title"/> below.)
</para>
</listitem>
@@ -190,7 +190,7 @@
<para>
Le droit <literal>SELECT</literal> sur each column used
- in a <command>SELECT</> command est nécessaire pour lire
+ in a <command>SELECT</command> command est nécessaire pour lire
ses valeurs. L'utilisation de <literal>FOR UPDATE</literal> ou de
<literal>FOR SHARE</literal> requiert en plus le droit
<literal>UPDATE</literal> (for at least one column
@@ -226,7 +226,7 @@
<replaceable class="parameter">non_recursive_term</replaceable> UNION [ ALL ] <replaceable class="parameter">recursive_term</replaceable>
</synopsis>
where the recursive self-reference must appear on the right-hand
- side of the <literal>UNION</>. Only one recursive self-reference
+ side of the <literal>UNION</literal>. Only one recursive self-reference
is permitted per query.
</para>
@@ -247,7 +247,7 @@
</para>
<para>
- See <xref linkend="queries-with"> for additional information.
+ See <xref linkend="queries-with"/> for additional information.
</para>
</refsect2>
@@ -324,9 +324,9 @@
<term><replaceable class="parameter">with_query_name</replaceable></term>
<listitem>
<para>
- A <literal>WITH</> query is referenced by writing its name,
+ A <literal>WITH</literal> query is referenced by writing its name,
just as though the query's name were a table name. (In fact,
- the <literal>WITH</> query hides any real table of the same name
+ the <literal>WITH</literal> query hides any real table of the same name
for the purposes of the primary query. If necessary, you can
refer to a real table of the same name by schema-qualifying
the table's name.)
@@ -583,7 +583,7 @@
</synopsis>
where <replaceable class="parameter">window_name</replaceable> is
a name that can be referenced from subsequent window definitions or
- <literal>OVER</> clauses, and
+ <literal>OVER</literal> clauses, and
<replaceable class="parameter">window_definition</replaceable> is
<synopsis>
[ <replaceable class="parameter">existing_window_name</replaceable> ]
@@ -595,31 +595,33 @@
<para>
If an <replaceable class="parameter">existing_window_name</replaceable>
- is specified it must refer to an earlier entry in the <literal>WINDOW</>
+ is specified it must refer to an earlier entry in the
+ <literal>WINDOW</literal>
list; the new window copies its partitioning clause from that entry,
as well as its ordering clause if any. In this case the new window cannot
- specify its own <literal>PARTITION BY</> clause, and it can specify
- <literal>ORDER BY</> only if the copied window does not have one.
+ specify its own <literal>PARTITION BY</literal> clause, and it can specify
+ <literal>ORDER BY</literal> only if the copied window does not have one.
The new window always uses its own frame clause; the copied window
must not specify a frame clause.
</para>
<para>
- The elements of the <literal>PARTITION BY</> list are interpreted in
+ The elements of the <literal>PARTITION BY</literal> list are interpreted in
the same fashion as elements of a
- <xref linkend="sql-groupby" endterm="sql-groupby-title">, and
- the elements of the <literal>ORDER BY</> list are interpreted in the
+ <xref linkend="sql-groupby" endterm="sql-groupby-title"/>, and
+ the elements of the <literal>ORDER BY</literal> list are interpreted in the
same fashion as elements of an
- <xref linkend="sql-orderby" endterm="sql-orderby-title">.
+ <xref linkend="sql-orderby" endterm="sql-orderby-title"/>.
The only difference is that these expressions can contain aggregate
- function calls, which are not allowed in a regular <literal>GROUP BY</>
+ function calls, which are not allowed in a regular <literal>GROUP
+ BY</literal>
clause. They are allowed here because windowing occurs after grouping
and aggregation.
</para>
<para>
- The optional <replaceable class="parameter">frame_clause</> defines
- the <firstterm>window frame</> for window functions that depend on the
+ The optional <replaceable class="parameter">frame_clause</replaceable> defines
+ the <firstterm>window frame</firstterm> for window functions that depend on the
frame (not all do). It can be one of
<synopsis>
RANGE UNBOUNDED PRECEDING
@@ -631,39 +633,40 @@
</synopsis>
The first two are equivalent and are also the default: they set the
frame to be all rows from the partition start up through the current row's
- last peer in the <literal>ORDER BY</> ordering (which means all rows if
- there is no <literal>ORDER BY</>). The options
- <literal>RANGE BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</> and
- <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</>
+ last peer in the <literal>ORDER BY</literal> ordering (which means all rows if
+ there is no <literal>ORDER BY</literal>). The options
+ <literal>RANGE BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED
+ FOLLOWING</literal> and
+ <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</literal>
are also equivalent: they always select all rows in the partition.
- Lastly, <literal>ROWS UNBOUNDED PRECEDING</> or its verbose equivalent
- <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW</> select
+ Lastly, <literal>ROWS UNBOUNDED PRECEDING</literal> or its verbose equivalent
+ <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW</literal> select
all rows up through the current row (regardless of duplicates).
Beware that this option can produce implementation-dependent results
- if the <literal>ORDER BY</> ordering does not order the rows uniquely.
+ if the <literal>ORDER BY</literal> ordering does not order the rows uniquely.
</para>
<para>
The purpose of a <literal>WINDOW</literal> clause is to specify the
- behavior of <firstterm>window functions</> appearing in the query's
- <xref linkend="sql-select-list" endterm="sql-select-list-title"> or
- <xref linkend="sql-orderby" endterm="sql-orderby-title">. These functions
+ behavior of <firstterm>window functions</firstterm> appearing in the query's
+ <xref linkend="sql-select-list" endterm="sql-select-list-title"/> or
+ <xref linkend="sql-orderby" endterm="sql-orderby-title"/>. These functions
can reference the <literal>WINDOW</literal> clause entries by name
- in their <literal>OVER</> clauses. A <literal>WINDOW</literal> clause
+ in their <literal>OVER</literal> clauses. A <literal>WINDOW</literal> clause
entry does not have to be referenced anywhere, however; if it is not
used in the query it is simply ignored. It is possible to use window
functions without any <literal>WINDOW</literal> clause at all, since
a window function call can specify its window definition directly in
- its <literal>OVER</> clause. However, the <literal>WINDOW</literal>
+ its <literal>OVER</literal> clause. However, the <literal>WINDOW</literal>
clause saves typing when the same window definition is needed for more
than one window function.
</para>
<para>
Window functions are described in detail in
- <xref linkend="tutorial-window">,
- <xref linkend="syntax-window-functions">, and
- <xref linkend="queries-window">.
+ <xref linkend="tutorial-window"/>,
+ <xref linkend="syntax-window-functions"/>, and
+ <xref linkend="queries-window"/>.
</para>
</refsect2>
@@ -681,28 +684,29 @@
<para>
Just as in a table, every output column of a <command>SELECT</command>
has a name. In a simple <command>SELECT</command> this name is just
- used to label the column for display, but when the <command>SELECT</>
+ used to label the column for display, but when the
+ <command>SELECT</command>
is a sub-query of a larger query, the name is seen by the larger query
as the column name of the virtual table produced by the sub-query.
To specify the name to use for an output column, write
- <literal>AS</> <replaceable class="parameter">output_name</replaceable>
+ <literal>AS</literal> <replaceable class="parameter">output_name</replaceable>
after the column's expression. (You can omit <literal>AS</literal>,
but only if the desired output name does not match any
<productname>PostgreSQL</productname> keyword (see <xref
- linkend="sql-keywords-appendix">). For protection against possible
+ linkend="sql-keywords-appendix"/>). For protection against possible
future keyword additions, it is recommended that you always either
write <literal>AS</literal> or double-quote the output name.)
If you do not specify a column name, a name is chosen automatically
by <productname>PostgreSQL</productname>. If the column's expression
is a simple column reference then the chosen name is the same as that
column's name; in more complex cases a generated name looking like
- <literal>?column<replaceable>N</>?</literal> is usually chosen.
+ <literal>?column<replaceable>N</replaceable>?</literal> is usually chosen.
</para>
<para>
An output column's name can be used to refer to the column's value in
- <literal>ORDER BY</> and <literal>GROUP BY</> clauses, but not in the
- <literal>WHERE</> or <literal>HAVING</> clauses; there you must write
+ <literal>ORDER BY</literal> and <literal>GROUP BY</literal> clauses, but not in the
+ <literal>WHERE</literal> or <literal>HAVING</literal> clauses; there you must write
out the expression instead.
</para>
@@ -712,7 +716,7 @@
sélectionnées. De plus,
<literal><replaceable class="parameter">nom_table</replaceable>.*</literal>
peut être écrit comme raccourci pour toutes les colonnes de cette table. In these
- cases it is not possible to specify new names with <literal>AS</>;
+ cases it is not possible to specify new names with <literal>AS</literal>;
the output column names will be the same as the table columns' names.
</para>
</refsect2>
@@ -1004,9 +1008,9 @@
<para>
If the <replaceable class="parameter">count</replaceable> expression
- evaluates to NULL, it is treated as <literal>LIMIT ALL</>, i.e., no
+ evaluates to NULL, it is treated as <literal>LIMIT ALL</literal>, i.e., no
limit. If <replaceable class="parameter">start</replaceable> evaluates
- to NULL, it is treated the same as <literal>OFFSET 0</>.
+ to NULL, it is treated the same as <literal>OFFSET 0</literal>.
</para>
<para>
@@ -1022,10 +1026,12 @@
and <literal>ROWS</literal> as well as <literal>FIRST</literal>
and <literal>NEXT</literal> are noise words that don't influence
the effects of these clauses. In this syntax, when using expressions
- other than simple constants for <replaceable class="parameter">start</>
+ other than simple constants for <replaceable
+ class="parameter">start</replaceable>
or <replaceable class="parameter">count</replaceable>, parentheses will be
- necessary in most cases. If <replaceable class="parameter">count</> is
- omitted in <literal>FETCH</>, it defaults to 1.
+ necessary in most cases. If <replaceable
+ class="parameter">count</replaceable> is
+ omitted in <literal>FETCH</literal>, it defaults to 1.
</para>
<para>
@@ -1356,7 +1362,7 @@
</para>
<para>
- This example shows how to use a simple <literal>WITH</> clause:
+ This example shows how to use a simple <literal>WITH</literal> clause:
<programlisting>
WITH t AS (
@@ -1376,7 +1382,7 @@
0.0735620250925422
</programlisting>
- Notice that the <literal>WITH</> query was evaluated only once,
+ Notice that the <literal>WITH</literal> query was evaluated only once,
so that we got two sets of the same three random values.
</para>
@@ -1403,7 +1409,7 @@
an initial condition, followed by <literal>UNION</literal>,
followed by the recursive part of the query. Be sure that the
recursive part of the query will eventually return no tuples, or
- else the query will loop indefinitely. (See <xref linkend="queries-with">
+ else the query will loop indefinitely. (See <xref linkend="queries-with"/>
for more examples.)
</para>
</refsect1>
@@ -1457,19 +1463,19 @@
<title>Omitting the <literal>AS</literal> Key Word</title>
<para>
- In the SQL standard, the optional key word <literal>AS</> can be
+ In the SQL standard, the optional key word <literal>AS</literal> can be
omitted before an output column name whenever the new column name
is a valid column name (that is, not the same as any reserved
keyword). <productname>PostgreSQL</productname> is slightly more
- restrictive: <literal>AS</> is required if the new column name
+ restrictive: <literal>AS</literal> is required if the new column name
matches any keyword at all, reserved or not. Recommended practice is
- to use <literal>AS</> or double-quote output column names, to prevent
+ to use <literal>AS</literal> or double-quote output column names, to prevent
any possible conflict against future keyword additions.
</para>
<para>
In <literal>FROM</literal> items, both the standard and
- <productname>PostgreSQL</productname> allow <literal>AS</> to
+ <productname>PostgreSQL</productname> allow <literal>AS</literal> to
be omitted before an alias that is an unreserved keyword. But
this is impractical for output column names, because of syntactic
ambiguities.
@@ -1520,7 +1526,7 @@
<para>
The SQL standard provides additional options for the window
- <replaceable class="parameter">frame_clause</>.
+ <replaceable class="parameter">frame_clause</replaceable>.
<productname>PostgreSQL</productname> currently supports only the
options listed above.
</para>
@@ -1535,7 +1541,7 @@
used by <productname>MySQL</productname>. The SQL:2008 standard
has introduced the clauses <literal>OFFSET ... FETCH {FIRST|NEXT}
...</literal> for the same functionality, as shown above
- in <xref linkend="sql-limit" endterm="sql-limit-title">, and this
+ in <xref linkend="sql-limit" endterm="sql-limit-title"/>, and this
syntax is also used by <productname>IBM DB2</productname>.
(Applications written for <productname>Oracle</productname>
frequently use a workaround involving the automatically
Modified: traduc/trunk/postgresql/ref/set.xml
===================================================================
--- traduc/trunk/postgresql/ref/set.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/set.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -163,8 +163,8 @@
<term><literal>SCHEMA</literal></term>
<listitem>
<para>
- <literal>SET SCHEMA '<replaceable>value</>'</> is an alias for
- <literal>SET search_path TO <replaceable>value</></>. Only one
+ <literal>SET SCHEMA '<replaceable>value</replaceable>'</literal> is an alias for
+ <literal>SET search_path TO <replaceable>value</replaceable></literal>. Only one
schema can be specified using this syntax.
</para>
</listitem>
Modified: traduc/trunk/postgresql/ref/set_role.xml
===================================================================
--- traduc/trunk/postgresql/ref/set_role.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/set_role.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -94,9 +94,9 @@
</para>
<para>
- <command>SET ROLE</> does not process session variables as specified by
+ <command>SET ROLE</command> does not process session variables as specified by
the role's <xref linkend="sql-alterrole"
- endterm="sql-alterrole-title"> settings; this only happens during
+ endterm="sql-alterrole-title"/> settings; this only happens during
login.
</para>
Modified: traduc/trunk/postgresql/ref/truncate.xml
===================================================================
--- traduc/trunk/postgresql/ref/truncate.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/truncate.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -18,7 +18,7 @@
</refnamediv>
<refsynopsisdiv>
-TRUNCATE [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">nom</replaceable> [, ... ]
+<synopsis>TRUNCATE [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">nom</replaceable> [, ... ]
[ RESTART IDENTITY | CONTINUE IDENTITY ] [ CASCADE | RESTRICT ]
</synopsis>
</refsynopsisdiv>
@@ -48,8 +48,9 @@
<term><replaceable class="parameter">name</replaceable></term>
<listitem>
<para>
- Le nom d'une table à vider (peut être qualifié par le schéma). If <literal>ONLY</> is specified, only that table is
- truncated. If <literal>ONLY</> is not specified, the table and
+ Le nom d'une table à vider (peut être qualifié par le schéma). If
+ <literal>ONLY</literal> is specified, only that table is
+ truncated. If <literal>ONLY</literal> is not specified, the table and
all its descendant tables (if any) are truncated.
</para>
</listitem>
@@ -107,10 +108,10 @@
</para>
<para>
- <command>TRUNCATE</> acquires an access exclusive lock on the
+ <command>TRUNCATE</command> acquires an access exclusive lock on the
tables in operates on, which blocks all other concurrent operations
on the table. If concurrent access to a table is required, then
- the <command>DELETE</> command should be used instead.
+ the <command>DELETE</command> command should be used instead.
</para>
<para>
@@ -129,7 +130,7 @@
<command>TRUNCATE</command> ne déclenchera aucun trigger <literal>ON
DELETE</literal> qui pourrait exister sur les tables. But it will fire
<literal>ON TRUNCATE</literal> triggers.
- If <literal>ON TRUNCATE</> triggers are defined for any of
+ If <literal>ON TRUNCATE</literal> triggers are defined for any of
the tables, then all <literal>BEFORE TRUNCATE</literal> triggers are
fired before any truncation happens, and all <literal>AFTER
TRUNCATE</literal> triggers are fired after the last truncation is
@@ -162,19 +163,19 @@
</warning>
<para>
- <command>TRUNCATE</> is transaction-safe with respect to the data
+ <command>TRUNCATE</command> is transaction-safe with respect to the data
in the tables: the truncation will be safely rolled back if the surrounding
transaction does not commit.
</para>
<warning>
<para>
- Any <command>ALTER SEQUENCE RESTART</> operations performed as a
- consequence of using the <literal>RESTART IDENTITY</> option are
+ Any <command>ALTER SEQUENCE RESTART</command> operations performed as a
+ consequence of using the <literal>RESTART IDENTITY</literal> option are
nontransactional and will not be rolled back on failure. To minimize
the risk, these operations are performed only after all the rest of
- <command>TRUNCATE</>'s work is done. However, there is still a risk
- if <command>TRUNCATE</> is performed inside a transaction block that is
+ <command>TRUNCATE</command>'s work is done. However, there is still a risk
+ if <command>TRUNCATE</command> is performed inside a transaction block that is
aborted afterwards. For example, consider
<programlisting>
@@ -184,12 +185,12 @@
COMMIT;
</programlisting>
- If the <command>COPY</> fails partway through, the table data
+ If the <command>COPY</command> fails partway through, the table data
rolls back correctly, but the sequences will be left with values
that are probably smaller than they had before, possibly leading
to duplicate-key failures or other problems in later transactions.
If this is likely to be a problem, it's best to avoid using
- <literal>RESTART IDENTITY</>, and accept that the new contents of
+ <literal>RESTART IDENTITY</literal>, and accept that the new contents of
the table will have higher serial numbers than the old.
</para>
</warning>
Modified: traduc/trunk/postgresql/ref/update.xml
===================================================================
--- traduc/trunk/postgresql/ref/update.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/update.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -175,9 +175,9 @@
sur la table cible de l'<command>UPDATE</command>.
Notez que <literal>WHERE CURRENT OF</literal> ne peut pas être
spécifié avec une condition booléenne. See
- <xref linkend="sql-declare" endterm="sql-declare-title">
+ <xref linkend="sql-declare" endterm="sql-declare-title"/>
for more information about using cursors with
- <literal>WHERE CURRENT OF</>.
+ <literal>WHERE CURRENT OF</literal>.
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/ref/vacuum.xml
===================================================================
--- traduc/trunk/postgresql/ref/vacuum.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/vacuum.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -163,8 +163,8 @@
superuser. However, database owners are allowed to
vacuum all tables in their databases, except shared catalogs.
(The restriction for shared catalogs means that a true database-wide
- <command>VACUUM</> can only be performed by a superuser.)
- <command>VACUUM</> will skip over any tables that the calling user
+ <command>VACUUM</command> can only be performed by a superuser.)
+ <command>VACUUM</command> will skip over any tables that the calling user
does not have permission to vacuum.
</para>
@@ -174,10 +174,10 @@
</para>
<para>
- For tables with <acronym>GIN</> indexes, <command>VACUUM</command> (in
+ For tables with <acronym>GIN</acronym> indexes, <command>VACUUM</command> (in
any form) also completes any pending index insertions, by moving pending
- index entries to the appropriate places in the main <acronym>GIN</> index
- structure. See <xref linkend="gin-fast-update"> for details.
+ index entries to the appropriate places in the main <acronym>GIN</acronym> index
+ structure. See <xref linkend="gin-fast-update"/> for details.
</para>
<para>
Modified: traduc/trunk/postgresql/ref/vacuumdb.xml
===================================================================
--- traduc/trunk/postgresql/ref/vacuumdb.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/vacuumdb.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -219,8 +219,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires
Modified: traduc/trunk/postgresql/ref/values.xml
===================================================================
--- traduc/trunk/postgresql/ref/values.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/ref/values.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -247,7 +247,7 @@
<command>VALUES</command> est conforme au standard SQL. Les clauses
<literal>LIMIT</literal> et <literal>OFFSET</literal> sont des extensions
<productname>PostgreSQL</productname> ; voir aussi <xref
- linkend="sql-select" endterm="sql-select-title">.
+ linkend="sql-select" endterm="sql-select-title"/>.
</para>
</refsect1>
Modified: traduc/trunk/postgresql/release.xml
===================================================================
--- traduc/trunk/postgresql/release.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/release.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -83,7 +83,7 @@
<title>Overview</title>
<para>
- After many years of development, <productname>PostgreSQL</> has
+ After many years of development, <productname>PostgreSQL</productname> has
become feature-complete in many areas. This release shows a
targeted approach to adding features (e.g. authentication,
monitoring, space reuse), and adds capabilities defined in the
@@ -228,7 +228,7 @@
<listitem>
<para>
- Remove <application>ipcclean</> utility command (Bruce)
+ Remove <application>ipcclean</application> utility command (Bruce)
</para>
<para>
@@ -247,38 +247,40 @@
<listitem>
<para>
- Change <filename>postgresql.conf</> default for
- <literal>log_min_messages</> to <literal>warning</> (previously
- <literal>notice</>) to reduce log file volume (Tom)
+ Change <filename>postgresql.conf</filename> default for
+ <literal>log_min_messages</literal> to <literal>warning</literal> (previously
+ <literal>notice</literal>) to reduce log file volume (Tom)
</para>
</listitem>
<listitem>
<para>
- Have <literal>debug_print_parse</>, <literal>debug_print_rewritten</>,
- and <literal>debug_print_plan</>
- output appear at <literal>LOG</> message level, not
- <literal>DEBUG1</> as formerly (Tom)
+ Have <literal>debug_print_parse</literal>,
+ <literal>debug_print_rewritten</literal>,
+ and <literal>debug_print_plan</literal>
+ output appear at <literal>LOG</literal> message level, not
+ <literal>DEBUG1</literal> as formerly (Tom)
</para>
</listitem>
<listitem>
<para>
- Make <literal>debug_pretty_print</> default to <literal>on</> (Tom)
+ Make <literal>debug_pretty_print</literal> default to
+ <literal>on</literal> (Tom)
</para>
</listitem>
<listitem>
<para>
- Make <varname>log_temp_files</> super-user set only, like other
+ Make <varname>log_temp_files</varname> super-user set only, like other
logging options (Simon)
</para>
</listitem>
<listitem>
<para>
- Disable appending of the epoch date/time when no <literal>%</>
- escapes are present in <literal>log_filename</> (Robert Haas)
+ Disable appending of the epoch date/time when no <literal>%</literal>
+ escapes are present in <literal>log_filename</literal> (Robert Haas)
</para>
<para>
@@ -289,39 +291,41 @@
<listitem>
<para>
- Remove <varname>explain_pretty_print</> parameter (no longer needed) (Tom)
+ Remove <varname>explain_pretty_print</varname> parameter (no longer needed) (Tom)
</para>
</listitem>
<listitem>
<para>
- Remove <varname>log_restartpoints</> from <filename>recovery.conf</>;
- instead use <varname>log_checkpoints</> (Simon Riggs)
+ Remove <varname>log_restartpoints</varname> from
+<filename>recovery.conf</filename>;
+ instead use <varname>log_checkpoints</varname> (Simon Riggs)
</para>
</listitem>
<listitem>
<para>
- Remove support for the (insecure) <literal>crypt</> authentication method
+ Remove support for the (insecure) <literal>crypt</literal> authentication method
(Magnus)
</para>
<para>
- This breaks compatibility with pre-<productname>PostgreSQL</> 7.2 versions.
+ This breaks compatibility with pre-<productname>PostgreSQL</productname> 7.2 versions.
</para>
</listitem>
<listitem>
<para>
- Remove <varname>krb_realm</> and <varname>krb_server_hostname</>, now
- <filename>pg_hba.conf</>-only settings (Magnus)
+ Remove <varname>krb_realm</varname> and
+ <varname>krb_server_hostname</varname>, now
+ <filename>pg_hba.conf</filename>-only settings (Magnus)
</para>
</listitem>
<listitem>
<para>
The <link
- linkend="release-8-4-pg-hba-conf"><filename>pg_hba.conf</></link>
+ linkend="release-8-4-pg-hba-conf"><filename>pg_hba.conf</filename></link>
section below also has extensive changes related to migration.
</para>
</listitem>
@@ -337,7 +341,7 @@
<listitem>
<para>
- Force child tables to inherit <literal>CHECK</> constraints from parents
+ Force child tables to inherit <literal>CHECK</literal> constraints from parents
(Alex Hunsaker, Nikhil Sontakke, Tom Lane)
</para>
@@ -351,26 +355,26 @@
<listitem>
<para>
- Change <command>TRUNCATE</> and <command>LOCK</> behavior to
+ Change <command>TRUNCATE</command> and <command>LOCK</command> behavior to
apply to all child tables (Peter)
</para>
<para>
- There is a new <literal>ONLY</> clause which disables this
+ There is a new <literal>ONLY</literal> clause which disables this
behavior.
</para>
</listitem>
<listitem>
<para>
- Disallow negative <literal>LIMIT</> or <literal>OFFSET</>
+ Disallow negative <literal>LIMIT</literal> or <literal>OFFSET</literal>
values, rather than treating them as zero (Simon)
</para>
</listitem>
<listitem>
<para>
- Disallow <command>LOCK TABLE</> outside a transaction block
+ Disallow <command>LOCK TABLE</command> outside a transaction block
(Tom)
</para>
@@ -392,24 +396,25 @@
<listitem>
<para>
- Have <literal>NUMERIC 0 ^ 4.3</> return <literal>1</>, rather
- than an error, and have <literal>0 ^ 0.0</> return <literal>1</>,
+ Have <literal>NUMERIC 0 ^ 4.3</literal> return <literal>1</literal>, rather
+ than an error, and have <literal>0 ^ 0.0</literal> return
+ <literal>1</literal>,
rather than error (Bruce)
</para>
<para>
- This was already the <type>float8</> behavior.
+ This was already the <type>float8</type> behavior.
</para>
</listitem>
<listitem>
<para>
Remove code that prevented unary minus of floating-point values
- from producing <literal>-0</> (Tom)
+ from producing <literal>-0</literal> (Tom)
</para>
<para>
- The changed behavior is more <acronym>IEEE</>-standard
+ The changed behavior is more <acronym>IEEE</acronym>-standard
compliant.
</para>
</listitem>
@@ -417,14 +422,14 @@
<listitem>
<para>
Throw an error if an escape character is the last character in
- a <literal>LIKE</> pattern (there is nothing to escape) (Tom)
+ a <literal>LIKE</literal> pattern (there is nothing to escape) (Tom)
</para>
</listitem>
<listitem>
<para>
- Remove <literal>~=~</> and <literal>~<>~</> operators
- formerly used for <literal>LIKE</> index comparisons (Tom)
+ Remove <literal>~=~</literal> and <literal>~<>~</literal> operators
+ formerly used for <literal>LIKE</literal> index comparisons (Tom)
</para>
<para>
@@ -434,7 +439,8 @@
<listitem>
<para>
- <function>xpath()</> now passes its arguments to <application>libxml</>
+ <function>xpath()</function> now passes its arguments to
+ <application>libxml</application>
without any changes (Andrew)
</para>
@@ -447,7 +453,7 @@
<listitem>
<para>
- Make <function>xmlelement()</> format attribute values just like
+ Make <function>xmlelement()</function> format attribute values just like
content values (Peter)
</para>
@@ -467,15 +473,16 @@
<listitem>
<para>
- Have <function>to_char()</>'s localized month/day names depend
- on <varname>LC_TIME</>, not <varname>LC_MESSAGES</> (Euler
+ Have <function>to_char()</function>'s localized month/day names depend
+ on <varname>LC_TIME</varname>, not <varname>LC_MESSAGES</varname> (Euler
Taveira de Oliveira)
</para>
</listitem>
<listitem>
<para>
- Cause <function>to_date()</> and <function>to_timestamp()</>
+ Cause <function>to_date()</function> and
+ <function>to_timestamp()</function>
to more consistently report errors on invalid input (Brendan
Jurd)
</para>
@@ -490,36 +497,36 @@
<listitem>
<para>
- Fix <function>to_timestamp()</> to not require upper/lower case
- matching for meridian (<literal>AM</>/<literal>PM</>) and era
- (<literal>BC</>/<literal>AD</>) format designations (Brendan
+ Fix <function>to_timestamp()</function> to not require upper/lower case
+ matching for meridian (<literal>AM</literal>/<literal>PM</literal>) and era
+ (<literal>BC</literal>/<literal>AD</literal>) format designations (Brendan
Jurd)
</para>
<para>
- For example, input value <literal>ad</> now matches the format
- string <literal>AD</>.
+ For example, input value <literal>ad</literal> now matches the format
+ string <literal>AD</literal>.
</para>
</listitem>
<listitem>
<para>
- Require the existence of periods in <function>to_timestamp()</>
- meridian (<literal>AM</>/<literal>PM</>) and era
- (<literal>BC</>/<literal>AD</>) format designations to match
+ Require the existence of periods in <function>to_timestamp()</function>
+ meridian (<literal>AM</literal>/<literal>PM</literal>) and era
+ (<literal>BC</literal>/<literal>AD</literal>) format designations to match
(Brendan Jurd)
</para>
<para>
- For example, input value <literal>AD</> now does not match
- format string <literal>A.D.</>.
+ For example, input value <literal>AD</literal> now does not match
+ format string <literal>A.D.</literal>.
</para>
</listitem>
<listitem>
<para>
- <varname>DateStyle</> no longer controls <type>INTERVAL</>
- output (use new variable <varname>IntervalStyle</>)
+ <varname>DateStyle</varname> no longer controls <type>INTERVAL</type>
+ output (use new variable <varname>IntervalStyle</varname>)
</para>
</listitem>
@@ -556,18 +563,18 @@
<listitem>
<para>
- Allow <command>SELECT DISTINCT</> and
- <literal>UNION</>/<literal>INTERSECT</>/<literal>EXCEPT</> to
+ Allow <command>SELECT DISTINCT</command> and
+ <literal>UNION</literal>/<literal>INTERSECT</literal>/<literal>EXCEPT</literal> to
use hashing (Tom)
</para>
<para>
This means that these types of queries no longer automatically
produce sorted output. The recommended response is to add an
- <literal>ORDER BY</> clause if needed. As a short-term workaround,
+ <literal>ORDER BY</literal> clause if needed. As a short-term workaround,
the previous behavior can be restored by
- disabling <literal>enable_hashagg</>, but that is a very
- performance-expensive fix. <literal>SELECT DISTINCT ON</> never
+ disabling <literal>enable_hashagg</literal>, but that is a very
+ performance-expensive fix. <literal>SELECT DISTINCT ON</literal> never
uses hashing.
</para>
</listitem>
@@ -578,27 +585,27 @@
</para>
<para>
- While semi-joins merely replace existing <literal>IN</> joins,
- anti-joins are a new capability for <literal>NOT EXISTS</>
+ While semi-joins merely replace existing <literal>IN</literal> joins,
+ anti-joins are a new capability for <literal>NOT EXISTS</literal>
clauses. This improves optimization possibilities.
</para>
</listitem>
<listitem>
<para>
- Improve <literal>IN</>/<literal>ANY</>/<literal>EXISTS</>
+ Improve <literal>IN</literal>/<literal>ANY</literal>/<literal>EXISTS</literal>
processing (Tom)
</para>
<para>
- <literal>IN</> and <literal>EXISTS</> now provide similar
+ <literal>IN</literal> and <literal>EXISTS</literal> now provide similar
performance for equivalent clauses.
</para>
</listitem>
<listitem>
<para>
- Improve the performance of <function>text_position()</> and
+ Improve the performance of <function>text_position()</function> and
related functions by using Boyer-Moore-Horspool searching (David
Rowley)
</para>
@@ -629,27 +636,28 @@
<listitem>
<para>
- Increase the default value of <varname>default_statistics_target</>
- from <literal>10</> to <literal>100</> (Greg Sabino Mullane,
+ Increase the default value of
+ <varname>default_statistics_target</varname>
+ from <literal>10</literal> to <literal>100</literal> (Greg Sabino Mullane,
Tom)
</para>
<para>
- The maximum value was also increased from <literal>1000</> to
- <literal>10000</>.
+ The maximum value was also increased from <literal>1000</literal> to
+ <literal>10000</literal>.
</para>
</listitem>
<listitem>
<para>
- Modify <varname>constraint_exclusion</> to check for partitioned
- tables by default when inheritance or <literal>UNION ALL</> is
+ Modify <varname>constraint_exclusion</varname> to check for partitioned
+ tables by default when inheritance or <literal>UNION ALL</literal> is
used (Tom)
</para>
<para>
- A new <varname>constraint_exclusion</> setting,
- <literal>partition</>, was added to match this behavior.
+ A new <varname>constraint_exclusion</varname> setting,
+ <literal>partition</literal>, was added to match this behavior.
</para>
</listitem>
@@ -660,15 +668,15 @@
<para>
The amount of read-ahead is controlled by
- <varname>effective_io_concurrency</>. This requires
- <function>posix_fadvise()</> support in the kernel.
+ <varname>effective_io_concurrency</varname>. This requires
+ <function>posix_fadvise()</function> support in the kernel.
</para>
</listitem>
<listitem>
<para>
- Inline simple set-returning <acronym>SQL</> functions in
- <literal>FROM</> clauses (Richard Rowell)
+ Inline simple set-returning <acronym>SQL</acronym> functions in
+ <literal>FROM</literal> clauses (Richard Rowell)
</para>
</listitem>
@@ -683,7 +691,7 @@
<listitem>
<para>
Reduce volume of temporary data in multi-batch hash joins
- by suppressing <quote>physical tlist</> optimization (Michael
+ by suppressing <quote>physical tlist</quote> optimization (Michael
Henderson, Ramon Lawrence)
</para>
</listitem>
@@ -691,7 +699,7 @@
<listitem>
<para>
Avoid waiting for idle-in-transaction sessions during
- <command>CREATE INDEX CONCURRENTLY</> (Simon)
+ <command>CREATE INDEX CONCURRENTLY</command> (Simon)
</para>
</listitem>
@@ -709,15 +717,15 @@
<listitem>
<para>
- Convert many <filename>postgresql.conf</> settings to enumerated
- values so <literal>pg_settings</> can easily display valid
+ Convert many <filename>postgresql.conf</filename> settings to enumerated
+ values so <literal>pg_settings</literal> can easily display valid
values (Magnus)
</para>
</listitem>
<listitem>
<para>
- Add <varname>cursor_tuple_fraction</> parameter to control the
+ Add <varname>cursor_tuple_fraction</varname> parameter to control the
fraction of a cursor's rows expected to be requested by the
user (Robert Hell)
</para>
@@ -725,7 +733,7 @@
<listitem>
<para>
- Allow underscores in <filename>postgresql.conf</> custom variable
+ Allow underscores in <filename>postgresql.conf</filename> custom variable
classes (Tom)
</para>
</listitem>
@@ -740,21 +748,22 @@
<listitem>
<para>
- Report appropriate error message for combination of <literal>MD5</>
- authentication and <varname>db_user_namespace</> enabled (Bruce)
+ Report appropriate error message for combination of
+ <literal>MD5</literal>
+ authentication and <varname>db_user_namespace</varname> enabled (Bruce)
</para>
</listitem>
<listitem>
<para>
- Support regular expressions in <filename>pg_ident.conf</>
+ Support regular expressions in <filename>pg_ident.conf</filename>
(Magnus)
</para>
</listitem>
<listitem>
<para>
- Allow <productname>Kerberos</>/<acronym>GSSAPI</> parameters
+ Allow <productname>Kerberos</productname>/<acronym>GSSAPI</acronym> parameters
to be changed without restarting the postmaster (Magnus)
</para>
</listitem>
@@ -764,12 +773,12 @@
</sect4>
<sect4 id="release-8-4-pg-hba-conf">
- <title><filename>pg_hba.conf</></title>
+ <title><filename>pg_hba.conf</filename></title>
<itemizedlist>
<listitem>
<para>
- Parse <filename>pg_hba.conf</> in the postmaster so errors are
+ Parse <filename>pg_hba.conf</filename> in the postmaster so errors are
reported on reload (Magnus)
</para>
@@ -782,14 +791,14 @@
<listitem>
<para>
- Remove the <literal>sameuser</> option, making it the default
+ Remove the <literal>sameuser</literal> option, making it the default
if no usermap is specified (Magnus)
</para>
</listitem>
<listitem>
<para>
- Change all authentication options to be <literal>name=value</>
+ Change all authentication options to be <literal>name=value</literal>
settings (Magnus)
</para>
</listitem>
@@ -801,21 +810,21 @@
</para>
<para>
- Previously this was only supported for <literal>ident</>
+ Previously this was only supported for <literal>ident</literal>
authentication.
</para>
</listitem>
<listitem>
<para>
- Allow <literal>ident</> authentication over Unix-domain sockets
- on <productname>Solaris</> (Garick Hamlin)
+ Allow <literal>ident</literal> authentication over Unix-domain sockets
+ on <productname>Solaris</productname> (Garick Hamlin)
</para>
</listitem>
<listitem>
<para>
- Add <literal>clientcert</> option to control requesting of a
+ Add <literal>clientcert</literal> option to control requesting of a
client certificate (Magnus)
</para>
@@ -827,12 +836,12 @@
<listitem>
<para>
- Add <literal>cert</> authentication method to allow user
- authentication via <acronym>SSL</> certificates (Magnus)
+ Add <literal>cert</literal> authentication method to allow user
+ authentication via <acronym>SSL</acronym> certificates (Magnus)
</para>
<para>
- Previously <acronym>SSL</> certificates could only verify that
+ Previously <acronym>SSL</acronym> certificates could only verify that
the client had access to a certificate, not authenticate a
user.
</para>
@@ -840,20 +849,22 @@
<listitem>
<para>
- Allow <literal>krb5</>, <literal>gssapi</> and <literal>sspi</>
- realm and <literal>krb5</> host settings to be specified in
- <filename>pg_hba.conf</> (Magnus)
+ Allow <literal>krb5</literal>, <literal>gssapi</literal> and
+ <literal>sspi</literal>
+ realm and <literal>krb5</literal> host settings to be specified in
+ <filename>pg_hba.conf</filename> (Magnus)
</para>
<para>
- These override the settings in <filename>postgresql.conf</>.
+ These override the settings in <filename>postgresql.conf</filename>.
</para>
</listitem>
<listitem>
<para>
- Add <literal>krb5</>, <literal>gssapi</>, and <literal>sspi</>
- <varname>include_realm</> parameter (Magnus)
+ Add <literal>krb5</literal>, <literal>gssapi</literal>, and
+ <literal>sspi</literal>
+ <varname>include_realm</varname> parameter (Magnus)
</para>
<para>
@@ -879,7 +890,7 @@
<listitem>
<para>
- Provide an option to <function>pg_start_backup()</> to force its
+ Provide an option to <function>pg_start_backup()</function> to force its
implied checkpoint to finish as quickly as possible (Tom)
</para>
@@ -891,13 +902,13 @@
<listitem>
<para>
- Have <function>pg_stop_backup()</> wait for modified <acronym>WAL</>
- files to be archived (Simon)
+ Have <function>pg_stop_backup()</function> wait for modified
+ <acronym>WAL</acronym> files to be archived (Simon)
</para>
<para>
This guarantees that the backup is valid at the time
- <function>pg_stop_backup()</> completes.
+ <function>pg_stop_backup()</function> completes.
</para>
</listitem>
@@ -917,8 +928,8 @@
<listitem>
<para>
- Allow <filename>recovery.conf</> boolean variables to take the
- same range of string values as <filename>postgresql.conf</>
+ Allow <filename>recovery.conf</filename> boolean variables to take the
+ same range of string values as <filename>postgresql.conf</filename>
(Bruce)
</para>
</listitem>
@@ -933,7 +944,7 @@
<listitem>
<para>
- Add <function>pg_conf_load_time()</> to report when
+ Add <function>pg_conf_load_time()</function> to report when
the Postgres configuration files were last loaded (George
Gensure)
</para>
@@ -941,29 +952,29 @@
<listitem>
<para>
- Add <function>pg_terminate_backend()</> to safely terminate a
- backend (the <literal>SIGTERM</> signal works also) (Tom, Bruce)
+ Add <function>pg_terminate_backend()</function> to safely terminate a
+ backend (the <literal>SIGTERM</literal> signal works also) (Tom, Bruce)
</para>
</listitem>
<listitem>
<para>
Add ability to track user-defined functions call counts and
- runtimes via parameter <varname>track_functions</> (Martin
+ runtimes via parameter <varname>track_functions</varname> (Martin
Pihlak)
</para>
<para>
Function statistics appear in a new system table,
- <literal>pg_stat_user_functions</>. However, inlined
- <acronym>SQL</> functions are not tracked.
+ <literal>pg_stat_user_functions</literal>. However, inlined
+ <acronym>SQL</acronym> functions are not tracked.
</para>
</listitem>
<listitem>
<para>
- Allow specification of the maximum <literal>pg_stat_activity</>
- query string size via <varname>track_activity_query_size</>
+ Allow specification of the maximum <literal>pg_stat_activity</literal>
+ query string size via <varname>track_activity_query_size</varname>
parameter (Thomas Lee)
</para>
</listitem>
@@ -977,8 +988,9 @@
<listitem>
<para>
- Add read-only <filename>postgresql.conf</> variables <varname>segment_size</>,
- <varname>wal_block_size</>, and <varname>wal_segment_size</> (Bernd Helmle)
+ Add read-only <filename>postgresql.conf</filename> variables
+ <varname>segment_size</varname>, <varname>wal_block_size</varname>, and
+ <varname>wal_segment_size</varname> (Bernd Helmle)
</para>
</listitem>
@@ -991,7 +1003,7 @@
<listitem>
<para>
- New <function>pg_stat_get_activity(pid)</> function to return
+ New <function>pg_stat_get_activity(pid)</function> function to return
information about a specific process id (Magnus)
</para>
</listitem>
@@ -999,15 +1011,15 @@
<listitem>
<para>
Move the server statistics file into the subdirectory
- <filename>pg_stat_tmp</> and allow its location to be specified
- via <varname>stats_temp_directory</> (Magnus)
+ <filename>pg_stat_tmp</filename> and allow its location to be specified
+ via <varname>stats_temp_directory</varname> (Magnus)
</para>
<para>
This allows the statistics file to be placed in a
- <acronym>RAM</>-resident directory to reduce I/O requirements.
+ <acronym>RAM</acronym>-resident directory to reduce I/O requirements.
On startup/shutdown, the file is copied to the top-level
- <literal>$PGDATA</> directory so it is preserved between
+ <literal>$PGDATA</literal> directory so it is preserved between
restarts.
</para>
</listitem>
@@ -1024,33 +1036,33 @@
<listitem>
<para>
- Add support for <literal>WINDOW</> functions (Hitoshi Harada)
+ Add support for <literal>WINDOW</literal> functions (Hitoshi Harada)
</para>
</listitem>
<listitem>
<para>
- Add <literal>WITH</> clauses support, including <literal>WITH
- RECURSIVE</> (Yoshiyuki Asaba, Tatsuo Ishii, Tom)
+ Add <literal>WITH</literal> clauses support, including <literal>WITH
+ RECURSIVE</literal> (Yoshiyuki Asaba, Tatsuo Ishii, Tom)
</para>
</listitem>
<listitem>
<para>
- New <command>TABLE</> command (Peter)
+ New <command>TABLE</command> command (Peter)
</para>
<para>
- <command>TABLE tablename</> is a short-hand for <command>SELECT
- * FROM tablename</>.
+ <command>TABLE tablename</command> is a short-hand for <command>SELECT
+ * FROM tablename</command>.
</para>
</listitem>
<listitem>
<para>
- Allow <literal>AS</> to be optional when specifying a
- <command>SELECT</> (or <literal>RETURNING</>) column output
- label (assuming the label is not an <acronym>SQL</> keyword)
+ Allow <literal>AS</literal> to be optional when specifying a
+ <command>SELECT</command> (or <literal>RETURNING</literal>) column output
+ label (assuming the label is not an <acronym>SQL</acronym> keyword)
(Hiroshi Saito)
</para>
</listitem>
@@ -1064,19 +1076,19 @@
<listitem>
<para>
- Allow <command>SELECT FOR UPDATE</>/<literal>SHARE</> to work
+ Allow <command>SELECT FOR UPDATE</command>/<literal>SHARE</literal> to work
on inheritance trees (Tom)
</para>
</listitem>
<listitem>
<para>
- Add infrastructure for <acronym>SQL/MED</> (Martin Pihlak,
+ Add infrastructure for <acronym>SQL/MED</acronym> (Martin Pihlak,
Peter)
</para>
<para>
- There are no remote or external <acronym>SQL/MED</> capabilities
+ There are no remote or external <acronym>SQL/MED</acronym> capabilities
yet, but this change provides a standardized and future-proof
system for managing connection information for modules like
dblink and plproxy.
@@ -1101,8 +1113,8 @@
</para>
<para>
- Specifically this allows <literal>array[row(1,2), row(3,4)]</>
- and <literal>row(1,1.1) = any (array[row(7,7.7), row(1,1.0)])</>.
+ Specifically this allows <literal>array[row(1,2), row(3,4)]</literal>
+ and <literal>row(1,1.1) = any (array[row(7,7.7), row(1,1.0)])</literal>.
This is particularly useful for recursive queries.
</para>
</listitem>
@@ -1110,7 +1122,7 @@
<listitem>
<para>
Add support for Unicode string and identifier specifications
- using code points, e.g. <literal>U&'d\0061t\+000061'</>
+ using code points, e.g. <literal>U&'d\0061t\+000061'</literal>
(Peter)
</para>
</listitem>
@@ -1124,37 +1136,37 @@
</itemizedlist>
<sect4>
- <title><command>TRUNCATE</></title>
+ <title><command>TRUNCATE</command></title>
<itemizedlist>
<listitem>
<para>
- Support statement-level <literal>ON TRUNCATE</> triggers (Simon)
+ Support statement-level <literal>ON TRUNCATE</literal> triggers (Simon)
</para>
</listitem>
<listitem>
<para>
- Add <command>TRUNCATE TABLE</> ...
- <literal>RESTART</>/<literal>CONTINUE IDENTITY</> clauses
+ Add <command>TRUNCATE TABLE</command> ...
+ <literal>RESTART</literal>/<literal>CONTINUE IDENTITY</literal> clauses
(Zoltan Boszormenyi)
</para>
<para>
The start value of a sequence can be changed by <command>ALTER
- SEQUENCE START WITH</>.
+ SEQUENCE START WITH</command>.
</para>
</listitem>
<listitem>
<para>
- Allow <command>TRUNCATE tab1, tab1</> to succeed (Bruce)
+ Allow <command>TRUNCATE tab1, tab1</command> to succeed (Bruce)
</para>
</listitem>
<listitem>
<para>
- Add a separate <command>TRUNCATE</> permission (Robert Haas)
+ Add a separate <command>TRUNCATE</command> permission (Robert Haas)
</para>
</listitem>
@@ -1163,38 +1175,39 @@
</sect4>
<sect4>
- <title><command>EXPLAIN</></title>
+ <title><command>EXPLAIN</command></title>
<itemizedlist>
<listitem>
<para>
- Have <command>EXPLAIN VERBOSE</> show the output columns of a
+ Have <command>EXPLAIN VERBOSE</command> show the output columns of a
query (Tom)
</para>
<para>
- Previously <command>EXPLAIN VERBOSE</> output an internal
+ Previously <command>EXPLAIN VERBOSE</command> output an internal
representation of the query plan. (That behavior is now
- available via <varname>debug_print_plan</>.)
+ available via <varname>debug_print_plan</varname>.)
</para>
</listitem>
<listitem>
<para>
- Make <command>EXPLAIN</> identify subplans and initplans with
+ Make <command>EXPLAIN</command> identify subplans and initplans with
individual labels (Tom)
</para>
</listitem>
<listitem>
<para>
- Have <command>EXPLAIN</> honor <varname>debug_print_plan</> (Tom)
+ Have <command>EXPLAIN</command> honor
+<varname>debug_print_plan</varname> (Tom)
</para>
</listitem>
<listitem>
<para>
- Allow <command>EXPLAIN</> on <command>CREATE TABLE AS</> (Peter)
+ Allow <command>EXPLAIN</command> on <command>CREATE TABLE AS</command> (Peter)
</para>
</listitem>
@@ -1203,33 +1216,34 @@
</sect4>
<sect4>
- <title><literal>LIMIT</>/<literal>OFFSET</></title>
+ <title><literal>LIMIT</literal>/<literal>OFFSET</literal></title>
<itemizedlist>
<listitem>
<para>
- Allow <literal>LIMIT</> and <literal>OFFSET</> to use subselects
+ Allow <literal>LIMIT</literal> and <literal>OFFSET</literal> to use subselects
as arguments (Tom)
</para>
</listitem>
<listitem>
<para>
- Document that <literal>LIMIT NULL</> and <literal>OFFSET NULL</>
+ Document that <literal>LIMIT NULL</literal> and <literal>OFFSET
+ NULL</literal>
have no effect (Tom)
</para>
</listitem>
<listitem>
<para>
- Add <acronym>SQL</>-standard syntax for
- <literal>LIMIT</>/<literal>OFFSET</> capabilities (Peter)
+ Add <acronym>SQL</acronym>-standard syntax for
+ <literal>LIMIT</literal>/<literal>OFFSET</literal> capabilities (Peter)
</para>
<para>
To wit,
<literal>OFFSET num {ROW|ROWS} FETCH {FIRST|NEXT} [num] {ROW|ROWS}
- ONLY</>.
+ ONLY</literal>.
</para>
</listitem>
@@ -1252,22 +1266,22 @@
<listitem>
<para>
- Improve reporting of dependencies during <command>DROP</>
+ Improve reporting of dependencies during <command>DROP</command>
commands (Alex Hunsaker)
</para>
</listitem>
<listitem>
<para>
- Refactor multi-object <command>DROP</> operations so conflicting
+ Refactor multi-object <command>DROP</command> operations so conflicting
dependencies do not generate an error (Alex Hunsaker)
</para>
</listitem>
<listitem>
<para>
- Add <literal>WITH [NO] DATA</> clause to <command>CREATE TABLE
- AS</>, per the <acronym>SQL</> standard (Tom, Peter)
+ Add <literal>WITH [NO] DATA</literal> clause to <command>CREATE TABLE
+ AS</command>, per the <acronym>SQL</acronym> standard (Tom, Peter)
</para>
</listitem>
@@ -1279,14 +1293,15 @@
<listitem>
<para>
- Allow <command>CREATE AGGREGATE</> to use an <type>internal</>
+ Allow <command>CREATE AGGREGATE</command> to use an
+ <type>internal</type>
transition datatype (for super-users only) (Tom)
</para>
</listitem>
<listitem>
<para>
- Add <literal>LIKE</> clause to <command>CREATE TYPE</> (Tom)
+ Add <literal>LIKE</literal> clause to <command>CREATE TYPE</command> (Tom)
</para>
<para>
@@ -1297,26 +1312,26 @@
<listitem>
<para>
- Allow <command>CREATE OR REPLACE VIEW</> to add columns to the
- <emphasis>end</> of a view (Robert Haas)
+ Allow <command>CREATE OR REPLACE VIEW</command> to add columns to the
+ <emphasis>end</emphasis> of a view (Robert Haas)
</para>
</listitem>
</itemizedlist>
<sect4>
- <title><command>ALTER</></title>
+ <title><command>ALTER</command></title>
<itemizedlist>
<listitem>
<para>
- Add <command>ALTER TYPE RENAME</> (Petr Jelinek)
+ Add <command>ALTER TYPE RENAME</command> (Petr Jelinek)
</para>
</listitem>
<listitem>
<para>
- Add <command>ALTER SEQUENCE ... RESTART</> (no parameter) to
+ Add <command>ALTER SEQUENCE ... RESTART</command> (no parameter) to
reset a sequence to its initial value (Zoltan Boszormenyi)
bjm: compatibility problem?
</para>
@@ -1324,7 +1339,7 @@
<listitem>
<para>
- Modify the <command>ALTER TABLE</> syntax to allow all reasonable
+ Modify the <command>ALTER TABLE</command> syntax to allow all reasonable
combinations for tables, indexes, sequences, and views (Tom)
</para>
</listitem>
@@ -1332,29 +1347,29 @@
<listitem>
<para>
New syntax supported (these formerly required <command>ALTER
- TABLE</>)
+ TABLE</command>)
</para>
<para>
<itemizedlist>
<listitem>
<para>
- <command>ALTER SEQUENCE OWNER TO</>
+ <command>ALTER SEQUENCE OWNER TO</command>
</para>
</listitem>
<listitem>
<para>
- <command>ALTER VIEW ALTER COLUMN SET/DROP DEFAULT</>
+ <command>ALTER VIEW ALTER COLUMN SET/DROP DEFAULT</command>
</para>
</listitem>
<listitem>
<para>
- <command>ALTER VIEW OWNER TO</>
+ <command>ALTER VIEW OWNER TO</command>
</para>
</listitem>
<listitem>
<para>
- <command>ALTER VIEW SET SCHEMA</>
+ <command>ALTER VIEW SET SCHEMA</command>
</para>
</listitem>
</itemizedlist>
@@ -1365,24 +1380,24 @@
<listitem>
<para>
Add support for the syntax <command>ALTER TABLE ... ALTER COLUMN
- ... SET DATA TYPE</> (Peter)
+ ... SET DATA TYPE</command> (Peter)
</para>
<para>
- This is <acronym>SQL</>-standard syntax for functionality that
+ This is <acronym>SQL</acronym>-standard syntax for functionality that
was already supported.
</para>
</listitem>
<listitem>
<para>
- Have <command>ALTER TABLE SET WITHOUT OIDS</> rewrite the table
- to remove <type>OID</> values (Tom)
+ Have <command>ALTER TABLE SET WITHOUT OIDS</command> rewrite the table
+ to remove <type>OID</type> values (Tom)
</para>
<para>
- Also, add <command>ALTER TABLE SET WITH OIDS</> to rewrite the
- table to add <type>OID</>s.
+ Also, add <command>ALTER TABLE SET WITH OIDS</command> to rewrite the
+ table to add <type>OID</type>s.
</para>
</listitem>
@@ -1397,7 +1412,8 @@
<listitem>
<para>
Improve reporting of
- <command>CREATE</>/<command>DROP</>/<command>RENAME DATABASE</>
+ <command>CREATE</command>/<command>DROP</command>/<command>RENAME
+ DATABASE</command>
failure when uncommitted prepared transactions are the cause
(Tom)
</para>
@@ -1405,7 +1421,7 @@
<listitem>
<para>
- Make <varname>LC_COLLATE</> and <varname>LC_CTYPE</> database-level
+ Make <varname>LC_COLLATE</varname> and <varname>LC_CTYPE</varname> database-level
settings (Radek Strnad, Heikki)
</para>
@@ -1418,14 +1434,14 @@
<listitem>
<para>
Improve checks that the database encoding, collation
- (<varname>LC_COLLATE</>), and character classes
- (<varname>LC_CTYPE</>) match (Heikki)
+ (<varname>LC_COLLATE</varname>), and character classes
+ (<varname>LC_CTYPE</varname>) match (Heikki)
</para>
</listitem>
<listitem>
<para>
- Add <command>ALTER DATABASE SET TABLESPACE</> to move a database
+ Add <command>ALTER DATABASE SET TABLESPACE</command> to move a database
to a new tablespace (Guillaume Lelarge, Bernd Helmle)
</para>
</listitem>
@@ -1443,8 +1459,8 @@
<listitem>
<para>
- Add verbose option to the <command>CLUSTER</> command and
- <application>clusterdb</> (Jim Cox)
+ Add verbose option to the <command>CLUSTER</command> command and
+ <application>clusterdb</application> (Jim Cox)
</para>
</listitem>
@@ -1498,8 +1514,8 @@
<listitem>
<para>
- <literal>xxx_pattern_ops</> indexes can now be used for simple
- equality comparisons, not only <literal>LIKE</> (Tom)
+ <literal>xxx_pattern_ops</literal> indexes can now be used for simple
+ equality comparisons, not only <literal>LIKE</literal> (Tom)
</para>
</listitem>
@@ -1513,26 +1529,26 @@
<listitem>
<para>
- Remove the requirement to use <literal>@@@</> when doing
- <acronym>GIN</> weighted lookups on full text indexes (Tom)
+ Remove the requirement to use <literal>@@@</literal> when doing
+ <acronym>GIN</acronym> weighted lookups on full text indexes (Tom)
</para>
<para>
- The normal <literal>@@</> text search operator can be used
+ The normal <literal>@@</literal> text search operator can be used
instead.
</para>
</listitem>
<listitem>
<para>
- Add an optimizer selectivity function for <literal>@@</> text
+ Add an optimizer selectivity function for <literal>@@</literal> text
search operations (Jan Urbanski)
</para>
</listitem>
<listitem>
<para>
- Add partial match support for <acronym>GIN</> indexes (Teodor
+ Add partial match support for <acronym>GIN</acronym> indexes (Teodor
Sigaev, Oleg Bartunov)
</para>
</listitem>
@@ -1552,7 +1568,7 @@
<listitem>
<para>
- Support multi-column <acronym>GIN</> indexes (Teodor Sigaev)
+ Support multi-column <acronym>GIN</acronym> indexes (Teodor Sigaev)
</para>
</listitem>
@@ -1561,7 +1577,7 @@
</sect4>
<sect4>
- <title><command>VACUUM</></title>
+ <title><command>VACUUM</command></title>
<itemizedlist>
<listitem>
@@ -1571,9 +1587,9 @@
<para>
This allows the recording of all free space discovered by vacuum
- in <filename>*.fsm</> files, rather than having to limit
+ in <filename>*.fsm</filename> files, rather than having to limit
recording to a fixed-sized shared memory area;
- <varname>max_fsm_pages</> and <varname>max_fsm_relations</>
+ <varname>max_fsm_pages</varname> and <varname>max_fsm_relations</varname>
settings have been removed.
</para>
</listitem>
@@ -1585,7 +1601,7 @@
</para>
<para>
- This allows <command>VACUUM</> to avoid sequentially scanning
+ This allows <command>VACUUM</command> to avoid sequentially scanning
a table when only a portion of the table needs vacuuming.
</para>
</listitem>
@@ -1603,16 +1619,16 @@
<listitem>
<para>
- Add <varname>vacuum_freeze_table_age</> parameter to control
- when <command>VACUUM</> should ignore the visibility map and
+ Add <varname>vacuum_freeze_table_age</varname> parameter to control
+ when <command>VACUUM</command> should ignore the visibility map and
do a full table scan to set frozen xids (Heikki)
</para>
</listitem>
<listitem>
<para>
- Add ability to specify autovacuum and <acronym>TOAST</> parameters
- in <command>CREATE TABLE</> (Alvaro, Euler Taveira de Oliveira)
+ Add ability to specify autovacuum and <acronym>TOAST</acronym> parameters
+ in <command>CREATE TABLE</command> (Alvaro, Euler Taveira de Oliveira)
</para>
<para>
@@ -1622,7 +1638,7 @@
<listitem>
<para>
- Add <literal>--freeze</> option to <application>vacuumdb</>
+ Add <literal>--freeze</literal> option to <application>vacuumdb</application>
(Bruce)
</para>
</listitem>
@@ -1639,20 +1655,20 @@
<listitem>
<para>
- Add a <literal>CaseSensitive</> option for text search synonym
+ Add a <literal>CaseSensitive</literal> option for text search synonym
dictionaries (Simon)
</para>
</listitem>
<listitem>
<para>
- Improve the precision of <type>NUMERIC</> division (Tom)
+ Improve the precision of <type>NUMERIC</type> division (Tom)
</para>
</listitem>
<listitem>
<para>
- Add <type>int2</> with <type>int8</> basic arithmetic operators
+ Add <type>int2</type> with <type>int8</type> basic arithmetic operators
(Tom)
</para>
@@ -1663,22 +1679,22 @@
<listitem>
<para>
- Allow <type>UUID</> input to accept optional hyphens after
+ Allow <type>UUID</type> input to accept optional hyphens after
every four digits (Robert Haas)
</para>
</listitem>
<listitem>
<para>
- Accept <literal>on</>/<literal>off</> as boolean data type
+ Accept <literal>on</literal>/<literal>off</literal> as boolean data type
values (Itagaki Takahiro)
</para>
</listitem>
<listitem>
<para>
- Allow spaces around <literal>NaN</> in the input string for
- type <type>numeric</> (Sam Mason)
+ Allow spaces around <literal>NaN</literal> in the input string for
+ type <type>numeric</type> (Sam Mason)
</para>
</listitem>
@@ -1690,72 +1706,73 @@
<listitem>
<para>
- Reject year <literal>0 BC</> and years <literal>000</> and
- <literal>0000</> (Tom)
+ Reject year <literal>0 BC</literal> and years <literal>000</literal> and
+ <literal>0000</literal> (Tom)
</para>
<para>
- Previously these were interpreted as <literal>1 BC</>; years
- <literal>0</> and <literal>00</> are assumed to be the year
+ Previously these were interpreted as <literal>1 BC</literal>; years
+ <literal>0</literal> and <literal>00</literal> are assumed to be the year
2000.
</para>
</listitem>
<listitem>
<para>
- Include <acronym>SGT</> (Singapore time) as a valid time zone
+ Include <acronym>SGT</acronym> (Singapore time) as a valid time zone
abbreviation (Tom)
</para>
</listitem>
<listitem>
<para>
- Support the <acronym>IS0 8601</> <type>interval</> syntax (Tom,
+ Support the <acronym>IS0 8601</acronym> <type>interval</type> syntax (Tom,
Kevin Grittner)
</para>
<para>
- For example, <literal>INTERVAL 'P1Y2M3DT4H5M6.7S'</> is now
+ For example, <literal>INTERVAL 'P1Y2M3DT4H5M6.7S'</literal> is now
supported.
</para>
</listitem>
<listitem>
<para>
- Allow <type>INTERVAL</> precision to be specified after the
- last field, for <acronym>SQL</>-standards compliance (Tom)
+ Allow <type>INTERVAL</type> precision to be specified after the
+ last field, for <acronym>SQL</acronym>-standards compliance (Tom)
</para>
<para>
Formerly the precision had to be specified after the keyword
- <type>INTERVAL</> (this syntax is still supported). Data type
+ <type>INTERVAL</type> (this syntax is still supported). Data type
definitions will now be output using the new format.
</para>
</listitem>
<listitem>
<para>
- Support <literal>infinite</> dates (Tom)
+ Support <literal>infinite</literal> dates (Tom)
</para>
</listitem>
<listitem>
<para>
- Add <varname>IntervalStyle</> parameter
- which controls how <type>INTERVAL</> values are output (Ron Mayer)
+ Add <varname>IntervalStyle</varname> parameter
+ which controls how <type>INTERVAL</type> values are output (Ron Mayer)
</para>
<para>
- Valid value are: <literal>postgres</>, <literal>postgres_verbose</>,
- <literal>sql_standard</>, <literal>iso_8601</>. This also
- controls the handling of negative <type>INTERVAL</> input when only
+ Valid value are: <literal>postgres</literal>,
+ <literal>postgres_verbose</literal>,
+ <literal>sql_standard</literal>, <literal>iso_8601</literal>. This also
+ controls the handling of negative <type>INTERVAL</type> input when only
some fields have positive/negative designations.
</para>
</listitem>
<listitem>
<para>
- Make <type>INTERVAL</> seconds rounding more consistent across
+ Make <type>INTERVAL</type> seconds rounding more consistent across
output formats (Ron Mayer)
</para>
</listitem>
@@ -1770,33 +1787,33 @@
<listitem>
<para>
- Have cast on <type>ARRAY</> apply to all elements, not just
+ Have cast on <type>ARRAY</type> apply to all elements, not just
the array result (Brendan Jurd)
</para>
<para>
- This allows <literal>NULL</> <type>ARRAY</> entries as long as
+ This allows <literal>NULL</literal> <type>ARRAY</type> entries as long as
they are properly cast.
</para>
</listitem>
<listitem>
<para>
- Make <acronym>SQL</>-syntax <type>ARRAY</> dimensions optional
- to match the <acronym>SQL</> standard (Peter)
+ Make <acronym>SQL</acronym>-syntax <type>ARRAY</type> dimensions optional
+ to match the <acronym>SQL</acronym> standard (Peter)
</para>
</listitem>
<listitem>
<para>
- Add <function>array_ndims()</> to return the number
+ Add <function>array_ndims()</function> to return the number
of dimensions of an array (Robert Haas)
</para>
</listitem>
<listitem>
<para>
- Add <function>array_length()</> to return the length
+ Add <function>array_length()</function> to return the length
of an array for the specified dimensions (Jim Nasby, Robert
Haas, Peter Eisentraut)
</para>
@@ -1804,7 +1821,7 @@
<listitem>
<para>
- Add new aggregate function <function>array_agg()</>, which
+ Add new aggregate function <function>array_agg()</function>, which
returns all aggregated values as a single array (Robert Haas,
Jeff Davis, Peter)
</para>
@@ -1812,32 +1829,32 @@
<listitem>
<para>
- Add <function>unnest()</>, which converts an array to
+ Add <function>unnest()</function>, which converts an array to
individual row values (Tom)
</para>
<para>
- This is the opposite of <function>array_agg()</>.
+ This is the opposite of <function>array_agg()</function>.
</para>
</listitem>
<listitem>
<para>
- Add <function>array_fill()</> to create arrays initialized with
+ Add <function>array_fill()</function> to create arrays initialized with
a value (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
- Add <function>generate_subscripts()</> to generate array
+ Add <function>generate_subscripts()</function> to generate array
subscripts (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
- Generate proper error if a <type>SERIAL</> array is specified
+ Generate proper error if a <type>SERIAL</type> array is specified
(Tom)
</para>
</listitem>
@@ -1847,27 +1864,27 @@
</sect4>
<sect4>
- <title>Wide-Value Storage (<acronym>TOAST</>)</title>
+ <title>Wide-Value Storage (<acronym>TOAST</acronym>)</title>
<itemizedlist>
<listitem>
<para>
- Consider <acronym>TOAST</> compression on values as short as
+ Consider <acronym>TOAST</acronym> compression on values as short as
32 bytes (previously 256 bytes) (Tom)
</para>
</listitem>
<listitem>
<para>
- Require 25% of space savings before using <acronym>TOAST</>
+ Require 25% of space savings before using <acronym>TOAST</acronym>
compression (previously 20%) (Tom)
</para>
</listitem>
<listitem>
<para>
- Be more aggressive in storing <literal>EXTERNAL</> and
- <literal>EXTENDED</> column values in <acronym>TOAST</>(Tom)
+ Be more aggressive in storing <literal>EXTERNAL</literal> and
+ <literal>EXTENDED</literal> column values in <acronym>TOAST</acronym>(Tom)
</para>
</listitem>
@@ -1883,52 +1900,53 @@
<listitem>
<para>
- Document that <function>setseed()</> allows values from
- <literal>-1</> to <literal>1</> (not just <literal>0</> to
- <literal>1</>), and enforce the valid range (Kris Jurka)
+ Document that <function>setseed()</function> allows values from
+ <literal>-1</literal> to <literal>1</literal> (not just
+ <literal>0</literal> to
+ <literal>1</literal>), and enforce the valid range (Kris Jurka)
</para>
</listitem>
<listitem>
<para>
- Add server side function <function>lo_import(filename, oid)</>
+ Add server side function <function>lo_import(filename, oid)</function>
(Tatsuo)
</para>
</listitem>
<listitem>
<para>
- Add <function>quote_nullable()</>, which behaves like
- <function>quote_literal()</> but returns <literal>NULL</> for
+ Add <function>quote_nullable()</function>, which behaves like
+ <function>quote_literal()</function> but returns <literal>NULL</literal> for
a null argument (Brendan Jurd)
</para>
</listitem>
<listitem>
<para>
- Improve full text search <function>headline()</> generation to
+ Improve full text search <function>headline()</function> generation to
allow several fragments (Sushant Sinha)
</para>
</listitem>
<listitem>
<para>
- Add <function>suppress_redundant_updates_trigger()</> trigger
+ Add <function>suppress_redundant_updates_trigger()</function> trigger
function to avoid non-data-changing updates (Andrew)
</para>
</listitem>
<listitem>
<para>
- Add <function>div(NUMERIC, NUMERIC)</> for <type>NUMERIC</>
+ Add <function>div(NUMERIC, NUMERIC)</function> for <type>NUMERIC</type>
division, without rounding (Tom)
</para>
</listitem>
<listitem>
<para>
- Add <type>TIMESTAMP</> and <type>TIMESTAMPTZ</> versions of
- <function>generate_series()</> (Hitoshi Harada)
+ Add <type>TIMESTAMP</type> and <type>TIMESTAMPTZ</type> versions of
+ <function>generate_series()</function> (Hitoshi Harada)
</para>
</listitem>
@@ -1940,72 +1958,73 @@
<listitem>
<para>
- Implement <function>current_query()</> for use by functions
+ Implement <function>current_query()</function> for use by functions
that need to know the currently running query (Tomas Doran)
</para>
</listitem>
<listitem>
<para>
- Add <function>pg_get_keywords()</> to return predefined
+ Add <function>pg_get_keywords()</function> to return predefined
parser keywords (Dave Page)
</para>
</listitem>
<listitem>
<para>
- Add <function>pg_get_functiondef()</> to see a functions
+ Add <function>pg_get_functiondef()</function> to see a functions
definition (Abhijit Menon-Sen)
</para>
</listitem>
<listitem>
<para>
- Modify <function>pg_relation_size()</> to handle free space
- map (<filename>*.fsm</>) files (Heikki)
+ Modify <function>pg_relation_size()</function> to handle free space
+ map (<filename>*.fsm</filename>) files (Heikki)
</para>
</listitem>
<listitem>
<para>
- Modify <function>pg_relation_size()</> to use <literal>regclass</>
+ Modify <function>pg_relation_size()</function> to use
+ <literal>regclass</literal>
(Heikki)
</para>
<para>
- <function>pg_relation_size(data_type_name)</> no longer works.
+ <function>pg_relation_size(data_type_name)</function> no longer works.
</para>
</listitem>
<listitem>
<para>
- Add <literal>boot_val</> and <literal>reset_val</> columns to
- <literal>pg_settings</> output (Greg Smith)
+ Add <literal>boot_val</literal> and <literal>reset_val</literal> columns to
+ <literal>pg_settings</literal> output (Greg Smith)
</para>
</listitem>
<listitem>
<para>
- Add support for <varname>CURRENT_CATALOG</>,
- <varname>CURRENT_SCHEMA</>, <varname>SET CATALOG</>, <varname>SET
- SCHEMA</> (Peter)
+ Add support for <varname>CURRENT_CATALOG</varname>,
+ <varname>CURRENT_SCHEMA</varname>, <varname>SET CATALOG</varname>, <varname>SET
+ SCHEMA</varname> (Peter)
</para>
<para>
- These are <acronym>SQL</>-standard capabilities.
+ These are <acronym>SQL</acronym>-standard capabilities.
</para>
</listitem>
<listitem>
<para>
- Add <function>pg_typeof()</> which returns the data type
+ Add <function>pg_typeof()</function> which returns the data type
of any value (Brendan Jurd)
</para>
</listitem>
<listitem>
<para>
- Have <function>version()</> return information about whether
+ Have <function>version()</function> return information about whether
the server is a 32 or 64-bit binary (Bruce)
</para>
</listitem>
@@ -2013,7 +2032,8 @@
<listitem>
<para>
Fix the behavior of information schema columns
- <literal>is_insertable_into</> and <literal>is_updatable</> to
+ <literal>is_insertable_into</literal> and
+ <literal>is_updatable</literal> to
be consistent (Peter)
</para>
</listitem>
@@ -2021,29 +2041,32 @@
<listitem>
<para>
Convert remaining builtin set-returning functions to use
- <literal>OUT</> parameters (Jaime Casanova)
+ <literal>OUT</literal> parameters (Jaime Casanova)
</para>
<para>
This makes it possible to call these functions without specifying
- a column list: <function>pg_show_all_settings()</>,
- <function>pg_lock_status()</>, <function>pg_prepared_xact()</>,
- <function>pg_prepared_statement()</>, <function>pg_cursor()</>
+ a column list: <function>pg_show_all_settings()</function>,
+ <function>pg_lock_status()</function>,
+ <function>pg_prepared_xact()</function>,
+ <function>pg_prepared_statement()</function>,
+ <function>pg_cursor()</function>
</para>
</listitem>
<listitem>
<para>
- Have <function>pg_*_is_visible()</> and
- <function>has_*_privilege()</> functions return <literal>NULL</>
+ Have <function>pg_*_is_visible()</function> and
+ <function>has_*_privilege()</function> functions return
+ <literal>NULL</literal>
for invalid oids, rather than generate an error (Tom)
</para>
</listitem>
<listitem>
<para>
- Add <function>has_column_privilege()</> and
- <function>has_any_column_privilege()</> functions (Stephen
+ Add <function>has_column_privilege()</function> and
+ <function>has_any_column_privilege()</function> functions (Stephen
Frost, Tom)
</para>
</listitem>
@@ -2070,27 +2093,28 @@
<listitem>
<para>
- Allow <literal>DEFAULT</> values for function arguments (Pavel
+ Allow <literal>DEFAULT</literal> values for function arguments (Pavel
Stehule)
</para>
</listitem>
<listitem>
<para>
- Add <command>CREATE FUNCTION ... RETURNS TABLE</> clause (Pavel
+ Add <command>CREATE FUNCTION ... RETURNS TABLE</command> clause (Pavel
Stehule)
</para>
</listitem>
<listitem>
<para>
- Allow <acronym>SQL</>-language functions to return the output
- of an <command>INSERT</>/<command>UPDATE</>/<command>DELETE</>
- <literal>RETURNING</> clause (Tom)
+ Allow <acronym>SQL</acronym>-language functions to return the output
+ of an
+ <command>INSERT</command>/<command>UPDATE</command>/<command>DELETE</command>
+ <literal>RETURNING</literal> clause (Tom)
</para>
<para>
- Formerly only <command>SELECT</> was supported.
+ Formerly only <command>SELECT</command> was supported.
</para>
</listitem>
@@ -2104,37 +2128,37 @@
<listitem>
<para>
- Support <literal>EXECUTE USING</> (Pavel Stehule)
+ Support <literal>EXECUTE USING</literal> (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
- Allow looping over an open cursor using a <literal>FOR</>
+ Allow looping over an open cursor using a <literal>FOR</literal>
loop (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
- Support <literal>RETURN QUERY EXECUTE</> (Pavel
+ Support <literal>RETURN QUERY EXECUTE</literal> (Pavel
Stehule)
</para>
</listitem>
<listitem>
<para>
- Improve the <literal>RAISE</> command: (Pavel Stehule)
+ Improve the <literal>RAISE</literal> command: (Pavel Stehule)
<itemizedlist>
<listitem>
<para>
- Support <literal>DETAIL</> and <literal>HINT</> fields
+ Support <literal>DETAIL</literal> and <literal>HINT</literal> fields
</para>
</listitem>
<listitem>
<para>
- Support <literal>SQLSTATE</> error codes
+ Support <literal>SQLSTATE</literal> error codes
</para>
</listitem>
<listitem>
@@ -2144,7 +2168,7 @@
</listitem>
<listitem>
<para>
- Allow <literal>RAISE</> without parameters in an exception
+ Allow <literal>RAISE</literal> without parameters in an exception
block to rethrow the current error
</para>
</listitem>
@@ -2154,32 +2178,32 @@
<listitem>
<para>
- Allow specification of <varname>SQLSTATE</> numeric codes
- in <literal>EXCEPTION</> lists (Pavel Stehule)
+ Allow specification of <varname>SQLSTATE</varname> numeric codes
+ in <literal>EXCEPTION</literal> lists (Pavel Stehule)
</para>
<para>
- This is useful for handling custom <varname>SQLSTATE</> codes.
+ This is useful for handling custom <varname>SQLSTATE</varname> codes.
</para>
</listitem>
<listitem>
<para>
- Support the <literal>CASE</> statement (Pavel Stehule)
+ Support the <literal>CASE</literal> statement (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
- Add <literal>FOUND</> and <command>GET DIAGNOSTICS</> support
- for the <literal>RETURN QUERY</> statement (Pavel Stehule)
+ Add <literal>FOUND</literal> and <command>GET DIAGNOSTICS</command> support
+ for the <literal>RETURN QUERY</literal> statement (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
- Make <command>FETCH</> and <command>MOVE</> set the
- <command>GET DIAGNOSTICS</> <literal>ROW_COUNT</> variable
+ Make <command>FETCH</command> and <command>MOVE</command> set the
+ <command>GET DIAGNOSTICS</command> <literal>ROW_COUNT</literal> variable
(Andrew Gierth)
</para>
</listitem>
@@ -2210,27 +2234,28 @@
<listitem>
<para>
- Fix <literal>pg_ctl restart</> to preserve command-line arguments
+ Fix <literal>pg_ctl restart</literal> to preserve command-line arguments
(Bruce)
</para>
</listitem>
<listitem>
<para>
- Add <literal>-w</>/<literal>--no-password</> option that
+ Add <literal>-w</literal>/<literal>--no-password</literal> option that
suppresses password prompts to all utilities that have a
- <literal>-W</>/<literal>--password</> option (Peter)
+ <literal>-W</literal>/<literal>--password</literal> option (Peter)
</para>
</listitem>
<listitem>
<para>
- Remove <literal>-q</> (quiet) option for create* and drop*
+ Remove <literal>-q</literal> (quiet) option for create* and drop*
utility commands (Peter)
</para>
<para>
- These options have had no effect since <productname>PostgreSQL</>
+ These options have had no effect since
+ <productname>PostgreSQL</productname>
8.3.
</para>
</listitem>
@@ -2238,27 +2263,28 @@
</itemizedlist>
<sect4>
- <title><link linkend="APP-PSQL"><application>psql</></link></title>
+ <title><link linkend="APP-PSQL"><application>psql</application></link></title>
<itemizedlist>
<listitem>
<para>
- Remove startup banner; now just suggest <literal>help</>
+ Remove startup banner; now just suggest <literal>help</literal>
(Joshua Drake)
</para>
</listitem>
<listitem>
<para>
- Have <literal>help</> show common backslash commands (Greg
+ Have <literal>help</literal> show common backslash commands (Greg
Sabino Mullane)
</para>
</listitem>
<listitem>
<para>
- Add <literal>\pset format wrapped</> mode to wrap output to the
- screen width, or file/pipe output too if <literal>\pset columns</>
+ Add <literal>\pset format wrapped</literal> mode to wrap output to the
+ screen width, or file/pipe output too if <literal>\pset
+ columns</literal>
is set (Bryce Nesbitt)
</para>
</listitem>
@@ -2292,39 +2318,39 @@
<listitem>
<para>
- Allow the normal range of boolean values in <command>\pset</>,
- rather than just <literal>on</> and <literal>off</> (Bruce)
+ Allow the normal range of boolean values in <command>\pset</command>,
+ rather than just <literal>on</literal> and <literal>off</literal> (Bruce)
</para>
</listitem>
<listitem>
<para>
- Add optional <literal>on</>/<literal>off</> arguments for
- <command>\timing</> (David Fetter)
+ Add optional <literal>on</literal>/<literal>off</literal> arguments for
+ <command>\timing</command> (David Fetter)
</para>
</listitem>
<listitem>
<para>
- Have <command>\l</> show access privileges (Andrew Gilligan)
+ Have <command>\l</command> show access privileges (Andrew Gilligan)
</para>
</listitem>
<listitem>
<para>
- Have <command>\l+</> show database sizes, if permissions
+ Have <command>\l+</command> show database sizes, if permissions
allow (Andrew Gilligan)
</para>
</listitem>
<listitem>
<para>
- Add the <command>\ef</> command to edit function definitions
+ Add the <command>\ef</command> command to edit function definitions
(Abhijit Menon-Sen)
</para>
<para>
- <command>\ef</> without a function name creates an empty
+ <command>\ef</command> without a function name creates an empty
function template for editing.
</para>
</listitem>
@@ -2334,19 +2360,19 @@
</sect4>
<sect4>
- <title><link linkend="APP-PSQL"><application>psql</></link> \d*</title>
+ <title><link linkend="APP-PSQL"><application>psql</application></link> \d*</title>
<itemizedlist>
<listitem>
<para>
- Have <command>\d</> show cases where this table is referenced
+ Have <command>\d</command> show cases where this table is referenced
as a foreign-key constraint (Kenneth D'Souza)
</para>
</listitem>
<listitem>
<para>
- Have <command>\d</> show the value of sequence columns
+ Have <command>\d</command> show the value of sequence columns
(Euler Taveira de Oliveira)
</para>
</listitem>
@@ -2354,66 +2380,67 @@
<listitem>
<para>
Add column storage type and other relation options to the
- <command>\d+</> display (Gregory Stark, Euler Taveira de
+ <command>\d+</command> display (Gregory Stark, Euler Taveira de
Oliveira)
</para>
</listitem>
<listitem>
<para>
- Show relation size in <command>\d+</> output (Dickson S.
+ Show relation size in <command>\d+</command> output (Dickson S.
Guedes)
</para>
</listitem>
<listitem>
<para>
- Make <command>\d*</> commands that do not have a pattern argument
- show system objects only if the <literal>S</> modifier is specified
+ Make <command>\d*</command> commands that do not have a pattern argument
+ show system objects only if the <literal>S</literal> modifier is specified
(Greg Sabino Mullane, Bruce)
</para>
<para>
The former behavior was inconsistent across different variants
- of <command>\d</>, and provided no easy way to see just user objects.
+ of <command>\d</command>, and provided no easy way to see just user objects.
</para>
</listitem>
<listitem>
<para>
- Make <command>\d</> and <command>\dt</> consistent in
+ Make <command>\d</command> and <command>\dt</command> consistent in
their display of system tables (Bruce)
</para>
<para>
- Previously, <literal>\d pg_class</> would show <literal>pg_class</>
- while <literal>\dt pg_class</> would not.
+ Previously, <literal>\d pg_class</literal> would show
+ <literal>pg_class</literal>
+ while <literal>\dt pg_class</literal> would not.
</para>
</listitem>
<listitem>
<para>
- Show enumerated values in <command>\dT+</> (David Fetter)
+ Show enumerated values in <command>\dT+</command> (David Fetter)
</para>
</listitem>
<listitem>
<para>
- Allow <command>\dC</> to accept wildcard patterns (Tom)
+ Allow <command>\dC</command> to accept wildcard patterns (Tom)
</para>
</listitem>
<listitem>
<para>
- Allow <command>\d*</> commands to work with versions of
- <productname>PostgreSQL</> back to 7.4 (Guillaume Lelarge)
+ Allow <command>\d*</command> commands to work with versions of
+ <productname>PostgreSQL</productname> back to 7.4 (Guillaume Lelarge)
</para>
</listitem>
<listitem>
<para>
- Make <command>\df</> not hide functions that take or return
- type <type>cstring</> (Tom)
+ Make <command>\df</command> not hide functions that take or return
+ type <type>cstring</type> (Tom)
</para>
<para>
@@ -2429,13 +2456,13 @@
</sect4>
<sect4>
- <title><link linkend="APP-PGDUMP"><application>pg_dump</></link></title>
+ <title><link linkend="APP-PGDUMP"><application>pg_dump</application></link></title>
<itemizedlist>
<listitem>
<para>
- Add a <literal>--no-tablespaces</> option to
- <application>pg_dump</>/<application>pg_dumpall</>/<application>pg_restore</>
+ Add a <literal>--no-tablespaces</literal> option to
+ <application>pg_dump</application>/<application>pg_dumpall</application>/<application>pg_restore</application>
so dumps can be restored to clusters that have non-matching
tablespace layouts (Gavin Roy)
</para>
@@ -2443,23 +2470,25 @@
<listitem>
<para>
- Remove <option>-d</> and <option>-D</> options from
- <application>pg_dump</> and <application>pg_dumpall</> (Tom)
+ Remove <option>-d</option> and <option>-D</option> options from
+ <application>pg_dump</application> and
+ <application>pg_dumpall</application> (Tom)
</para>
<para>
These options were too frequently confused with the option to
- select a database name in other <productname>PostgreSQL</>
+ select a database name in other <productname>PostgreSQL</productname>
client applications. The functionality is still available,
but you must spell out the long option name
- <option>--inserts</> or <option>--column-inserts</>.
+ <option>--inserts</option> or <option>--column-inserts</option>.
</para>
</listitem>
<listitem>
<para>
- Remove <option>-i</>/<option>--ignore-version</> option from
- <application>pg_dump</> and <application>pg_dumpall</> (Tom)
+ Remove <option>-i</option>/<option>--ignore-version</option> option from
+ <application>pg_dump</application> and
+ <application>pg_dumpall</application> (Tom)
</para>
<para>
@@ -2471,15 +2500,16 @@
<listitem>
<para>
- Disable <varname>statement_timeout</> during dump and restore
+ Disable <varname>statement_timeout</varname> during dump and restore
(Joshua Drake)
</para>
</listitem>
<listitem>
<para>
- Add <application>pg_dump</>/<application>pg_dumpall</> option
- <option>--lock-wait-timeout</> (David Gould)
+ Add
+ <application>pg_dump</application>/<application>pg_dumpall</application> option
+ <option>--lock-wait-timeout</option> (David Gould)
</para>
<para>
@@ -2490,41 +2520,45 @@
<listitem>
<para>
- Reorder <application>pg_dump</> <literal>--data-only</> output
+ Reorder <application>pg_dump</application>
+ <literal>--data-only</literal> output
to dump primary-key tables referenced by foreign keys before
the foreign-key referencing tables (Tom)
</para>
<para>
This allows data loads when foreign keys are already present.
- If circular references make this impossible, a <literal>NOTICE</>
+ If circular references make this impossible, a
+ <literal>NOTICE</literal>
is issued.
</para>
</listitem>
<listitem>
<para>
- Allow <application>pg_dump</>, <application>pg_dumpall</>, and
- <application>pg_restore</> to use a specified role (Benedek
+ Allow <application>pg_dump</application>,
+ <application>pg_dumpall</application>, and
+ <application>pg_restore</application> to use a specified role (Benedek
László)
</para>
</listitem>
<listitem>
<para>
- Allow <application>pg_restore</> of a custom format archive to
+ Allow <application>pg_restore</application> of a custom format archive to
use multiple concurrent connections to do the restore (Andrew)
</para>
<para>
The number of concurrent connections is controlled by the option
- <literal>--jobs</>.
+ <literal>--jobs</literal>.
</para>
</listitem>
<listitem>
<para>
- Add new <application>pg_dump</> <literal>--binary-upgrade</>
+ Add new <application>pg_dump</application>
+ <literal>--binary-upgrade</literal>
option for use by binary upgrade utilities (Bruce)
</para>
</listitem>
@@ -2539,13 +2573,13 @@
<title>Programming Tools</title>
<sect4>
- <title><link linkend="libpq"><application>libpq</></link></title>
+ <title><link linkend="libpq"><application>libpq</application></link></title>
<itemizedlist>
<listitem>
<para>
- Allow the <type>OID</> to be specified when importing large
- objects using <function>lo_import_with_oid()</> (Tatsuo)
+ Allow the <type>OID</type> to be specified when importing large
+ objects using <function>lo_import_with_oid()</function> (Tatsuo)
</para>
</listitem>
@@ -2569,18 +2603,18 @@
<listitem>
<para>
- Have <function>PQexecParams()</> return
- <varname>PGRES_EMPTY_QUERY</> for an empty query (Tom)
+ Have <function>PQexecParams()</function> return
+ <varname>PGRES_EMPTY_QUERY</varname> for an empty query (Tom)
</para>
<para>
- It previously returned <varname>PGRES_COMMAND_OK</>.
+ It previously returned <varname>PGRES_COMMAND_OK</varname>.
</para>
</listitem>
<listitem>
<para>
- Document how to avoid the overhead of <function>WSACleanup()</>
+ Document how to avoid the overhead of <function>WSACleanup()</function>
on Windows (Andrew Chernow)
</para>
</listitem>
@@ -2590,22 +2624,22 @@
</sect4>
<sect4>
- <title><link linkend="libpq"><application>libpq</></link>
- <acronym>SSL</> (Secure Sockets Layer)</title>
+ <title><link linkend="libpq"><application>libpq</application></link>
+ <acronym>SSL</acronym> (Secure Sockets Layer)</title>
<itemizedlist>
<listitem>
<para>
- Fix certificate validation for <acronym>SSL</> connections
+ Fix certificate validation for <acronym>SSL</acronym> connections
(Magnus)
</para>
<para>
- <application>libpq</> now verifies both the certificate and
- the name of the server by default when making <acronym>SSL</>
+ <application>libpq</application> now verifies both the certificate and
+ the name of the server by default when making <acronym>SSL</acronym>
connections. If a root certificate is not available to use for
- verification, <acronym>SSL</> connections will fail. The
- <literal>sslverify</> parameter can be used to disable the host
+ verification, <acronym>SSL</acronym> connections will fail. The
+ <literal>sslverify</literal> parameter can be used to disable the host
and certificate verification if required.
</para>
</listitem>
@@ -2619,7 +2653,7 @@
<listitem>
<para>
- Add connection parameter <literal>sslverify</> to control
+ Add connection parameter <literal>sslverify</literal> to control
the verification of the server's certificate
(Magnus)
</para>
@@ -2631,20 +2665,20 @@
<listitem>
<para>
- Add a <function>PQinitOpenSSL</> function to allow greater control
+ Add a <function>PQinitOpenSSL</function> function to allow greater control
over OpenSSL/libcrypto initialization (Andrew Chernow)
</para>
</listitem>
<listitem>
<para>
- Properly unregister <application>OpenSSL</> callbacks when
+ Properly unregister <application>OpenSSL</application> callbacks when
libpq is done with all connections (Bruce, Magnus, Russell Smith)
</para>
<para>
This is required for applications that unload the libpq library,
- otherwise invalid <application>OpenSSL</> callbacks will remain.
+ otherwise invalid <application>OpenSSL</application> callbacks will remain.
</para>
</listitem>
@@ -2653,7 +2687,7 @@
</sect4>
<sect4>
- <title><link linkend="ecpg"><application>ecpg</></link></title>
+ <title><link linkend="ecpg"><application>ecpg</application></link></title>
<itemizedlist>
<listitem>
@@ -2679,7 +2713,7 @@
</sect4>
<sect4>
- <title>Server Programming Interface (<acronym>SPI</>)</title>
+ <title>Server Programming Interface (<acronym>SPI</acronym>)</title>
<itemizedlist>
<listitem>
@@ -2691,8 +2725,8 @@
<listitem>
<para>
- Add new <varname>SPI_OK_REWRITTEN</> return code to
- <function>SPI_execute()</> (Heikki)
+ Add new <varname>SPI_OK_REWRITTEN</varname> return code to
+ <function>SPI_execute()</function> (Heikki)
</para>
<para>
@@ -2717,7 +2751,7 @@
</para>
<para>
- This adds support for daylight saving time (<acronym>DST</>)
+ This adds support for daylight saving time (<acronym>DST</acronym>)
calculations beyond year 2038.
</para>
</listitem>
@@ -2731,13 +2765,13 @@
<listitem>
<para>
- Update build system to use <productname>Autoconf</> 2.61 (Peter)
+ Update build system to use <productname>Autoconf</productname> 2.61 (Peter)
</para>
</listitem>
<listitem>
<para>
- Require <productname>GNU bison</> for source code builds (Peter)
+ Require <productname>GNU bison</productname> for source code builds (Peter)
</para>
<para>
@@ -2748,58 +2782,60 @@
<listitem>
<para>
- Add <application>pg_config</> <literal>--htmldir</> option
+ Add <application>pg_config</application> <literal>--htmldir</literal> option
(Peter)
</para>
</listitem>
<listitem>
<para>
- Pass <type>float4</> by value inside the server (Zoltan
+ Pass <type>float4</type> by value inside the server (Zoltan
Boszormenyi)
</para>
<para>
- Add <application>configure</> option
- <literal>--disable-float4-byval</> to use the old behavior.
+ Add <application>configure</application> option
+ <literal>--disable-float4-byval</literal> to use the old behavior.
</para>
</listitem>
<listitem>
<para>
- Pass <type>float8</> and <type>int8</> by value in the server
+ Pass <type>float8</type> and <type>int8</type> by value in the server
where possible (Zoltan Boszormenyi)
</para>
<para>
- Add <application>configure</> option
- <literal>--disable-float8-byval</> to use the old behavior.
+ Add <application>configure</application> option
+ <literal>--disable-float8-byval</literal> to use the old behavior.
</para>
</listitem>
<listitem>
<para>
- Add configure options <literal>--with-segsize</>,
- <literal>--with-blocksize</>, <literal>--with-wal-blocksize</>,
- <literal>--with-wal-segsize</> (Zdenek Kotala, Tom)
+ Add configure options <literal>--with-segsize</literal>,
+ <literal>--with-blocksize</literal>,
+ <literal>--with-wal-blocksize</literal>,
+ <literal>--with-wal-segsize</literal> (Zdenek Kotala, Tom)
</para>
<para>
This allows compile-time control over several constants that
- affect how tables and <acronym>WAL</> files are segmented and
+ affect how tables and <acronym>WAL</acronym> files are segmented and
their internal block sizes.
</para>
</listitem>
<listitem>
<para>
- Allow threaded builds on <productname>Solaris</> 2.5 (Bruce)
+ Allow threaded builds on <productname>Solaris</productname> 2.5 (Bruce)
</para>
</listitem>
<listitem>
<para>
- Use the system's <function>getopt_long()</> on <productname>Solaris</>
+ Use the system's <function>getopt_long()</function> on
+ <productname>Solaris</productname>
(Zdenek Kotala, Tom)
</para>
@@ -2811,15 +2847,16 @@
<listitem>
<para>
- Add support for the <productname>Sun Studio</> compiler on
- <productname>Linux</> (Julius Stroffek)
+ Add support for the <productname>Sun Studio</productname> compiler on
+ <productname>Linux</productname> (Julius Stroffek)
</para>
</listitem>
<listitem>
<para>
- Append the major version number to the <application>gettext</>
- domain, and the <literal>soname</> major version number to
+ Append the major version number to the
+ <application>gettext</application>
+ domain, and the <literal>soname</literal> major version number to
libraries (Peter)
</para>
@@ -2830,22 +2867,22 @@
<listitem>
<para>
- Allow out-of-tree builds on <productname>Mingw</> and
- <productname>Cygwin</> (Richard Evans)
+ Allow out-of-tree builds on <productname>Mingw</productname> and
+ <productname>Cygwin</productname> (Richard Evans)
</para>
</listitem>
<listitem>
<para>
- Fix the use of <productname>Mingw</> as a cross-compiling source
+ Fix the use of <productname>Mingw</productname> as a cross-compiling source
platform (Peter)
</para>
</listitem>
<listitem>
<para>
- Fix problem when setting <varname>LC_MESSAGES</> on
- <application>MSVC</>-built systems (Hiroshi Inoue, Hiroshi
+ Fix problem when setting <varname>LC_MESSAGES</varname> on
+ <application>MSVC</application>-built systems (Hiroshi Inoue, Hiroshi
Saito, Magnus) bjm: details?
</para>
</listitem>
@@ -2867,34 +2904,35 @@
<listitem>
<para>
- Improve <application>gettext</> support to allow better translation
+ Improve <application>gettext</application> support to allow better translation
of plurals (Peter)
</para>
</listitem>
<listitem>
<para>
- Add <application>DTrace</> probes (Robert Lor)
+ Add <application>DTrace</application> probes (Robert Lor)
</para>
</listitem>
<listitem>
<para>
- Add <application>DTrace</> support on <application>Mac OS X
- Leopard</> (Robert Lor)
+ Add <application>DTrace</application> support on <application>Mac OS X
+ Leopard</application> (Robert Lor)
</para>
</listitem>
<listitem>
<para>
- Add new <type>cstring</> to <type>text</> conversion functions
+ Add new <type>cstring</type> to <type>text</type> conversion functions
(Brendan Jurd, Tom)
</para>
</listitem>
<listitem>
<para>
- Add a <structfield>relistemp</> column to <structname>pg_class</>
+ Add a <structfield>relistemp</structfield> column to
+ <structname>pg_class</structname>
to ease identification of temporary tables (Tom)
</para>
</listitem>
@@ -2907,7 +2945,7 @@
<listitem>
<para>
- Make <type>name</> char-aligned (Tom)
+ Make <type>name</type> char-aligned (Tom)
</para>
</listitem>
@@ -2927,33 +2965,36 @@
<listitem>
<para>
- Add <function>shmem_startup_hook()</> for custom shared memory
+ Add <function>shmem_startup_hook()</function> for custom shared memory
requirements (Tom)
</para>
</listitem>
<listitem>
<para>
- Replace <literal>pg_class</> column <literal>reltriggers</>
- with boolean <literal>relhastriggers</> (Simon)
+ Replace <literal>pg_class</literal> column
+ <literal>reltriggers</literal>
+ with boolean <literal>relhastriggers</literal> (Simon)
</para>
<para>
- Also remove unused <literal>pg_class</> columns <literal>relukeys</>,
- <literal>relfkeys</>, and <literal>relrefs</>.
+ Also remove unused <literal>pg_class</literal> columns
+ <literal>relukeys</literal>,
+ <literal>relfkeys</literal>, and <literal>relrefs</literal>.
</para>
</listitem>
<listitem>
<para>
- Move <acronym>SQL</>-command manual pages from the <filename>manl</>
- (man-el) section to <filename>man7</> (Peter)
+ Move <acronym>SQL</acronym>-command manual pages from the
+ <filename>manl</filename>
+ (man-el) section to <filename>man7</filename> (Peter)
</para>
</listitem>
<listitem>
<para>
- Move platform <acronym>FAQ</>s into the main documentation
+ Move platform <acronym>FAQ</acronym>s into the main documentation
(Peter)
</para>
</listitem>
@@ -2967,7 +3008,7 @@
<listitem>
<para>
- Add support for the <literal>KOI8U</> (Ukrainian) encoding
+ Add support for the <literal>KOI8U</literal> (Ukrainian) encoding
(Peter)
</para>
</listitem>
@@ -2992,21 +3033,21 @@
<listitem>
<para>
- Add query mode option to <filename>/contrib/pgbench</>
+ Add query mode option to <filename>/contrib/pgbench</filename>
(Itagaki Takahiro)
</para>
</listitem>
<listitem>
<para>
- Add duration option to <filename>/contrib/pgbench</> (Itagaki
+ Add duration option to <filename>/contrib/pgbench</filename> (Itagaki
Takahiro)
</para>
</listitem>
<listitem>
<para>
- Fix <filename>/contrib/pgstattuple</> to handle tables and
+ Fix <filename>/contrib/pgstattuple</filename> to handle tables and
indexes with over 2 billion pages (Tatsuhito Kasahara)
</para>
</listitem>
@@ -3014,7 +3055,7 @@
<listitem>
<para>
Add Levenshtein string-distance function to
- <filename>/contrib/fuzzystrmatch</> that allows the user to
+ <filename>/contrib/fuzzystrmatch</filename> that allows the user to
specify the cost of insertion, deletion, and substitution
(Volkan Yazici)
</para>
@@ -3022,36 +3063,36 @@
<listitem>
<para>
- Remove <function>dblink_current_query()</> from
- <filename>/contrib/dblink</>; it should now use
- <function>current_query()</> (Tomas Doran)
+ Remove <function>dblink_current_query()</function> from
+ <filename>/contrib/dblink</filename>; it should now use
+ <function>current_query()</function> (Tomas Doran)
</para>
</listitem>
<listitem>
<para>
- Have <filename>/contrib/ltree</> support multibyte encodings
+ Have <filename>/contrib/ltree</filename> support multibyte encodings
(laser)
</para>
</listitem>
<listitem>
<para>
- Add <filename>/contrib/btree_gin</> to allow GIN indexes to
+ Add <filename>/contrib/btree_gin</filename> to allow GIN indexes to
handle more datatypes (Oleg, Teodor)
</para>
</listitem>
<listitem>
<para>
- Add <filename>/contrib/citext</> as a case-insensitive,
+ Add <filename>/contrib/citext</filename> as a case-insensitive,
multibyte-aware text data type (David Wheeler)
</para>
</listitem>
<listitem>
<para>
- Make sure <filename>/contrib/dblink</> uses a password supplied
+ Make sure <filename>/contrib/dblink</filename> uses a password supplied
by the user, and not accidentally from the server's .pgpass file
(Joe Conway)
</para>
@@ -3063,57 +3104,59 @@
<listitem>
<para>
- Add <function>fsm_page_contents()</>
- to<filename>/contrib/pageinspect</> (Heikki)
+ Add <function>fsm_page_contents()</function>
+ to<filename>/contrib/pageinspect</filename> (Heikki)
</para>
<para>
- Modify <function>get_raw_page()</> to support free space map
- (<filename>*.fsm</>) files. Also update
- <filename>/contrib/pg_freespacemap</>.
+ Modify <function>get_raw_page()</function> to support free space map
+ (<filename>*.fsm</filename>) files. Also update
+ <filename>/contrib/pg_freespacemap</filename>.
</para>
</listitem>
<listitem>
<para>
- Add support for multibyte encodings to <filename>/contrib/pg_trgm</>
+ Add support for multibyte encodings to
+ <filename>/contrib/pg_trgm</filename>
(Teodor)
</para>
</listitem>
<listitem>
<para>
- Rewrite <filename>/contrib/intagg</> to user new server-side
- functions <function>array_agg()</> and <function>unnest()</>
+ Rewrite <filename>/contrib/intagg</filename> to user new server-side
+ functions <function>array_agg()</function> and
+ <function>unnest()</function>
(Tom)
</para>
</listitem>
<listitem>
<para>
- Remove <filename>/contrib/intarray</>'s definitions of the
- <literal><@</> and <literal>@></> operators (Tom)
+ Remove <filename>/contrib/intarray</filename>'s definitions of the
+ <literal><@</literal> and <literal>@></literal> operators (Tom)
</para>
<para>
This avoids confusion with the equivalent built-in operators.
- If necessary, the <filename>/contrib/intarray</> implementations
- are still available under their historical names <literal>@</>
- and <literal>~</>.
+ If necessary, the <filename>/contrib/intarray</filename> implementations
+ are still available under their historical names <literal>@</literal>
+ and <literal>~</literal>.
</para>
</listitem>
<listitem>
<para>
- Add <filename>/contrib/auto_explain</> to automatically run
- <command>EXPLAIN</> on queries exceeding a specified duration
+ Add <filename>/contrib/auto_explain</filename> to automatically run
+ <command>EXPLAIN</command> on queries exceeding a specified duration
(Itagaki Takahiro, Tom)
</para>
</listitem>
<listitem>
<para>
- Add <filename>/contrib/pg_stat_statements</> for server-wide
+ Add <filename>/contrib/pg_stat_statements</filename> for server-wide
tracking of statement execution statistics (Itagaki Takahiro)
</para>
</listitem>
Modified: traduc/trunk/postgresql/runtime.xml
===================================================================
--- traduc/trunk/postgresql/runtime.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/runtime.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -195,7 +195,7 @@
serveur <acronym>NFS</acronym> peuvent poser des soucis de fiabilité. Si
possible, montez les systèmes de fichiers <acronym>NFS</acronym> en
synchrone (autrement dit sans cache) pour éviter cela. Also, soft-mounting
- <acronym>NFS</> is not recommended. Les
+ <acronym>NFS</acronym> is not recommended. Les
<acronym>SAN</acronym> utilisent un protocole de communication bas-niveau
plutôt que <acronym>NFS</acronym>.
</para>
@@ -1058,51 +1058,51 @@
</variablelist>
<table id="shared-memory-parameters">
- <title><productname>PostgreSQL</productname> shared memory usage</>
+ <title><productname>PostgreSQL</productname> shared memory usage</title>
<tgroup cols="2">
<colspec colnum="1" colwidth="0.5*"/>
<colspec colnum="2" colwidth="1.5*"/>
<thead>
<row>
- <entry>Usage</>
- <entry>Approximate shared memory bytes required (as of 8.3)</>
+ <entry>Usage</entry>
+ <entry>Approximate shared memory bytes required (as of 8.3)</entry>
</row>
</thead>
<tbody>
<row>
- <entry>Connections</>
+ <entry>Connections</entry>
<entry>(1800 + 270 * <xref
- linkend="guc-max-locks-per-transaction">) * <xref
- linkend="guc-max-connections"></entry>
+ linkend="guc-max-locks-per-transaction"/>) * <xref
+ linkend="guc-max-connections"/></entry>
</row>
<row>
- <entry>Autovacuum workers</>
+ <entry>Autovacuum workers</entry>
<entry>(1800 + 270 * <xref
- linkend="guc-max-locks-per-transaction">) * <xref
- linkend="guc-autovacuum-max-workers"></entry>
+ linkend="guc-max-locks-per-transaction"/>) * <xref
+ linkend="guc-autovacuum-max-workers"/></entry>
</row>
<row>
- <entry>Prepared transactions</>
+ <entry>Prepared transactions</entry>
<entry>(770 + 270 * <xref
- linkend="guc-max-locks-per-transaction">) * <xref linkend="guc-max-prepared-transactions"></entry>
+ linkend="guc-max-locks-per-transaction"/>) * <xref linkend="guc-max-prepared-transactions"/></entry>
</row>
<row>
- <entry>Shared disk buffers</>
- <entry>(<xref linkend="guc-block-size"> + 208) * <xref linkend="guc-shared-buffers"></entry>
+ <entry>Shared disk buffers</entry>
+ <entry>(<xref linkend="guc-block-size"/> + 208) * <xref linkend="guc-shared-buffers"/></entry>
</row>
<row>
- <entry>WAL buffers</>
- <entry>(<xref linkend="guc-wal-block-size"> + 8) * <xref linkend="guc-wal-buffers"></entry>
+ <entry>WAL buffers</entry>
+ <entry>(<xref linkend="guc-wal-block-size"/> + 8) * <xref linkend="guc-wal-buffers"/></entry>
</row>
<row>
- <entry>Fixed space requirements</>
+ <entry>Fixed space requirements</entry>
<entry>770 kB</entry>
</row>
</tbody>
@@ -1350,9 +1350,9 @@
<para>
To terminate an individual session while allowing other sessions to
- continue, use <function>pg_terminate_backend()</> (see <xref
- linkend="functions-admin-signal-table">) or send a
- <systemitem>SIGTERM</> signal to the child process associated with
+ continue, use <function>pg_terminate_backend()</function> (see <xref
+ linkend="functions-admin-signal-table"/>) or send a
+ <systemitem>SIGTERM</systemitem> signal to the child process associated with
the session.
</para>
</sect1>
@@ -1400,9 +1400,9 @@
<filename>server.key</filename>, et pour le certificat,
<filename>server.crt</filename> (<xref linkend="ssl-tcp"/>). Le client TCP
doit se connecter en utilisant <literal>sslmode='require'</literal>,
- specify <literal>sslverify='cn'</>
- or <literal>sslverify='cert'</> and have the required certificate
- files present (<xref linkend="libpq-connect">).
+ specify <literal>sslverify='cn'</literal>
+ or <literal>sslverify='cert'</literal> and have the required certificate
+ files present (<xref linkend="libpq-connect"/>).
</para>
</sect1>
@@ -1653,16 +1653,16 @@
</para>
<para>
- The <literal>clientcert</literal> option in <filename>pg_hba.conf</>
+ The <literal>clientcert</literal> option in <filename>pg_hba.conf</filename>
is available for all authentication methods, but only for rows
- specified as <literal>hostssl</>. Unless specified, the default is
+ specified as <literal>hostssl</literal>. Unless specified, the default is
not to verify the client certificate.
</para>
<para>
- You can use the authentication method <literal>cert</> to use the
+ You can use the authentication method <literal>cert</literal> to use the
client certificate for authenticating users. See
- <xref linkend="auth-cert"> for details.
+ <xref linkend="auth-cert"/> for details.
</para>
</sect2>
@@ -1767,7 +1767,7 @@
<acronym>CAs</acronym> global ou un local) devra être utilisé lorsque
le serveur sera en production pour que le client puisse vérifier
l'identité du serveur. If all the clients
- are local to the organization, using a local <acronym>CA</> is
+ are local to the organization, using a local <acronym>CA</acronym> is
recommended.
</para>
Modified: traduc/trunk/postgresql/sources.xml
===================================================================
--- traduc/trunk/postgresql/sources.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/sources.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -22,12 +22,12 @@
Les règles de disposition (positionnement des
parenthèses, etc) suivent les conventions BSD.
In
- particular, curly braces for the controlled blocks of <literal>if</>,
- <literal>while</>, <literal>switch</>, etc go on their own lines.
+ particular, curly braces for the controlled blocks of <literal>if</literal>,
+ <literal>while</literal>, <literal>switch</literal>, etc go on their own lines.
</para>
<para>
- Do not use C++ style comments (<literal>//</> comments). Strict ANSI C
+ Do not use C++ style comments (<literal>//</literal> comments). Strict ANSI C
compilers do not accept them. For the same reason, do not use C++
extensions such as declaring new variables mid-block.
</para>
@@ -41,7 +41,7 @@
*/
</programlisting>
Note that comment blocks that begin in column 1 will be preserved as-is
- by <application>pgindent</>, but it will re-flow indented comment blocks
+ by <application>pgindent</application>, but it will re-flow indented comment blocks
as though they were plain text. If you want to preserve the line breaks
in an indented block, add dashes like this:
<programlisting>
@@ -215,9 +215,9 @@
<listitem>
<para>
<function>errdetail_log(const char *msg, ...)</function> is the same as
- <function>errdetail</> except that this string goes only to the server
- log, never to the client. If both <function>errdetail</> and
- <function>errdetail_log</> are used then one string goes to the client
+ <function>errdetail</function> except that this string goes only to the server
+ log, never to the client. If both <function>errdetail</function> and
+ <function>errdetail_log</function> are used then one string goes to the client
and the other to the log. This is useful for error details that are
too security-sensitive or too bulky to include in the report
sent to the client.
Modified: traduc/trunk/postgresql/spi.xml
===================================================================
--- traduc/trunk/postgresql/spi.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/spi.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -713,7 +713,7 @@
<para>
<function>SPI_execute_with_args</function> executes a command that might
include references to externally supplied parameters. The command text
- refers to a parameter as <literal>$<replaceable>n</></literal>, and
+ refers to a parameter as <literal>$<replaceable>n</replaceable></literal>, and
the call specifies data types and values for each such symbol.
<parameter>read_only</parameter> and <parameter>count</parameter> have
the same interpretation as in <function>SPI_execute</function>.
@@ -727,7 +727,7 @@
</para>
<para>
- Similar results can be achieved with <function>SPI_prepare</> followed by
+ Similar results can be achieved with <function>SPI_prepare</function> followed by
<function>SPI_execute_plan</function>; however, when using this function
the query plan is customized to the specific parameter values provided.
For one-time query execution, this function should be preferred.
@@ -754,7 +754,7 @@
<term><literal>int <parameter>nargs</parameter></literal></term>
<listitem>
<para>
- number of input parameters (<literal>$1</>, <literal>$2</>, etc.)
+ number of input parameters (<literal>$1</literal>, <literal>$2</literal>, etc.)
</para>
</listitem>
</varlistentry>
@@ -797,7 +797,7 @@
<term><literal>bool <parameter>read_only</parameter></literal></term>
<listitem>
<para>
- <literal>true</> for read-only execution
+ <literal>true</literal> for read-only execution
</para>
</listitem>
</varlistentry>
@@ -1669,7 +1669,7 @@
<term><literal>int <parameter>nargs</parameter></literal></term>
<listitem>
<para>
- number of input parameters (<literal>$1</>, <literal>$2</>, etc.)
+ number of input parameters (<literal>$1</literal>, <literal>$2</literal>, etc.)
</para>
</listitem>
</varlistentry>
@@ -1712,7 +1712,7 @@
<term><literal>bool <parameter>read_only</parameter></literal></term>
<listitem>
<para>
- <literal>true</> for read-only execution
+ <literal>true</literal> for read-only execution
</para>
</listitem>
</varlistentry>
@@ -1733,7 +1733,7 @@
<para>
Pointer to portal containing the cursor. Note there is no error
- return convention; any error will be reported via <function>elog</>.
+ return convention; any error will be reported via <function>elog</function>.
</para>
</refsect1>
</refentry>
Modified: traduc/trunk/postgresql/storage.xml
===================================================================
--- traduc/trunk/postgresql/storage.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/storage.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -87,7 +87,7 @@
</row>
<row>
- <entry><filename>pg_stat_tmp</></entry>
+ <entry><filename>pg_stat_tmp</filename></entry>
<entry>Subdirectory containing temporary files for the statistics
subsystem</entry>
</row>
@@ -143,10 +143,10 @@
Chaque table et index sont stockés dans un fichier séparé, nommé d'après le
numéro <firstterm>filenode</firstterm> de la table ou de l'index, lequel se trouve dans
<structname>pg_class</structname>.<structfield>relfilenode</structfield>. In addition to the
-main file (aka. main fork), a <firstterm>free space map</> (see
-<xref linkend="storage-fsm">) that stores information about free space
+main file (aka. main fork), a <firstterm>free space map</firstterm> (see
+<xref linkend="storage-fsm"/>) that stores information about free space
available in the relation, is stored in a file named after the filenode
-number, with the the <literal>_fsm</> suffix.
+number, with the the <literal>_fsm</literal> suffix.
</para>
<caution>
@@ -168,7 +168,7 @@
sur les tailles des fichiers.
(Actually, 1 GB is just the default segment size. The segment size can be
adjusted using the configuration option <option>--with-segsize</option>
-when building <productname>PostgreSQL</>.)
+when building <productname>PostgreSQL</productname>.)
Le contenu des tables et des index est discuté plus
en détails dans <xref linkend="storage-page-layout"/>.
</para>
@@ -409,36 +409,36 @@
<indexterm>
<primary>Free Space Map</primary>
</indexterm>
- <indexterm><primary>FSM</><see>Free Space Map</></indexterm>
+ <indexterm><primary>FSM</primary><see>Free Space Map</see></indexterm>
<para>
A Free Space Map is stored with every heap and index relation, except for
hash indexes, to keep track of available space in the relation. It's stored
along the main relation data, in a separate FSM relation fork, named after
-relfilenode of the relation, but with a <literal>_fsm</> suffix. For example,
+relfilenode of the relation, but with a <literal>_fsm</literal> suffix. For example,
if the relfilenode of a relation is 12345, the FSM is stored in a file called
-<filename>12345_fsm</>, in the same directory as the main relation file.
+<filename>12345_fsm</filename>, in the same directory as the main relation file.
</para>
<para>
-The Free Space Map is organized as a tree of <acronym>FSM</> pages. The
-bottom level <acronym>FSM</> pages stores the free space available on every
+The Free Space Map is organized as a tree of <acronym>FSM</acronym> pages. The
+bottom level <acronym>FSM</acronym> pages stores the free space available on every
heap (or index) page, using one byte to represent each heap page. The upper
levels aggregate information from the lower levels.
</para>
<para>
-Within each <acronym>FSM</> page is a binary tree, stored in an array with
+Within each <acronym>FSM</acronym> page is a binary tree, stored in an array with
one byte per node. Each leaf node represents a heap page, or a lower level
-<acronym>FSM</> page. In each non-leaf node, the higher of its children's
+<acronym>FSM</acronym> page. In each non-leaf node, the higher of its children's
values is stored. The maximum value in the leaf nodes is therefore stored
at the root.
</para>
<para>
-See <filename>src/backend/storage/freespace/README</> for more details on
-how the <acronym>FSM</> is structured, and how it's updated and searched.
-<xref linkend="pgfreespacemap"> contrib module can be used to view the
+See <filename>src/backend/storage/freespace/README</filename> for more details on
+how the <acronym>FSM</acronym> is structured, and how it's updated and searched.
+<xref linkend="pgfreespacemap"/> contrib module can be used to view the
information stored in free space maps.
</para>
Modified: traduc/trunk/postgresql/syntax.xml
===================================================================
--- traduc/trunk/postgresql/syntax.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/syntax.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -332,7 +332,7 @@
(<literal>\</literal>) comme une séquence type C
d'<firstterm>échappement d'antislash</firstterm> avec laquelle la combinaison
d'antislash et du (ou des) caractère(s) suivant représente une valeur
- spéciale, as shown in <xref linkend="sql-backslash-table">.
+ spéciale, as shown in <xref linkend="sql-backslash-table"/>.
</para>
<table id="sql-backslash-table">
@@ -340,7 +340,7 @@
<tgroup cols="2">
<thead>
<row>
- <entry>Backslash Escape Sequence</>
+ <entry>Backslash Escape Sequence</entry>
<entry>Interpretation</entry>
</row>
</thead>
@@ -399,7 +399,7 @@
It is your responsibility that the byte sequences you create are
valid characters in the server character set encoding. When the
server encoding is UTF-8, then the alternative Unicode escape
- syntax, explained in <xref linkend="sql-syntax-strings-uescape">,
+ syntax, explained in <xref linkend="sql-syntax-strings-uescape"/>,
should be used instead. (The alternative would be doing the
UTF-8 encoding by hand and writing out the bytes, which would be
very cumbersome.)
@@ -1375,8 +1375,8 @@
</programlisting>
The parentheses are required here to show that
- <structfield>compositecol</> is a column name not a table name,
- or that <structname>mytable</> is a table name not a schema name
+ <structfield>compositecol</structfield> is a column name not a table name,
+ or that <structname>mytable</structname> is a table name not a schema name
in the second case.
</para>
</sect2>
@@ -1543,8 +1543,8 @@
to grouping of the selected rows into a single output row — each
row remains separate in the query output. However the window function
is able to scan all the rows that would be part of the current row's
- group according to the grouping specification (<literal>PARTITION BY</>
- list) of the window function call.
+ group according to the grouping specification (<literal>PARTITION
+ BY</literal> list) of the window function call.
The syntax of a window function call is one of the following:
<synopsis>
@@ -1574,66 +1574,67 @@
Here, <replaceable>expression</replaceable> represents any value
expression that does not itself contain window function calls.
- The <literal>PARTITION BY</> and <literal>ORDER BY</> lists have
- essentially the same syntax and semantics as <literal>GROUP BY</>
- and <literal>ORDER BY</> clauses of the whole query.
+ The <literal>PARTITION BY</literal> and <literal>ORDER BY</literal> lists have
+ essentially the same syntax and semantics as <literal>GROUP BY</literal>
+ and <literal>ORDER BY</literal> clauses of the whole query.
<replaceable>window_name</replaceable> is a reference to a named window
specification defined in the query's <literal>WINDOW</literal> clause.
Named window specifications are usually referenced with just
- <literal>OVER</> <replaceable>window_name</replaceable>, but it is
+ <literal>OVER</literal> <replaceable>window_name</replaceable>, but it is
also possible to write a window name inside the parentheses and then
optionally supply an ordering clause and/or frame clause (the referenced
window must lack these clauses, if they are supplied here).
This latter syntax follows the same rules as modifying an existing
window name within the <literal>WINDOW</literal> clause; see the
- <xref linkend="sql-select" endterm="sql-select-title"> reference
+ <xref linkend="sql-select" endterm="sql-select-title"/> reference
page for details.
</para>
<para>
The <replaceable class="parameter">frame_clause</replaceable> specifies
- the set of rows constituting the <firstterm>window frame</>, for those
+ the set of rows constituting the <firstterm>window frame</firstterm>, for those
window functions that act on the frame instead of the whole partition.
- The default framing option is <literal>RANGE UNBOUNDED PRECEDING</>,
+ The default framing option is <literal>RANGE UNBOUNDED PRECEDING</literal>,
which is the same as <literal>RANGE BETWEEN UNBOUNDED PRECEDING AND
- CURRENT ROW</>; it selects rows up through the current row's last
- peer in the <literal>ORDER BY</> ordering (which means all rows if
- there is no <literal>ORDER BY</>). The options
- <literal>RANGE BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</> and
- <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</>
+ CURRENT ROW</literal>; it selects rows up through the current row's last
+ peer in the <literal>ORDER BY</literal> ordering (which means all rows if
+ there is no <literal>ORDER BY</literal>). The options
+ <literal>RANGE BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED
+ FOLLOWING</literal> and
+ <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</literal>
are also equivalent: they always select all rows in the partition.
- Lastly, <literal>ROWS UNBOUNDED PRECEDING</> or its verbose equivalent
- <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW</> select
+ Lastly, <literal>ROWS UNBOUNDED PRECEDING</literal> or its verbose equivalent
+ <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW</literal> select
all rows up through the current row (regardless of duplicates).
Beware that this option can produce implementation-dependent results
- if the <literal>ORDER BY</> ordering does not order the rows uniquely.
+ if the <literal>ORDER BY</literal> ordering does not order the rows uniquely.
</para>
<para>
The built-in window functions are described in <xref
- linkend="functions-window-table">. Other window functions can be added by
+ linkend="functions-window-table"/>. Other window functions can be added by
the user. Also, any built-in or user-defined aggregate function can be
used as a window function.
</para>
<para>
- The syntaxes using <literal>*</> are used for calling parameter-less
+ The syntaxes using <literal>*</literal> are used for calling parameter-less
aggregate functions as window functions, for example
- <literal>count(*) OVER (PARTITION BY x ORDER BY y)</>.
- <literal>*</> is customarily not used for non-aggregate window functions.
+ <literal>count(*) OVER (PARTITION BY x ORDER BY y)</literal>.
+ <literal>*</literal> is customarily not used for non-aggregate window functions.
Aggregate window functions, unlike normal aggregate functions, do not
- allow <literal>DISTINCT</> to be used within the function argument list.
+ allow <literal>DISTINCT</literal> to be used within the function argument list.
</para>
<para>
Window function calls are permitted only in the <literal>SELECT</literal>
- list and the <literal>ORDER BY</> clause of the query.
+ list and the <literal>ORDER BY</literal> clause of the query.
</para>
<para>
More information about window functions can be found in
- <xref linkend="tutorial-window"> and
- <xref linkend="queries-window">.
+ <xref linkend="tutorial-window"/> and
+ <xref linkend="queries-window"/>.
</para>
</sect2>
@@ -1784,7 +1785,7 @@
</programlisting>
This has the same effect as casting each expression to the array
element type individually.
- For more on casting, see <xref linkend="sql-syntax-type-casts">.
+ For more on casting, see <xref linkend="sql-syntax-type-casts"/>.
</para>
<para>
@@ -1808,7 +1809,7 @@
Comme les tableaux multidimensionnels doivent être rectangulaires, les
constructeurs internes du même niveau doivent produire des
sous-tableaux de dimensions identiques.
- Any cast applied to the outer <literal>ARRAY</> constructor propagates
+ Any cast applied to the outer <literal>ARRAY</literal> constructor propagates
automatically to all the inner constructors.
</para>
Modified: traduc/trunk/postgresql/textsearch.xml
===================================================================
--- traduc/trunk/postgresql/textsearch.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/textsearch.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -805,7 +805,7 @@
'fat' | 'rat':AB
</programlisting>
- Also, <literal>*</> can be attached to a lexeme to specify prefix matching:
+ Also, <literal>*</literal> can be attached to a lexeme to specify prefix matching:
<programlisting>
SELECT to_tsquery('supern:*A & star:A*B');
@@ -814,7 +814,7 @@
'supern':*A & 'star':*AB
</programlisting>
- Such a lexeme will match any word in a <type>tsvector</> that begins
+ Such a lexeme will match any word in a <type>tsvector</type> that begins
with the given string.
</para>
@@ -2392,11 +2392,12 @@
</para>
<para>
- The <literal>synonym</> template also has an optional parameter
- <literal>CaseSensitive</>, which defaults to <literal>false</>. When
- <literal>CaseSensitive</> is <literal>false</>, words in the synonym file
+ The <literal>synonym</literal> template also has an optional parameter
+ <literal>CaseSensitive</literal>, which defaults to
+ <literal>false</literal>. When
+ <literal>CaseSensitive</literal> is <literal>false</literal>, words in the synonym file
are folded to lower case, as are input tokens. When it is
- <literal>true</>, words and tokens are not folded to lower case,
+ <literal>true</literal>, words and tokens are not folded to lower case,
but are compared as-is.
</para>
@@ -3333,7 +3334,8 @@
<para>
Les index GIN ne sont pas à perte for standard queries, but their performance
depends logarithmically on the number of unique words.
- (However, GIN indexes store only the words (lexemes) of <type>tsvector</>
+ (However, GIN indexes store only the words (lexemes) of
+ <type>tsvector</type>
values, and not their weight labels. Thus a table row recheck is needed
when using a query that involves weights.)
</para>
@@ -3360,7 +3362,7 @@
Les index GIN sont un peu plus lents à mettre à jour que les
index GiST, but
about 10 times slower if fast-update support was disabled
- (see <xref linkend="gin-fast-update"> for details)
+ (see <xref linkend="gin-fast-update"/> for details)
</para>
</listitem>
<listitem>
Modified: traduc/trunk/postgresql/trigger.xml
===================================================================
--- traduc/trunk/postgresql/trigger.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/trigger.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -646,7 +646,7 @@
<para>
Après avoir compilé le code source (see <xref
- linkend="dfunc">), déclarez la fonction et les
+ linkend="dfunc"/>), déclarez la fonction et les
déclencheurs :
<programlisting>CREATE FUNCTION trigf() RETURNS trigger
AS '<replaceable>nomfichier</replaceable>'
Modified: traduc/trunk/postgresql/typeconv.xml
===================================================================
--- traduc/trunk/postgresql/typeconv.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/typeconv.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -177,7 +177,7 @@
categories</firstterm>, including <type>boolean</type>, <type>numeric</type>,
<type>string</type>, <type>bitstring</type>, <type>datetime</type>,
<type>timespan</type>, <type>geometric</type>, <type>network</type>, and
-user-defined. (For a list see <xref linkend="catalog-typcategory-table">;
+user-defined. (For a list see <xref linkend="catalog-typcategory-table"/>;
but note it is also possible to create custom type categories.) Within each
category there can be one or more <firstterm>preferred types</firstterm>, which
are preferentially selected when there is ambiguity. With careful selection
@@ -515,8 +515,8 @@
</step>
<step performance="optional">
<para>
-If a function is declared with a <literal>VARIADIC</> array parameter, and
-the call does not use the <literal>VARIADIC</> keyword, then the function
+If a function is declared with a <literal>VARIADIC</literal> array parameter, and
+the call does not use the <literal>VARIADIC</literal> keyword, then the function
is treated as if the array parameter were replaced by one or more occurrences
of its element type, as needed to match the call. After such expansion the
function might have effective argument types identical to some non-variadic
@@ -534,7 +534,7 @@
schema with identical parameter types in the non-defaulted positions (which is
possible if they have different sets of defaultable parameters), the system
will not be able to determine which to prefer, and so an <quote>ambiguous
-function call</> error will result if no better match to the call can be
+function call</quote> error will result if no better match to the call can be
found.
</para>
</step>
Modified: traduc/trunk/postgresql/vacuumlo.xml
===================================================================
--- traduc/trunk/postgresql/vacuumlo.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/vacuumlo.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -59,8 +59,8 @@
</varlistentry>
<varlistentry>
- <term><option>-w</></term>
- <term><option>--no-password</></term>
+ <term><option>-w</option></term>
+ <term><option>--no-password</option></term>
<listitem>
<para>
Never issue a password prompt. If the server requires password
Modified: traduc/trunk/postgresql/wal.xml
===================================================================
--- traduc/trunk/postgresql/wal.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/wal.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -162,7 +162,7 @@
causes file system <emphasis>data</emphasis> to be flushed
to disk. Fortunately, data flushing during journaling can
often be disabled with a filesystem mount option, e.g.
- <literal>data=writeback</> on a Linux ext3 file system.
+ <literal>data=writeback</literal> on a Linux ext3 file system.
Journaled file systems do improve boot speed after a crash.
</para>
</tip>
@@ -574,9 +574,10 @@
Les journaux de transaction sont stockés dans le répertoire
<filename>pg_xlog</filename> sous le répertoire de données, comme un ensemble
de fichiers, chacun d'une taille de 16 Mo généralement (but the size can be changed
- by altering the <option>--with-wal-segsize</> configure option when
+ by altering the <option>--with-wal-segsize</option> configure option when
building the server). Chaque
- fichier est divisé en pages de généralement 8 Ko (this size can be changed via the <option>--with-wal-blocksize</>
+ fichier est divisé en pages de généralement 8 Ko (this size can be
+ changed via the <option>--with-wal-blocksize</option>
configure option). Les en-têtes de
l'entrée du journal sont décrites dans
<filename>access/xlog.h</filename> ; le contenu de l'entrée dépend
@@ -622,7 +623,7 @@
point de contrôle. Parce que l'ensemble du contenu des pages de
données est sauvegardé dans le journal à la première modification de
page après un point de contrôle (assuming
- <xref linkend="guc-full-page-writes"> is not disabled), toutes les pages changées depuis
+ <xref linkend="guc-full-page-writes"/> is not disabled), toutes les pages changées depuis
le point de contrôle seront restaurées dans un état cohérent.
</para>
Modified: traduc/trunk/postgresql/xaggr.xml
===================================================================
--- traduc/trunk/postgresql/xaggr.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/xaggr.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -126,7 +126,7 @@
Dans ce cas, le type d'état effectif pour tout appel d'agrégat est le type
tableau avec comme éléments le type effectif d'entrée. The behavior of the aggregate
is to concatenate all the inputs into an array of that type.
- (Note: the built-in aggregate <function>array_agg</> provides similar
+ (Note: the built-in aggregate <function>array_agg</function> provides similar
functionality, with better performance than this definition would have.)
</para>
@@ -156,7 +156,7 @@
<para>
En fonction du <quote>contexte</quote> de l'appel, consultable
par le nœud <structname>AggState</structname> ou
- <structname>WindowAggState</>, une fonction C
+ <structname>WindowAggState</structname>, une fonction C
sait si elle est appelée en tant que
transition d'agrégat ou en tant que fonction finale. Par exemple :
<programlisting> if (fcinfo->context &&
Modified: traduc/trunk/postgresql/xfunc.xml
===================================================================
--- traduc/trunk/postgresql/xfunc.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/xfunc.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -100,7 +100,7 @@
Une fonction SQL peut être déclarée de façon à renvoyer un ensemble (set)
en spécifiant le type renvoyé par la fonction comme <literal>SETOF
<replaceable>un_type</replaceable></literal>, or equivalently by declaring it as
- <literal>RETURNS TABLE(<replaceable>columns</>)</literal>. Dans ce
+ <literal>RETURNS TABLE(<replaceable>columns</replaceable>)</literal>. Dans ce
cas, toutes les lignes de la dernière requête sont renvoyées. Des détails
supplémentaires sont donnés plus loin dans ce chapitre.
</para>
@@ -110,9 +110,9 @@
de plusieurs instructions SQL séparées par des points-virgule. Un
point-virgule après la dernière instruction est optionnel. Sauf si la
fonction déclare renvoyer <type>void</type>, la dernière instruction doit
- être un <command>SELECT</command>,
- or an <command>INSERT</>, <command>UPDATE</>, or <command>DELETE</>
- that has a <literal>RETURNING</> clause.
+ être un <command>SELECT</command>, or an <command>INSERT</command>,
+ <command>UPDATE</command>, or <command>DELETE</command>
+ that has a <literal>RETURNING</literal> clause.
</para>
<para>
@@ -125,7 +125,7 @@
placer de commandes <command>BEGIN</command>, <command>COMMIT</command>,
<command>ROLLBACK</command> ou <command>SAVEPOINT</command> dans une fonction
<acronym>SQL</acronym>). Néanmoins, la commande finale doit être un
- <command>SELECT</command> or have a <literal>RETURNING</> clause
+ <command>SELECT</command> or have a <literal>RETURNING</literal> clause
qui renvoie ce qui a été spécifié comme type
de retour de la fonction. Autrement, si vous voulez définir une fonction
SQL qui réalise des actions mais n'a pas de valeur utile à renvoyer,
@@ -252,7 +252,8 @@
</programlisting>
qui ajuste le solde et renvoie sa nouvelle valeur.
- The same thing could be done in one command using <literal>RETURNING</>:
+ The same thing could be done in one command using
+ <literal>RETURNING</literal>:
<programlisting>
CREATE FUNCTION tf1 (integer, numeric) RETURNS numeric AS $$
@@ -479,7 +480,7 @@
</sect2>
<sect2 id="xfunc-output-parameters">
- <title>Fonctions <acronym>SQL</> avec des paramètres en sortie</title>
+ <title>Fonctions <acronym>SQL</acronym> avec des paramètres en sortie</title>
<indexterm>
<primary>fonction</primary>
@@ -550,18 +551,19 @@
<para>
Les paramètres peuvent être marqués comme <literal>IN</literal> (par défaut),
- <literal>OUT</literal> ou <literal>INOUT</literal>, or <literal>VARIADIC</>.
+ <literal>OUT</literal> ou <literal>INOUT</literal>, or
+<literal>VARIADIC</literal>.
Un paramètre <literal>INOUT</literal>
sert à la fois de paramètre en entrée (il fait partie de la liste
d'arguments en appel) et comme paramètre de sortie (il fait partie du
type d'enregistrement résultat).
- <literal>VARIADIC</> parameters are input parameters, but are treated
+ <literal>VARIADIC</literal> parameters are input parameters, but are treated
specially as described next.
</para>
</sect2>
<sect2 id="xfunc-sql-variadic-functions">
- <title><acronym>SQL</> Functions with Variable Numbers of Arguments</title>
+ <title><acronym>SQL</acronym> Functions with Variable Numbers of Arguments</title>
<indexterm>
<primary>function</primary>
@@ -574,10 +576,10 @@
<para>
<acronym>SQL</acronym> functions can be declared to accept
- variable numbers of arguments, so long as all the <quote>optional</>
+ variable numbers of arguments, so long as all the <quote>optional</quote>
arguments are of the same data type. The optional arguments will be
passed to the function as an array. The function is declared by
- marking the last parameter as <literal>VARIADIC</>; this parameter
+ marking the last parameter as <literal>VARIADIC</literal>; this parameter
must be declared as being of an array type. For example:
<screen>
@@ -593,7 +595,7 @@
</screen>
Effectively, all the actual arguments at or beyond the
- <literal>VARIADIC</> position are gathered up into a one-dimensional
+ <literal>VARIADIC</literal> position are gathered up into a one-dimensional
array, as if you had written
<screen>
@@ -602,7 +604,7 @@
You can't actually write that, though — or at least, it will
not match this function definition. A parameter marked
- <literal>VARIADIC</> matches one or more occurrences of its element
+ <literal>VARIADIC</literal> matches one or more occurrences of its element
type, not of its own type.
</para>
@@ -610,7 +612,7 @@
Sometimes it is useful to be able to pass an already-constructed array
to a variadic function; this is particularly handy when one variadic
function wants to pass on its array parameter to another one. You can
- do that by specifying <literal>VARIADIC</> in the call:
+ do that by specifying <literal>VARIADIC</literal> in the call:
<screen>
SELECT mleast(VARIADIC ARRAY[10, -1, 5, 4.4]);
@@ -618,13 +620,13 @@
This prevents expansion of the function's variadic parameter into its
element type, thereby allowing the array argument value to match
- normally. <literal>VARIADIC</> can only be attached to the last
+ normally. <literal>VARIADIC</literal> can only be attached to the last
actual argument of a function call.
</para>
</sect2>
<sect2 id="xfunc-sql-parameter-defaults">
- <title><acronym>SQL</> Functions with Default Values for Arguments</title>
+ <title><acronym>SQL</acronym> Functions with Default Values for Arguments</title>
<indexterm>
<primary>function</primary>
@@ -825,11 +827,12 @@
<note>
<para>
- If a function's last command is <command>INSERT</>, <command>UPDATE</>,
- or <command>DELETE</> with <literal>RETURNING</>, that command will
+ If a function's last command is <command>INSERT</command>,
+ <command>UPDATE</command>, or <command>DELETE</command> with
+ <literal>RETURNING</literal>, that command will
always be executed to completion, even if the function is not declared
- with <literal>SETOF</> or the calling query does not fetch all the
- result rows. Any extra rows produced by the <literal>RETURNING</>
+ with <literal>SETOF</literal> or the calling query does not fetch all the
+ result rows. Any extra rows produced by the <literal>RETURNING</literal>
clause are silently dropped, but the commanded table modifications
still happen (and are all completed before returning from the function).
</para>
@@ -837,7 +840,7 @@
</sect2>
<sect2 id="xfunc-sql-functions-returning-table">
- <title><acronym>SQL</acronym> Functions Returning <literal>TABLE</></title>
+ <title><acronym>SQL</acronym> Functions Returning <literal>TABLE</literal></title>
<indexterm>
<primary>function</primary>
@@ -847,12 +850,12 @@
<para>
There is another way to declare a function as returning a set,
which is to use the syntax
- <literal>RETURNS TABLE(<replaceable>columns</>)</literal>.
- This is equivalent to using one or more <literal>OUT</> parameters plus
- marking the function as returning <literal>SETOF record</> (or
- <literal>SETOF</> a single output parameter's type, as appropriate).
+ <literal>RETURNS TABLE(<replaceable>columns</replaceable>)</literal>.
+ This is equivalent to using one or more <literal>OUT</literal> parameters plus
+ marking the function as returning <literal>SETOF record</literal> (or
+ <literal>SETOF</literal> a single output parameter's type, as appropriate).
This notation is specified in recent versions of the SQL standard, and
- thus may be more portable than using <literal>SETOF</>.
+ thus may be more portable than using <literal>SETOF</literal>.
</para>
<para>
@@ -865,9 +868,10 @@
$$ LANGUAGE SQL;
</programlisting>
- It is not allowed to use explicit <literal>OUT</> or <literal>INOUT</>
- parameters with the <literal>RETURNS TABLE</> notation — you must
- put all the output columns in the <literal>TABLE</> list.
+ It is not allowed to use explicit <literal>OUT</literal> or
+ <literal>INOUT</literal>
+ parameters with the <literal>RETURNS TABLE</literal> notation — you must
+ put all the output columns in the <literal>TABLE</literal> list.
</para>
</sect2>
@@ -1024,10 +1028,10 @@
<para>
Another possible conflict is between variadic and non-variadic functions.
- For instance, it is possible to create both <literal>foo(numeric)</> and
- <literal>foo(VARIADIC numeric[])</>. In this case it is unclear which one
+ For instance, it is possible to create both <literal>foo(numeric)</literal> and
+ <literal>foo(VARIADIC numeric[])</literal>. In this case it is unclear which one
should be matched to a call providing a single numeric argument, such as
- <literal>foo(10.1)</>. The rule is that the function appearing
+ <literal>foo(10.1)</literal>. The rule is that the function appearing
earlier in the search path is used, or if the two functions are in the
same schema, the non-variadic one is preferred.
</para>
@@ -3164,16 +3168,16 @@
<para>
There is a variant of polymorphism that is only available to C-language
functions: they can be declared to take parameters of type
- <literal>"any"</>. (Note that this type name must be double-quoted,
+ <literal>"any"</literal>. (Note that this type name must be double-quoted,
since it's also a SQL reserved word.) This works like
- <type>anyelement</> except that it does not constrain different
- <literal>"any"</> arguments to be the same type, nor do they help
+ <type>anyelement</type> except that it does not constrain different
+ <literal>"any"</literal> arguments to be the same type, nor do they help
determine the function's result type. A C-language function can also
- declare its final parameter to be <literal>VARIADIC "any"</>. This will
+ declare its final parameter to be <literal>VARIADIC "any"</literal>. This will
match one or more actual arguments of any type (not necessarily the same
- type). These arguments will <emphasis>not</> be gathered into an array
+ type). These arguments will <emphasis>not</emphasis> be gathered into an array
as happens with normal variadic functions; they will just be passed to
- the function separately. The <function>PG_NARGS()</> macro and the
+ the function separately. The <function>PG_NARGS()</function> macro and the
methods described above must be used to determine the number of actual
arguments and their types when using this feature.
</para>
Modified: traduc/trunk/postgresql/xindex.xml
===================================================================
--- traduc/trunk/postgresql/xindex.xml 2009-04-16 15:29:44 UTC (rev 1296)
+++ traduc/trunk/postgresql/xindex.xml 2009-04-16 16:18:33 UTC (rev 1297)
@@ -956,7 +956,7 @@
l'index pour trouver des objets dont les rectangles limites chevauchent les
limites de l'objet cible. Dans ce cas, l'index est dit être à perte
pour l'opérateur. Lossy index searches are implemented by having the index
- method return a <firstterm>recheck</> flag when a row might or might
+ method return a <firstterm>recheck</firstterm> flag when a row might or might
not really satisfy the query condition. The core system will then
test the original query condition on the retrieved row to see whether
it should be returned as a valid match. This approach works if
More information about the Trad
mailing list