rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-09-30 22:01:16 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update release notes for RC1.

Browse Source
This commit is contained in:
Tom Lane 2006-11-24 23:31:55 +00:00
parent df3a6fe477
commit a7a3d0f0d9
1 changed files with 77 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

93
doc/src/sgml/release.sgml
View File

@ -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>
@ -407,19 +407,22 @@ links to the main documentation.
</para>
</listitem>
<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.
</para>
<para>
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)
</para>
<listitem>
<para>
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.
</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>
@ -1761,18 +1794,18 @@ links to the main documentation.
</para>
</listitem>
<listitem>
<para>
Run PL/Perl and PL/PerlU in separate interpreters, for security
reasons.
</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)
</para>
</listitem>
<listitem>
<para>
Run PL/Perl and PL/PerlU in separate interpreters, for security
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 languages can be used
in any given backend process.
</para>
</listitem>
</itemizedlist>
@ -1815,6 +1848,12 @@ links to the main documentation.
</para>
</listitem>
<listitem>
<para>
Python 2.5 is now supported (Tom)
</para>
</listitem>
</itemizedlist>
</sect3>