Skip to content

Commit

Permalink
Mise à jour en version 9.0.13
Browse files Browse the repository at this point in the history
  • Loading branch information
@gleu
gleu committed May 8, 2013
1 parent a16c144 commit f891be0
Show file tree
Hide file tree
Showing 5 changed files with 566 additions and 30 deletions.
47 changes: 28 additions & 19 deletions postgresql/func.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1544,8 +1544,9 @@ both</optional>
Code les données binaires en une représentation textuelle. Les
formats supportés sont&nbsp;:
<literal>base64</literal>, <literal>hex</literal>, <literal>escape</literal>.
<literal>escape</literal> affiche simplement des octets nuls sous la
forme <literal>\000</literal> et des antislashs.
<literal>escape</literal> convertit les octets nuls et les octets dont le bit
de poids fort est à 1, en séquence octal (<literal>\</><replaceable>nnn</>)
et des antislashs doubles.
</entry>
<entry><literal>encode( E'123\\000\\001', 'base64')</literal></entry>
<entry><literal>MTIzAAE=</literal></entry>
Expand Down Expand Up @@ -2884,13 +2885,14 @@ in <parameter>chaîne</parameter>)</literal></entry>
<row>
<entry>
<literal><function>decode</function>(<parameter>chaîne</parameter> <type>text</type>,
<parameter>type</parameter> <type>text</type>)</literal>
<parameter>format</parameter> <type>text</type>)</literal>
</entry>
<entry><type>bytea</type></entry>
<entry>
Décode la chaîne binaire <parameter>chaîne</parameter> auparavant codée
avec <function>encode</function>. Le type de paramètre est le même que
dans <function>encode</function>.
Décode les données binaires de leur représentation textuelle dans
<parameter>chaîne</parameter> auparavant codée. Les options pour
<parameter>format</parameter> sont les mêmes que pour
<function>encode</function>.
</entry>
<entry><literal>decode(E'123\\000456', 'escape')</literal></entry>
<entry><literal>123\000456</literal></entry>
Expand All @@ -2903,9 +2905,12 @@ in <parameter>chaîne</parameter>)</literal></entry>
</entry>
<entry><type>text</type></entry>
<entry>
Code la chaîne binaire en sa représentation <acronym>ASCII</acronym>.
Les types supportés sont <literal>base64</literal>,
<literal>hex</literal>, <literal>escape</literal>.
Code les données binaires en une représentation textuelle. Les formats
supportés sont&nbsp;:
<literal>base64</literal>, <literal>hex</literal>, <literal>escape</literal>.
<literal>escape</literal> convertit les octets nuls et les octets dont le bit
de poids fort est à 1, en séquence octal (<literal>\</><replaceable>nnn</>)
et des antislashs doubles.
</entry>
<entry><literal>encode(E'123\\000456'::bytea, 'escape')</literal></entry>
<entry><literal>123\000456</literal></entry>
Expand Down Expand Up @@ -6920,18 +6925,22 @@ SELECT EXTRACT(SECOND FROM TIME '17:12:28.5');
<term><literal>week</literal></term>
<listitem>
<para>
Le numéro de la semaine dans l'année, à laquelle appartient le jour. Par
définition (<acronym>ISO</acronym> 8601), la première semaine d'une
année contient le 4 janvier de cette année. (La semaine
<acronym>ISO</acronym>-8601 commence un lundi.) Dit autrement, le
premier jeudi d'une année se trouve dans la première semaine de cette
année.
Le numéro de la semaine dans l'année, à laquelle appartient le jour.
Par définition (<acronym>ISO</acronym> 8601), les semaines commencent
le lundi et la première semaine d'une année contient le 4 janvier de
cette année. Autrement dit, le premier jeudi d'une année se trouve dans
la première semaine de cette année.
</para>
<para>
De ce fait, les dates de début janvier peuvent
faire partie de la 52è ou 53è semaine de l'année précédente. Par exemple,
<literal>2005-01-01</literal> fait partie de la 53è semaine de 2004 et
<literal>2006-01-01</literal> fait partie de la 52è semaine de l'année 2005.
Dans la définition ISO, il est possible que les premiers jours de janvier
fassent partie de la semaine 52 ou 53 de l'année précédente. Il est aussi
possibles que les derniers jours de décembre fassent partie de la première
semaine de l'année suivante. Par exemple, <literal>2005-01-01</literal>
fait partie de la semaine 53 de l'année 2004 et <literal>2006-01-01</literal>
fait partie de la semaine 52 de l'année 2005, alors que
<literal>2012-12-31</literal> fait partie de la première semaine de 2013.
Il est recommandé d'utiliser le champ <literal>isoyear</literal> avec
<literal>week</literal> pour obtenir des résultats cohérents.
</para>

<screen>SELECT EXTRACT(WEEK FROM TIMESTAMP '2001-02-16 20:38:40');
Expand Down
237 changes: 233 additions & 4 deletions postgresql/release-8.4.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,235 @@
par $Author: gleu $
révision $Revision: 1317 $ -->

<sect1 id="release-8-4-17">
<title>Release 8.4.17</title>

<note>
<title>Release Date</title>
<simpara>2013-04-04</simpara>
</note>

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

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

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

<para>
However, this release corrects several errors in management of GiST
indexes. After installing this update, it is advisable to
<command>REINDEX</command> any GiST indexes that meet one or more of the
conditions described below.
</para>

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

</sect2>

<sect2>
<title>Changes</title>

<itemizedlist>

<listitem>
<para>
Reset OpenSSL randomness state in each postmaster child process
(Marko Kreen)
</para>

<para>
This avoids a scenario wherein random numbers generated by
<filename>contrib/pgcrypto</filename> functions might be relatively easy for
another database user to guess. The risk is only significant when
the postmaster is configured with <varname>ssl</varname> = <literal>on</literal>
but most connections don't use SSL encryption. (CVE-2013-1900)
</para>
</listitem>

<listitem>
<para>
Fix GiST indexes to not use <quote>fuzzy</quote> geometric comparisons when
it's not appropriate to do so (Alexander Korotkov)
</para>

<para>
The core geometric types perform comparisons using <quote>fuzzy</quote>
equality, but <function>gist_box_same</function> must do exact comparisons,
else GiST indexes using it might become inconsistent. After installing
this update, users should <command>REINDEX</command> any GiST indexes on
<type>box</type>, <type>polygon</type>, <type>circle</type>, or <type>point</type>
columns, since all of these use <function>gist_box_same</function>.
</para>
</listitem>

<listitem>
<para>
Fix erroneous range-union and penalty logic in GiST indexes that use
<filename>contrib/btree_gist</filename> for variable-width data types, that is
<type>text</type>, <type>bytea</type>, <type>bit</type>, and <type>numeric</type>
columns (Tom Lane)
</para>

<para>
These errors could result in inconsistent indexes in which some keys
that are present would not be found by searches, and also in useless
index bloat. Users are advised to <command>REINDEX</command> such indexes
after installing this update.
</para>
</listitem>

<listitem>
<para>
Fix bugs in GiST page splitting code for multi-column indexes
(Tom Lane)
</para>

<para>
These errors could result in inconsistent indexes in which some keys
that are present would not be found by searches, and also in indexes
that are unnecessarily inefficient to search. Users are advised to
<command>REINDEX</command> multi-column GiST indexes after installing this
update.
</para>
</listitem>

<listitem>
<para>
Fix infinite-loop risk in regular expression compilation (Tom Lane,
Don Porter)
</para>
</listitem>

<listitem>
<para>
Fix potential null-pointer dereference in regular expression compilation
(Tom Lane)
</para>
</listitem>

<listitem>
<para>
Fix <function>to_char()</function> to use ASCII-only case-folding rules where
appropriate (Tom Lane)
</para>

<para>
This fixes misbehavior of some template patterns that should be
locale-independent, but mishandled <quote><literal>I</literal></quote> and
<quote><literal>i</literal></quote> in Turkish locales.
</para>
</listitem>

<listitem>
<para>
Fix unwanted rejection of timestamp <literal>1999-12-31 24:00:00</literal>
(Tom Lane)
</para>
</listitem>

<listitem>
<para>
Remove useless <quote>picksplit doesn't support secondary split</quote> log
messages (Josh Hansen, Tom Lane)
</para>

<para>
This message seems to have been added in expectation of code that was
never written, and probably never will be, since GiST's default
handling of secondary splits is actually pretty good. So stop nagging
end users about it.
</para>
</listitem>

<listitem>
<para>
Fix possible failure to send a session's last few transaction
commit/abort counts to the statistics collector (Tom Lane)
</para>
</listitem>

<listitem>
<para>
Eliminate memory leaks in PL/Perl's <function>spi_prepare()</function> function
(Alex Hunsaker, Tom Lane)
</para>
</listitem>

<listitem>
<para>
Fix <application>pg_dumpall</application> to handle database names containing
<quote><literal>=</literal></quote> correctly (Heikki Linnakangas)
</para>
</listitem>

<listitem>
<para>
Avoid crash in <application>pg_dump</application> when an incorrect connection
string is given (Heikki Linnakangas)
</para>
</listitem>

<listitem>
<para>
Ignore invalid indexes in <application>pg_dump</application> (Michael Paquier)
</para>

<para>
Dumping invalid indexes can cause problems at restore time, for example
if the reason the index creation failed was because it tried to enforce
a uniqueness condition not satisfied by the table's data. Also, if the
index creation is in fact still in progress, it seems reasonable to
consider it to be an uncommitted DDL change, which
<application>pg_dump</application> wouldn't be expected to dump anyway.
</para>
</listitem>

<listitem>
<para>
Fix <filename>contrib/pg_trgm</filename>'s <function>similarity()</function> function
to return zero for trigram-less strings (Tom Lane)
</para>

<para>
Previously it returned <literal>NaN</literal> due to internal division by zero.
</para>
</listitem>

<listitem>
<para>
Update time zone data files to <application>tzdata</application> release 2013b
for DST law changes in Chile, Haiti, Morocco, Paraguay, and some
Russian areas. Also, historical zone data corrections for numerous
places.
</para>

<para>
Also, update the time zone abbreviation files for recent changes in
Russia and elsewhere: <literal>CHOT</literal>, <literal>GET</literal>,
<literal>IRKT</literal>, <literal>KGT</literal>, <literal>KRAT</literal>, <literal>MAGT</literal>,
<literal>MAWT</literal>, <literal>MSK</literal>, <literal>NOVT</literal>, <literal>OMST</literal>,
<literal>TKT</literal>, <literal>VLAT</literal>, <literal>WST</literal>, <literal>YAKT</literal>,
<literal>YEKT</literal> now follow their current meanings, and
<literal>VOLT</literal> (Europe/Volgograd) and <literal>MIST</literal>
(Antarctica/Macquarie) are added to the default abbreviations list.
</para>
</listitem>

</itemizedlist>

</sect2>
</sect1>

<sect1 id="release-8-4-16">
<title>Release 8.4.16</title>

Expand Down Expand Up @@ -101,10 +330,10 @@
</para>

<para>
The main consequence of this mistake is that lowering <link
linkend="guc-vacuum-freeze-min-age"><varname>vacuum_freeze_min_age</varname></link>
would cause full-table vacuuming scans to occur much more frequently
than intended.
In installations that have existed for more than <link
linkend="guc-vacuum-freeze-min-age"><varname>vacuum_freeze_min_age</></link>
transactions, this mistake prevented autovacuum from using partial-table
scans, so that a full-table scan would always happen instead.
</para>
</listitem>

Expand Down

0 comments on commit f891be0

Please sign in to comment.