Skip to content

Commit

Permalink
Mise à jour en version 8.4.13
Browse files Browse the repository at this point in the history
  • Loading branch information
@gleu
gleu committed Aug 24, 2012
1 parent afe47ef commit 6388871
Show file tree
Hide file tree
Showing 6 changed files with 465 additions and 11 deletions.
5 changes: 5 additions & 0 deletions backup.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1448,6 +1448,11 @@ tar -rf /var/lib/pgsql/backup.tar /var/lib/pgsql/archive/
Rappelez vous d'ajouter de la gestion d'erreur à vos scripts.
</para>

</sect3>

<sect3 id="compressed-archive-logs">
<title>Compression des journaux archivés</title>

<para>
Si la taille du stockage des archives est un problème, utilisez
<application>pg_compresslog</application>,
Expand Down
4 changes: 2 additions & 2 deletions legal.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,15 +5,15 @@
révision $Revision$ -->

<copyright>
<year>1996-2009</year>
<year>1996-2012</year>
<holder>The PostgreSQL Global Development Group</holder>
</copyright>

<legalnotice id="legalnotice">
<title>Legal Notice</title>

<para>
<productname>PostgreSQL</productname> is Copyright &copy; 1996-2009
<productname>PostgreSQL</productname> is Copyright &copy; 1996-2012
by the PostgreSQL Global Development Group and is distributed under
the terms of the license of the University of California below.
</para>
Expand Down
223 changes: 223 additions & 0 deletions release-8.3.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,229 @@
par $Author: gleu $
révision $Revision: 1317 $ -->

<sect1 id="release-8-3-20">
<title>Release 8.3.20</title>

<note>
<title>Release Date</title>
<simpara>2012-08-17</simpara>
</note>

<para>
This release contains a variety of fixes from 8.3.19.
For information about new features in the 8.3 major release, see
<xref linkend="release-8-3"/>.
</para>

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

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

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

<para>
However, if you are upgrading from a version earlier than 8.3.17,
see the release notes for 8.3.17.
</para>

</sect2>

<sect2>
<title>Changes</title>

<itemizedlist>

<listitem>
<para>
Prevent access to external files/URLs via XML entity references
(Noah Misch, Tom Lane)
</para>

<para>
<function>xml_parse()</function> would attempt to fetch external files or
URLs as needed to resolve DTD and entity references in an XML value,
thus allowing unprivileged database users to attempt to fetch data
with the privileges of the database server. While the external data
wouldn't get returned directly to the user, portions of it could be
exposed in error messages if the data didn't parse as valid XML; and
in any case the mere ability to check existence of a file might be
useful to an attacker. (CVE-2012-3489)
</para>
</listitem>

<listitem>
<para>
Prevent access to external files/URLs via <filename>contrib/xml2</filename>'s
<function>xslt_process()</function> (Peter Eisentraut)
</para>

<para>
<application>libxslt</application> offers the ability to read and write both
files and URLs through stylesheet commands, thus allowing
unprivileged database users to both read and write data with the
privileges of the database server. Disable that through proper use
of <application>libxslt</application>'s security options. (CVE-2012-3488)
</para>

<para>
Also, remove <function>xslt_process()</function>'s ability to fetch documents
and stylesheets from external files/URLs. While this was a
documented <quote>feature</quote>, it was long regarded as a bad idea.
The fix for CVE-2012-3489 broke that capability, and rather than
expend effort on trying to fix it, we're just going to summarily
remove it.
</para>
</listitem>

<listitem>
<para>
Prevent too-early recycling of btree index pages (Noah Misch)
</para>

<para>
When we allowed read-only transactions to skip assigning XIDs, we
introduced the possibility that a deleted btree page could be
recycled while a read-only transaction was still in flight to it.
This would result in incorrect index search results. The probability
of such an error occurring in the field seems very low because of the
timing requirements, but nonetheless it should be fixed.
</para>
</listitem>

<listitem>
<para>
Fix crash-safety bug with newly-created-or-reset sequences (Tom Lane)
</para>

<para>
If <command>ALTER SEQUENCE</command> was executed on a freshly created or
reset sequence, and then precisely one <function>nextval()</function> call
was made on it, and then the server crashed, WAL replay would restore
the sequence to a state in which it appeared that no
<function>nextval()</function> had been done, thus allowing the first
sequence value to be returned again by the next
<function>nextval()</function> call. In particular this could manifest for
<type>serial</type> columns, since creation of a serial column's sequence
includes an <command>ALTER SEQUENCE OWNED BY</command> step.
</para>
</listitem>

<listitem>
<para>
Ensure the <filename>backup_label</filename> file is fsync'd after
<function>pg_start_backup()</function> (Dave Kerr)
</para>
</listitem>

<listitem>
<para>
Back-patch 9.1 improvement to compress the fsync request queue
(Robert Haas)
</para>

<para>
This improves performance during checkpoints. The 9.1 change
has now seen enough field testing to seem safe to back-patch.
</para>
</listitem>

<listitem>
<para>
Only allow autovacuum to be auto-canceled by a directly blocked
process (Tom Lane)
</para>

<para>
The original coding could allow inconsistent behavior in some cases;
in particular, an autovacuum could get canceled after less than
<literal>deadlock_timeout</literal> grace period.
</para>
</listitem>

<listitem>
<para>
Improve logging of autovacuum cancels (Robert Haas)
</para>
</listitem>

<listitem>
<para>
Fix log collector so that <literal>log_truncate_on_rotation</literal> works
during the very first log rotation after server start (Tom Lane)
</para>
</listitem>

<listitem>
<para>
Ensure that a whole-row reference to a subquery doesn't include any
extra <literal>GROUP BY</literal> or <literal>ORDER BY</literal> columns (Tom Lane)
</para>
</listitem>

<listitem>
<para>
Disallow copying whole-row references in <literal>CHECK</literal>
constraints and index definitions during <command>CREATE TABLE</command>
(Tom Lane)
</para>

<para>
This situation can arise in <command>CREATE TABLE</command> with
<literal>LIKE</literal> or <literal>INHERITS</literal>. The copied whole-row
variable was incorrectly labeled with the row type of the original
table not the new one. Rejecting the case seems reasonable for
<literal>LIKE</literal>, since the row types might well diverge later. For
<literal>INHERITS</literal> we should ideally allow it, with an implicit
coercion to the parent table's row type; but that will require more
work than seems safe to back-patch.
</para>
</listitem>

<listitem>
<para>
Fix memory leak in <literal>ARRAY(SELECT ...)</literal> subqueries (Heikki
Linnakangas, Tom Lane)
</para>
</listitem>

<listitem>
<para>
Fix extraction of common prefixes from regular expressions (Tom Lane)
</para>

<para>
The code could get confused by quantified parenthesized
subexpressions, such as <literal>^(foo)?bar</literal>. This would lead to
incorrect index optimization of searches for such patterns.
</para>
</listitem>

<listitem>
<para>
Report errors properly in <filename>contrib/xml2</filename>'s
<function>xslt_process()</function> (Tom Lane)
</para>
</listitem>

<listitem>
<para>
Update time zone data files to <application>tzdata</application> release 2012e
for DST law changes in Morocco and Tokelau
</para>
</listitem>

</itemizedlist>

</sect2>
</sect1>

<sect1 id="release-8-3-19">
<title>Release 8.3.19</title>

Expand Down

0 comments on commit 6388871

Please sign in to comment.