mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-02-05 19:09:58 +08:00
Update release notes for RC1.
This commit is contained in:
parent
df3a6fe477
commit
a7a3d0f0d9
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.484 2006/11/23 03:30:49 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.485 2006/11/24 23:31:55 tgl Exp $ -->
|
||||
<!--
|
||||
|
||||
Typical markup:
|
||||
@ -40,7 +40,7 @@ links to the main documentation.
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2006-1?-??</simpara>
|
||||
<para>CURRENT AS OF 2006-11-05</>
|
||||
<para>CURRENT AS OF 2006-11-24</>
|
||||
</note>
|
||||
|
||||
<sect2>
|
||||
@ -409,17 +409,20 @@ links to the main documentation.
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Data can no longer be shared between a PL/Perl function and a
|
||||
PL/PerlU function, and modules used by a /PerlU function are no
|
||||
longer available to PL/Perl functions.
|
||||
For security's sake, modules used by a PL/PerlU function are no
|
||||
longer available to PL/Perl functions (Andrew)
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
This also implies that data can no longer be shared between a PL/Perl
|
||||
function and a PL/PerlU function.
|
||||
Some perl installations have not been compiled with the correct flags
|
||||
to allow multiple interpreters to exist within a single process.
|
||||
In this situation PL/Perl and PL/PerlU cannot both be used in a
|
||||
single backend. The solution is to get a Perl installation which
|
||||
supports multiple interpreters. (Andrew)
|
||||
supports multiple interpreters.
|
||||
</para>
|
||||
</note>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
@ -938,6 +941,36 @@ links to the main documentation.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix race condition for truncation of a large relation across a
|
||||
gigabyte boundary by <command>VACUUM</> (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix bug causing needless deadlock errors on row-level locks (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix bugs affecting multi-gigabyte hash indexes (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Each backend process is now its own process group leader (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This allows query cancel to abort subprocesses invoked from a
|
||||
backend or archive/recovery process.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect3>
|
||||
@ -1764,13 +1797,13 @@ links to the main documentation.
|
||||
<listitem>
|
||||
<para>
|
||||
Run PL/Perl and PL/PerlU in separate interpreters, for security
|
||||
reasons.
|
||||
reasons (Andrew)
|
||||
</para>
|
||||
<para>
|
||||
In consequence, they can no longer share data nor loaded modules.
|
||||
Also, if Perl has not been compiled with the requisite flags to
|
||||
allow multiple interpreters, only one of these lamguages can be used
|
||||
in any given backend process. (Andrew)
|
||||
allow multiple interpreters, only one of these languages can be used
|
||||
in any given backend process.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
@ -1815,6 +1848,12 @@ links to the main documentation.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Python 2.5 is now supported (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect3>
|
||||
|
Loading…
Reference in New Issue
Block a user