Changeset 412

Show
Ignore:
Timestamp:
10/07/06 15:54:22 (2 years ago)
Author:
gleu
Message:

Nombreuses corrections pour que l'ensemble de documents soit valide.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • traduc/trunk/manuel/backup.xml

    r411 r412  
    161161   <para> 
    162162    After restoring a backup, it is wise to run <xref 
    163     linkend="sql-analyze" endterm="sql-analyze-title"> on each 
     163    linkend="sql-analyze" endterm="sql-analyze-title"/> on each 
    164164    database so the query optimizer has useful statistics. An easy way 
    165165    to do this is to run <command>vacuumdb -a -z</command>; this is 
     
    619619    of a transaction and its safe recording in archive storage.  To put 
    620620    a limit on how old unarchived data can be, you can set 
    621     <xref linkend="guc-archive-timeout"> to force the server to switch 
     621    <xref linkend="guc-archive-timeout"/> to force the server to switch 
    622622    to a new WAL segment file at least that often.  Note that archived 
    623623    files that are ended early due to a forced switch are still the same 
     
    633633    just-finished transaction is archived immediately.  Other utility 
    634634    functions related to WAL management are listed in <xref 
    635     linkend="functions-admin-backup-table">. 
     635    linkend="functions-admin-backup-table"/>. 
    636636   </para> 
    637637  </sect2> 
     
    14011401<programlisting> 
    14021402triggered = false; 
    1403 while (!NextWALFileReady() && !triggered) 
     1403while (!NextWALFileReady() &amp;&amp; !triggered) 
    14041404{ 
    14051405    sleep(100000L);         // wait for ~0.1 sec 
     
    14511451       Set up Continuous Archiving from the Primary to a WAL archive located 
    14521452       in a directory on the Standby Server. Ensure that both <xref 
    1453        linkend="guc-archive-command"> and <xref linkend="guc-archive-timeout"
    1454        are set. (See <xref linkend="backup-archiving-wal">) 
     1453       linkend="guc-archive-command"/> and <xref linkend="guc-archive-timeout"/
     1454       are set. (See <xref linkend="backup-archiving-wal"/>) 
    14551455      </para> 
    14561456     </listitem> 
     
    14581458      <para> 
    14591459       Make a Base Backup of the Primary Server. (See <xref 
    1460        linkend="backup-base-backup">) 
     1460       linkend="backup-base-backup"/>) 
    14611461      </para> 
    14621462     </listitem> 
     
    14651465       Begin recovery on the Standby Server from the local WAL archive, 
    14661466       using a recovery.conf that specifies a restore_command that waits as 
    1467        described previously. (See <xref linkend="backup-pitr-recovery">) 
     1467       described previously. (See <xref linkend="backup-pitr-recovery"/>) 
    14681468      </para> 
    14691469     </listitem> 
     
    15521552    possible to implement record-based Log Shipping using the 
    15531553    <function>pg_xlogfile_name_offset</function> function (see <xref 
    1554     linkend="functions-admin">), though this requires custom 
     1554    linkend="functions-admin"/>), though this requires custom 
    15551555    development. 
    15561556   </para> 
  • traduc/trunk/manuel/catalogs.xml

    r398 r412  
    40514051   <title><structname>pg_shdescription</structname> Columns</title> 
    40524052 
    4053    <tgroup cols="4"/
     4053   <tgroup cols="4"
    40544054    <thead> 
    40554055     <row> 
     
    50125012    <listitem> 
    50135013     <para> 
    5014       via the <xref linkend="sql-declare" endterm="sql-declare-title"
     5014      via the <xref linkend="sql-declare" endterm="sql-declare-title"/
    50155015      statement in SQL 
    50165016     </para> 
     
    50205020     <para> 
    50215021      via the Bind message in the frontend/backend protocol, as 
    5022       described in <xref linkend="protocol-flow-ext-query"
     5022      described in <xref linkend="protocol-flow-ext-query"/
    50235023     </para> 
    50245024    </listitem> 
     
    50275027     <para> 
    50285028      via the Server Programming Interface (SPI), as described in 
    5029       <xref linkend="spi-interface"
     5029      <xref linkend="spi-interface"/
    50305030     </para> 
    50315031    </listitem> 
     
    50525052   <title><structname>pg_cursors</structname> Columns</title> 
    50535053 
    5054    <tgroup cols="4"/
     5054   <tgroup cols="4"
    50555055    <thead> 
    50565056     <row> 
     
    55175517   all the prepared statements that are available in the current 
    55185518   session. See <xref linkend="sql-prepare" 
    5519    endterm="sql-prepare-title"> for more information about prepared 
     5519   endterm="sql-prepare-title"/> for more information about prepared 
    55205520   statements. 
    55215521  </para> 
     
    55265526   prepared statement is created and removed when a prepared statement 
    55275527   is released (for example, via the <xref linkend="sql-deallocate" 
    5528    endterm="sql-deallocate-title"> command). 
     5528   endterm="sql-deallocate-title"/> command). 
    55295529  </para> 
    55305530 
     
    55325532   <title><structname>pg_prepared_statements</structname> Columns</title> 
    55335533 
    5534    <tgroup cols="4"/
     5534   <tgroup cols="4"
    55355535    <thead> 
    55365536     <row> 
     
    63716371   of time zone abbreviations that are currently recognized by the datetime 
    63726372   input routines.  The contents of this view change when the 
    6373    <xref linkend="guc-timezone-abbreviations"> run-time parameter is modified. 
     6373   <xref linkend="guc-timezone-abbreviations"/> run-time parameter is modified. 
    63746374  </para> 
    63756375 
     
    63776377   <title><structname>pg_timezone_abbrevs</structname> Columns</title> 
    63786378 
    6379    <tgroup cols="3"/
     6379   <tgroup cols="3"
    63806380    <thead> 
    63816381     <row> 
     
    64296429   <title><structname>pg_timezone_names</structname> Columns</title> 
    64306430 
    6431    <tgroup cols="3"/
     6431   <tgroup cols="3"
    64326432    <thead> 
    64336433     <row> 
  • traduc/trunk/manuel/client-auth.xml

    r411 r412  
    344344         <para> 
    345345          Authenticate using LDAP to a central server. See <xref 
    346           linkend="auth-ldap"> for details. 
     346          linkend="auth-ldap"/> for details. 
    347347         </para> 
    348348        </listitem> 
  • traduc/trunk/manuel/config.xml

    r411 r412  
    15091509        Turning off this parameter does not affect use of 
    15101510        WAL archiving for point-in-time recovery (PITR) 
    1511         (see <xref linkend="continuous-archiving">). 
     1511        (see <xref linkend="continuous-archiving"/>). 
    15121512       </para> 
    15131513 
     
    45334533 
    45344534    <variablelist> 
    4535     <variablelist> 
    45364535     <varlistentry id="guc-allow-system-table-mods" xreflabel="allow_system_table_mods"> 
    45374536      <term><varname>allow_system_table_mods</varname> (<type>boolean</type>)</term> 
     
    47074706   </variablelist> 
    47084707  </sect1> 
     4708 
    47094709  <sect1 id="runtime-config-short"> 
    47104710   <title>Options courtes</title> 
  • traduc/trunk/manuel/ddl.xml

    r398 r412  
    8383  <para> 
    8484   Pour créer une table, il faut utiliser la commande bien nommée <xref 
    85    linkend="sql-createtable" endterm="sql-createtable-title">. Dans cette 
     85   linkend="sql-createtable" endterm="sql-createtable-title"/>. Dans cette 
    8686   commande, vous devez spécifier au moins le nom de la 
    8787   nouvelle table, les noms des colonnes et le type de données pour chacune des 
     
    140140   Si vous n'avez plus besoin d'une table, vous pouvez la retirer en utilisant 
    141141   la commande <xref 
    142    linkend="sql-droptable" endterm="sql-droptable-title">. Par exemple&nbsp;: 
     142   linkend="sql-droptable" endterm="sql-droptable-title"/>. Par exemple&nbsp;: 
    143143<programlisting>DROP TABLE ma_premiere_table; 
    144144DROP TABLE produits;</programlisting> 
     
    14281428   <para> 
    14291429    Pour créer un schéma, utilisez la commande <xref linkend="sql-createschema" 
    1430     endterm="sql-createschema-title">. Donnez au schéma un nom de votre choix. Par 
     1430    endterm="sql-createschema-title"/>. Donnez au schéma un nom de votre choix. Par 
    14311431    exemple&nbsp;: 
    14321432<programlisting>CREATE SCHEMA mon_schema;</programlisting> 
     
    20902090     requêtes. Ceci facilitait les erreurs et est en plus une violation du 
    20912091     standard SQL. You can get the pre-7.1 behavior by turning off the 
    2092      <xref linkend="guc-sql-inheritance"> configuration 
     2092     <xref linkend="guc-sql-inheritance"/> configuration 
    20932093     option. 
    20942094   </para> 
  • traduc/trunk/manuel/ecpg.xml

    r411 r412  
    771771   <para> 
    772772    The numeric type offers to do calculations with arbitrary precision. See 
    773     <xref linkend="datatype-numeric"> for the equivalent type in the 
     773    <xref linkend="datatype-numeric"/> for the equivalent type in the 
    774774    <productname>PostgreSQL</productname> server. Because of the arbitrary precision this 
    775775    variable needs to be able to expand and shrink dynamically. That's why you 
     
    11361136        <table> 
    11371137         <title>Valid input formats for <function>PGTYPESdate_from_asc</function></title> 
    1138          <tgroup cols="2"/
     1138         <tgroup cols="2"
    11391139          <thead> 
    11401140           <row> 
     
    15711571   <para> 
    15721572    The timestamp type in C enables your programs to deal with data of the SQL 
    1573     type timestamp. See <xref linkend="datatype-datetime"> for the equivalent 
     1573    type timestamp. See <xref linkend="datatype-datetime"/> for the equivalent 
    15741574    type in the <productname>PostgreSQL</productname> server. 
    15751575   </para> 
     
    21932193     PGTYPESdecimal_new() and PGTYPESdecimal_free(). There are a lot of other 
    21942194     functions that deal with the decimal type in the Informix compatibility 
    2195      mode described in <xref linkend="ecpg-informix-compat">. 
     2195     mode described in <xref linkend="ecpg-informix-compat"/>. 
    21962196   </para> 
    21972197   <para> 
  • traduc/trunk/manuel/func.xml

    r411 r412  
    15291529       <entry> 
    15301530        Remplace la sous-chaîne correspondant à l'expression rationnelle POSIX. 
    1531         Voir <xref linkend="functions-matching"> pour plus d'informations 
     1531        Voir <xref linkend="functions-matching"/> pour plus d'informations 
    15321532        sur la correspondance de modèle. 
    15331533       </entry> 
     
    57955795        <entry><type>timestamp with time zone</type></entry> 
    57965796        <entry>Date et heure actuelle (début de la transaction en cours)&nbsp;; 
    5797          voir <xref linkend="functions-datetime-current"
     5797         voir <xref linkend="functions-datetime-current"/
    57985798        </entry> 
    57995799        <entry></entry> 
     
    80918091   Les <firstterm>fonctions d'agrégat</firstterm> calculent une seule 
    80928092   valeur résultant d'un ensemble de valeurs en entrée. Les fonctions d'agrégats 
    8093    intégrées sont listées dans <xref linkend="functions-aggregate-table"> et 
    8094    <xref linkend="functions-aggregate-statistics-table">. Les considérations 
     8093   intégrées sont listées dans <xref linkend="functions-aggregate-table"/> et 
     8094   <xref linkend="functions-aggregate-statistics-table"/>. Les considérations 
    80958095   spéciales sur la syntaxe des fonctions 
    80968096   d'agrégat sont expliquées dans la <xref linkend="syntax-aggregates"/>. 
  • traduc/trunk/manuel/gin.xml

    r411 r412  
    106106           Returns an array of keys of the query to be executed. n contains 
    107107           the strategy number of the operation  
    108            (see <xref linkend="xindex-strategies">). 
     108           (see <xref linkend="xindex-strategies"/>). 
    109109           Depending on n, query may be different type. 
    110110      </para> 
  • traduc/trunk/manuel/indexam.xml

    r411 r412  
    277277  </para> 
    278278 
    279   </para> 
    280  
    281279  <para> 
    282280   Bien sûr, Le but d'un index est de supporter les parcours de lignes 
  • traduc/trunk/manuel/indices.xml

    r411 r412  
    265265   tsearch2 and intarray modules. For more information see <xref linkend="GIN"/>. 
    266266  </para> 
    267   </note>   
    268267 
    269268 </sect1> 
  • traduc/trunk/manuel/information_schema.xml

    r404 r412  
    492492 
    493493  <para> 
    494    See also under <xref linkend="infoschema-columns">, a similarly 
     494   See also under <xref linkend="infoschema-columns"/>, a similarly 
    495495   structured view, for further information on some of the columns. 
    496496  </para> 
  • traduc/trunk/manuel/libpq.xml

    r404 r412  
    42784278<para> 
    42794279LDAP connection parameter lookup uses the connection service file 
    4280 <filename>pg_service.conf</filename> (see <xref linkend="libpq-pgservice">). 
     4280<filename>pg_service.conf</filename> (see <xref linkend="libpq-pgservice"/>). 
    42814281A line in a <filename>pg_service.conf</filename> stanza that starts with 
    42824282<literal>ldap://</literal> will be recognized as an LDAP URL and an LDAP 
  • traduc/trunk/manuel/monitoring.xml

    r404 r412  
    163163 
    164164  <para> 
    165    The parameter <xref linkend="guc-stats-command-string"> enables monitoring 
     165   The parameter <xref linkend="guc-stats-command-string"/> enables monitoring 
    166166   of the current command being executed by any server process. 
    167167   The statistics collector subprocess need not be running to enable this 
  • traduc/trunk/manuel/ref/alter_index.xml

    r410 r412  
    207207 
    208208  <simplelist type="inline"> 
    209    <member><xref linkend="sql-createindex" endterm="sql-createindex-title"></member> 
    210    <member><xref linkend="sql-reindex" endterm="sql-reindex-title"></member> 
     209   <member><xref linkend="sql-createindex" endterm="sql-createindex-title"/></member> 
     210   <member><xref linkend="sql-reindex" endterm="sql-reindex-title"/></member> 
    211211  </simplelist> 
    212212 </refsect1> 
  • traduc/trunk/manuel/ref/copy.xml

    r410 r412  
    104104    <listitem> 
    105105     <para> 
    106       A <xref linkend="sql-select" endterm="sql-select-title"> or 
    107       <xref linkend="sql-values" endterm="sql-values-title"> command 
     106      A <xref linkend="sql-select" endterm="sql-select-title"/> or 
     107      <xref linkend="sql-values" endterm="sql-values-title"/> command 
    108108      whose results are to be copied. 
    109109      Note that parentheses are required around the query. 
  • traduc/trunk/manuel/ref/postmaster.xml

    r410 r412  
    1313 <refnamediv> 
    1414  <refname id="postmaster-ref">postmaster</refname> 
    15   <refpurpose>Serveur de bases de données <productname>PostgreSQL</productname></refpurpose> 
     15  <refpurpose>Serveur de bases de données <productname>PostgreSQL</productname></refpurpose> 
    1616 </refnamediv> 
    1717 
     
    3131 
    3232  <para> 
    33    <command>postmaster</command> est un alias obsolète de <command>postgres</command>. 
     33   <command>postmaster</command> est un alias obsolÚte de <command>postgres</command>. 
    3434  </para> 
    3535 </refsect1> 
  • traduc/trunk/manuel/ref/select.xml

    r410 r412  
    225225        doit être entouré de parenthèses et un alias 
    226226        <emphasis>doit</emphasis> lui être fourni. 
    227         Une commande <xref linkend="sql-values" endterm="sql-values-title"
     227        Une commande <xref linkend="sql-values" endterm="sql-values-title"/
    228228        peut aussi être utilisée ici. 
    229229       </para> 
  • traduc/trunk/manuel/release.xml

    r411 r412  
    870870       <para> 
    871871        Improve the length output used by 
    872         <literal>UNION</literal>/<literal>INTERSECT</literal>/<literal>EXCEPT</ltieral> 
     872       <literal>UNION</literal>/<literal>INTERSECT</literal>/<literal>EXCEPT</literal> 
    873873        (Tom) 
    874874       </para> 
     
    10501050      <listitem> 
    10511051       <para> 
    1052         Add <command>CREATE</command>/<command>ALTER ROLE PASSWORD NULL</commabnd>, 
     1052        Add <command>CREATE</command>/<command>ALTER ROLE PASSWORD NULL</command>, 
    10531053        which removes the role's password (Peter) 
    10541054       </para> 
     
    13461346 
    13471347       <para> 
    1348         The new operators are <literal>&</literal> (and), <literal>|</literal> 
     1348        The new operators are <literal>&amp;</literal> (and), <literal>|</literal> 
    13491349        (or), <literal>~</literal> (not), <literal>+</literal> <type>int8</type>, 
    13501350        <literal>-</literal> <type>int8</type>, and <type>inet</type> <literal>-</literal> 
  • traduc/trunk/manuel/syntax.xml

    r404 r412  
    15371537    which will be expanded to a list of the elements of the row value, 
    15381538    just as occurs when the <literal>.*</literal> syntax is used at the top level 
    1539     of a <command>SELECT<command/> list.  For example, if table <literal>t</literal> has 
     1539    of a <command>SELECT</command> list.  For example, if table <literal>t</literal> has 
    15401540    columns <literal>f1</literal> and <literal>f2</literal>, these are the same: 
    15411541<programlisting>