Skip to content

Commit

Permalink
Mise à jour en version 9.6.5
Browse files Browse the repository at this point in the history
  • Loading branch information
@gleu
gleu committed Sep 2, 2017
1 parent 40d94b6 commit ae67fee
Show file tree
Hide file tree
Showing 8 changed files with 842 additions and 18 deletions.
16 changes: 4 additions & 12 deletions postgresql/catalogs.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1336,12 +1336,8 @@
<entry><structfield>rolreplication</structfield></entry>
<entry><type>bool</type></entry>
<entry>
Le rôle est un rôle de réplication, c'est-à-dire qu'il peut
initier une réplication en flux (voir <xref
linkend="streaming-replication"/>) et lancer/arrêter le mode de
sauvegarde système grâce aux fonctions
<function>pg_start_backup</function> et
<function>pg_stop_backup</function>.
Le rôle est un rôle de réplication. Ce type de rôle peut initier des
connexions de réplication et créer/supprimer des slots de réplication.
</entry>
</row>

Expand Down Expand Up @@ -9343,12 +9339,8 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
<entry><type>bool</type></entry>
<entry></entry>
<entry>
Le rôle est un rôle de réplication. Autrement dit, ce rôle peut
être utilisé pour lancer une réplication en flux (voir <xref
linkend="streaming-replication"/>) et peut mettre en place le
mode de sauvegarde système en utilisant les fonctions
<function>pg_start_backup</function> et
<function>pg_stop_backup</function>.
Le rôle est un rôle de réplication. Ce type de rôle peut initier des
connexions de réplication et créer/supprimer des slots de réplication.
</entry>
</row>

Expand Down
9 changes: 4 additions & 5 deletions postgresql/ref/create_role.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -157,11 +157,10 @@
<term><literal>NOREPLICATION</literal></term>
<listitem>
<para>
Ces clauses déterminent si un rôle peut initier une réplication en flux,
ou placer le système en mode sauvegarde et l'en sortir. Un rôle ayant
l'attribut <literal>REPLICATION</literal> est un rôle très privilégié et
ne devrait être utilisé que pour la réplication.
<literal>NOREPLICATION</literal> est la valeur par défaut.
Ces clauses déterminent si un rôle est un rôle de réplication. Un rôle
doit avoir cet attribut (ou être un superutilisateur) pour être capable
de se connecter à un serveur en mode réplication (physique ou logique)
et pour être capable de créer ou supprimer des slots de réplication.
</para>
</listitem>
</varlistentry>
Expand Down
139 changes: 139 additions & 0 deletions postgresql/release-9.2.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,145 @@
<!-- doc/src/sgml/release-9.2.sgml -->
<!-- See header comment in release.sgml about typical markup -->

<sect1 id="release-9-2-23">
<title>Release 9.2.23</title>

<formalpara>
<title>Release date:</title>
<para>2017-08-31</para>
</formalpara>

<para>
This release contains a small number of fixes from 9.2.22.
For information about new features in the 9.2 major release, see
<xref linkend="release-9-2"/>.
</para>

<para>
The <productname>PostgreSQL</productname> community will stop releasing updates
for the 9.2.X release series in September 2017.
Users are encouraged to update to a newer release branch soon.
</para>

<sect2>
<title>Migration to Version 9.2.23</title>

<para>
A dump/restore is not required for those running 9.2.X.
</para>

<para>
However, if you are upgrading from a version earlier than 9.2.22,
see <xref linkend="release-9-2-22"/>.
</para>

</sect2>

<sect2>
<title>Changes</title>

<itemizedlist>

<listitem>
<para>
Show foreign tables
in <structname>information_schema</structname>.<structname>table_privileges</structname>
view (Peter Eisentraut)
</para>

<para>
All other relevant <structname>information_schema</structname> views include
foreign tables, but this one ignored them.
</para>

<para>
Since this view definition is installed by <application>initdb</application>,
merely upgrading will not fix the problem. If you need to fix this
in an existing installation, you can, as a superuser, do this
in <application>psql</application>:
<programlisting>
BEGIN;
DROP SCHEMA information_schema CASCADE;
\i <replaceable>SHAREDIR</replaceable>/information_schema.sql
COMMIT;
</programlisting>
(Run <literal>pg_config --sharedir</literal> if you're uncertain
where <replaceable>SHAREDIR</replaceable> is.) This must be repeated in each
database to be fixed.
</para>
</listitem>

<listitem>
<para>
Clean up handling of a fatal exit (e.g., due to receipt
of <systemitem>SIGTERM</systemitem>) that occurs while trying to execute
a <command>ROLLBACK</command> of a failed transaction (Tom Lane)
</para>

<para>
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
message about <quote>cannot drop active portal</quote>.
</para>
</listitem>

<listitem>
<para>
Remove assertion that could trigger during a fatal exit (Tom Lane)
</para>
</listitem>

<listitem>
<para>
Correctly identify columns that are of a range type or domain type over
a composite type or domain type being searched for (Tom Lane)
</para>

<para>
Certain <command>ALTER</command> commands that change the definition of a
composite type or domain type are supposed to fail if there are any
stored values of that type in the database, because they lack the
infrastructure needed to update or check such values. Previously,
these checks could miss relevant values that are wrapped inside range
types or sub-domains, possibly allowing the database to become
inconsistent.
</para>
</listitem>

<listitem>
<para>
Change <application>ecpg</application>'s parser to allow <literal>RETURNING</literal>
clauses without attached C variables (Michael Meskes)
</para>

<para>
This allows <application>ecpg</application> programs to contain SQL constructs
that use <literal>RETURNING</literal> internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
</para>
</listitem>

<listitem>
<para>
Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)
</para>

<para>
This fix avoids possible crashes of PL/Perl due to inconsistent
assumptions about the width of <type>time_t</type> values.
A side-effect that may be visible to extension developers is
that <literal>_USE_32BIT_TIME_T</literal> is no longer defined globally
in <productname>PostgreSQL</productname> Windows builds. This is not expected
to cause problems, because type <type>time_t</type> is not used
in any <productname>PostgreSQL</productname> API definitions.
</para>
</listitem>

</itemizedlist>

</sect2>
</sect1>

<sect1 id="release-9-2-22">
<title>Release 9.2.22</title>

Expand Down
141 changes: 141 additions & 0 deletions postgresql/release-9.3.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,147 @@
<!-- doc/src/sgml/release-9.3.sgml -->
<!-- See header comment in release.sgml about typical markup -->

<sect1 id="release-9-3-19">
<title>Release 9.3.19</title>

<formalpara>
<title>Release date:</title>
<para>2017-08-31</para>
</formalpara>

<para>
This release contains a small number of fixes from 9.3.18.
For information about new features in the 9.3 major release, see
<xref linkend="release-9-3"/>.
</para>

<sect2>
<title>Migration to Version 9.3.19</title>

<para>
A dump/restore is not required for those running 9.3.X.
</para>

<para>
However, if you are upgrading from a version earlier than 9.3.18,
see <xref linkend="release-9-3-18"/>.
</para>

</sect2>

<sect2>
<title>Changes</title>

<itemizedlist>

<listitem>
<para>
Show foreign tables
in <structname>information_schema</structname>.<structname>table_privileges</structname>
view (Peter Eisentraut)
</para>

<para>
All other relevant <structname>information_schema</structname> views include
foreign tables, but this one ignored them.
</para>

<para>
Since this view definition is installed by <application>initdb</application>,
merely upgrading will not fix the problem. If you need to fix this
in an existing installation, you can, as a superuser, do this
in <application>psql</application>:
<programlisting>
BEGIN;
DROP SCHEMA information_schema CASCADE;
\i <replaceable>SHAREDIR</replaceable>/information_schema.sql
COMMIT;
</programlisting>
(Run <literal>pg_config --sharedir</literal> if you're uncertain
where <replaceable>SHAREDIR</replaceable> is.) This must be repeated in each
database to be fixed.
</para>
</listitem>

<listitem>
<para>
Clean up handling of a fatal exit (e.g., due to receipt
of <systemitem>SIGTERM</systemitem>) that occurs while trying to execute
a <command>ROLLBACK</command> of a failed transaction (Tom Lane)
</para>

<para>
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
message about <quote>cannot drop active portal</quote>.
</para>
</listitem>

<listitem>
<para>
Remove assertion that could trigger during a fatal exit (Tom Lane)
</para>
</listitem>

<listitem>
<para>
Correctly identify columns that are of a range type or domain type over
a composite type or domain type being searched for (Tom Lane)
</para>

<para>
Certain <command>ALTER</command> commands that change the definition of a
composite type or domain type are supposed to fail if there are any
stored values of that type in the database, because they lack the
infrastructure needed to update or check such values. Previously,
these checks could miss relevant values that are wrapped inside range
types or sub-domains, possibly allowing the database to become
inconsistent.
</para>
</listitem>

<listitem>
<para>
Fix crash in <application>pg_restore</application> when using parallel mode and
using a list file to select a subset of items to restore
(Fabr&iacute;zio de Royes Mello)
</para>
</listitem>

<listitem>
<para>
Change <application>ecpg</application>'s parser to allow <literal>RETURNING</literal>
clauses without attached C variables (Michael Meskes)
</para>

<para>
This allows <application>ecpg</application> programs to contain SQL constructs
that use <literal>RETURNING</literal> internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
</para>
</listitem>

<listitem>
<para>
Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)
</para>

<para>
This fix avoids possible crashes of PL/Perl due to inconsistent
assumptions about the width of <type>time_t</type> values.
A side-effect that may be visible to extension developers is
that <literal>_USE_32BIT_TIME_T</literal> is no longer defined globally
in <productname>PostgreSQL</productname> Windows builds. This is not expected
to cause problems, because type <type>time_t</type> is not used
in any <productname>PostgreSQL</productname> API definitions.
</para>
</listitem>

</itemizedlist>

</sect2>
</sect1>

<sect1 id="release-9-3-18">
<title>Release 9.3.18</title>

Expand Down

0 comments on commit ae67fee

Please sign in to comment.