Commit 9e6c5f1e authored by Bruce Momjian's avatar Bruce Momjian

Move server-side languages up one section in the 9.0 release notes.

parent bf6285b3
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-9.0.sgml,v 2.3 2010/03/20 03:30:12 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/release-9.0.sgml,v 2.4 2010/03/20 14:03:31 momjian Exp $ -->
<sect1 id="release-9-0"> <sect1 id="release-9-0">
...@@ -1289,259 +1289,259 @@ ...@@ -1289,259 +1289,259 @@
</sect4> </sect4>
<sect4> </sect3>
<title>Server-Side Languages</title>
<sect3>
<title>Server-Side Languages</title>
<itemizedlist>
<listitem>
<para>
Add the <literal>OR REPLACE</> clause to <command>CREATE
LANGUAGE</> (Tom)
</para>
<para>
This is helpful to optionally install a language if it does not
already exist, and is particularly helpful now that PL/pgSQL is
installed by default.
</para>
</listitem>
</itemizedlist>
<sect4>
<title>PL/PgSQL Server-Side Language</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Add the <literal>OR REPLACE</> clause to <command>CREATE Install server-side language PL/pgSQL by default (Bruce)
LANGUAGE</> (Tom)
</para> </para>
</listitem>
<listitem>
<para> <para>
This is helpful to optionally install a language if it does not Allow PL/pgSQL to handle row types with dropped columns (Pavel Stehule)
already exist, and is particularly helpful now that PL/pgSQL is
installed by default.
</para> </para>
</listitem> </listitem>
</itemizedlist> <listitem>
<para>
<sect5> Allow <literal>IN</> parameters to be assigned values within
<title>PL/PgSQL Server-Side Language</title> PL/pgSQL functions (Steve Prentice)
</para>
<itemizedlist> </listitem>
<listitem>
<para>
Install server-side language PL/pgSQL by default (Bruce)
</para>
</listitem>
<listitem>
<para>
Allow PL/pgSQL to handle row types with dropped columns (Pavel Stehule)
</para>
</listitem>
<listitem>
<para>
Allow <literal>IN</> parameters to be assigned values within
PL/pgSQL functions (Steve Prentice)
</para>
</listitem>
<listitem>
<para>
Improve error location reporting in PL/pgSQL (Tom)
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Have PL/pgSQL use the main lexer, rather than a custom version (Tom) Improve error location reporting in PL/pgSQL (Tom)
</para> </para>
</listitem> </listitem>
</itemizedlist> <listitem>
<para>
Have PL/pgSQL use the main lexer, rather than a custom version (Tom)
</para>
</listitem>
</sect5> </itemizedlist>
<sect5> </sect4>
<title>PL/pgSQL Cursors</title>
<itemizedlist>
<listitem> <sect4>
<para> <title>PL/pgSQL Cursors</title>
Add count and <literal>ALL</> options to <command>MOVE <itemizedlist>
FORWARD</>/<literal>BACKWARD</> in PL/pgSQL (Pavel Stehule)
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Allow PL/pgSQL's <literal>WHERE CURRENT OF</> to use a cursor Add count and <literal>ALL</> options to <command>MOVE
variable (Tom) FORWARD</>/<literal>BACKWARD</> in PL/pgSQL (Pavel Stehule)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add PL/pgSQL's <command>OPEN cursor FOR EXECUTE</> to use parameters Allow PL/pgSQL's <literal>WHERE CURRENT OF</> to use a cursor
(Pavel Stehule, Itagaki Takahiro) variable (Tom)
</para> </para>
</listitem>
<para> <listitem>
This is accomplished with a new <literal>USING</> clause. <para>
</para> Add PL/pgSQL's <command>OPEN cursor FOR EXECUTE</> to use parameters
</listitem> (Pavel Stehule, Itagaki Takahiro)
</para>
</itemizedlist> <para>
This is accomplished with a new <literal>USING</> clause.
</para>
</listitem>
</sect5> </itemizedlist>
<sect5> </sect4>
<title>PL/Perl Server-Side Language</title>
<itemizedlist>
<listitem> <sect4>
<para> <title>PL/Perl Server-Side Language</title>
Add new PL/Perl functions: <function>quote_literal()</>, <itemizedlist>
<function>quote_nullable()</>, <function>quote_ident()</>,
<function>encode_bytea()</>, <function>decode_bytea()</>,
<function>looks_like_number()</>, <function>encode_array_literal()</>,
<function>encode_array_constructor()</> (Tim Bunce)
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Add server variable <varname>plperl.on_init</> to specify a PL/Perl Add new PL/Perl functions: <function>quote_literal()</>,
Perl initialization function (Tim Bunce) <function>quote_nullable()</>, <function>quote_ident()</>,
</para> <function>encode_bytea()</>, <function>decode_bytea()</>,
<function>looks_like_number()</>, <function>encode_array_literal()</>,
<function>encode_array_constructor()</> (Tim Bunce)
</para>
</listitem>
<para> <listitem>
<varname>plperl.on_plperl_init</> and <varname>plperl.on_plperlu_init</> <para>
are also available for trusted/untrusted-specific initialization. Add server variable <varname>plperl.on_init</> to specify a PL/Perl
</para> Perl initialization function (Tim Bunce)
</listitem> </para>
<listitem> <para>
<para> <varname>plperl.on_plperl_init</> and <varname>plperl.on_plperlu_init</>
Improve error context support in PL/Perl (Alexey Klyukin) are also available for trusted/untrusted-specific initialization.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Support <command>END</> blocks in PL/Perl (Tim Bunce) Improve error context support in PL/Perl (Alexey Klyukin)
</para> </para>
</listitem>
<para> <listitem>
<command>END</> blocks do not currently allow database access. <para>
</para> Support <command>END</> blocks in PL/Perl (Tim Bunce)
</listitem> </para>
<listitem> <para>
<para> <command>END</> blocks do not currently allow database access.
Allow <command>use strict</> in PL/Perl (Tim Bunce) </para>
</para> </listitem>
</listitem>
<listitem> <listitem>
<para> <para>
Allow <command>require</> in PL/Perl (Tim Bunce) Allow <command>use strict</> in PL/Perl (Tim Bunce)
</para> </para>
</listitem>
<para> <listitem>
This basically tests to see if the module is loaded, and if not, <para>
generates an error. Allow <command>require</> in PL/Perl (Tim Bunce)
</para> </para>
</listitem>
<listitem> <para>
<para> This basically tests to see if the module is loaded, and if not,
Allow <command>use feature</> in PL/Perl if Perl version 5.10 or generates an error.
later is used (Tim Bunce) </para>
</para> </listitem>
</listitem>
<listitem> <listitem>
<para> <para>
Verify that PL/Perl return values are valid in the server encoding Allow <command>use feature</> in PL/Perl if Perl version 5.10 or
(Andrew) later is used (Tim Bunce)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Improve PL/Perl code structure (Tim Bunce) Verify that PL/Perl return values are valid in the server encoding
</para> (Andrew)
</listitem> </para>
</listitem>
<listitem> <listitem>
<para> <para>
PL/Perl subroutines are now given names (Tim Bunce) Improve PL/Perl code structure (Tim Bunce)
</para> </para>
</listitem>
<para> <listitem>
This is for the use of profiling and code coverage tools. DIDN'T <para>
THEY HAVE NAMES BEFORE? PL/Perl subroutines are now given names (Tim Bunce)
</para> </para>
</listitem>
<listitem> <para>
<para> This is for the use of profiling and code coverage tools. DIDN'T
PL/Perl no longer allows <application>Safe</> version 2.20 because THEY HAVE NAMES BEFORE?
it is unsafe (Tim Bunce) </para>
</para> </listitem>
</listitem>
</itemizedlist> <listitem>
<para>
PL/Perl no longer allows <application>Safe</> version 2.20 because
it is unsafe (Tim Bunce)
</para>
</listitem>
</sect5> </itemizedlist>
<sect5> </sect4>
<title>PL/Python Server-Side Language</title>
<itemizedlist>
<listitem> <sect4>
<para> <title>PL/Python Server-Side Language</title>
Add Unicode support in PL/Python (Peter) <itemizedlist>
</para>
<para> <listitem>
Strings are automatically converted from/to the server encoding as <para>
necessary. Add Unicode support in PL/Python (Peter)
</para> </para>
</listitem>
<listitem> <para>
<para> Strings are automatically converted from/to the server encoding as
Improve <type>bytea</> support in PL/Python (Caleb Welton) necessary.
</para> </para>
</listitem>
<para> <listitem>
<type>Bytea</> values passed into PL/Python now are represented as <para>
binary, rather than the Postgres <type>bytea</> text format. Null Improve <type>bytea</> support in PL/Python (Caleb Welton)
bytes are now also output properly from PL/Python. <type>Boolean</> </para>
and <type>numeric</> value passing in PL/Python was also improved.
</para>
</listitem>
<listitem> <para>
<para> <type>Bytea</> values passed into PL/Python now are represented as
Add array parameter/return support to PL/Python (Peter) binary, rather than the Postgres <type>bytea</> text format. Null
</para> bytes are now also output properly from PL/Python. <type>Boolean</>
</listitem> and <type>numeric</> value passing in PL/Python was also improved.
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Improve mapping of domains to Python base types in PL/Python (Peter) Add array parameter/return support to PL/Python (Peter)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add <application>Python</> 3 support to PL/Python (Peter) Improve mapping of domains to Python base types in PL/Python (Peter)
</para> </para>
</listitem>
<para> <listitem>
The new server-side language is called <literal>plpython3u</>. <para>
</para> Add <application>Python</> 3 support to PL/Python (Peter)
</listitem> </para>
<listitem> <para>
<para> The new server-side language is called <literal>plpython3u</>.
Improve error location and exception reporting in PL/Python (Peter) </para>
</para> </listitem>
</listitem>
</itemizedlist> <listitem>
<para>
Improve error location and exception reporting in PL/Python (Peter)
</para>
</listitem>
</sect5> </itemizedlist>
</sect4> </sect4>
...@@ -1552,9 +1552,9 @@ ...@@ -1552,9 +1552,9 @@
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Add <command>vacuumdb</> <option>--analyze-only</> option to only Add <command>vacuumdb</> <option>--analyze-only</> option to only
analyze (Bruce) analyze (Bruce)
</para> </para>
</listitem> </listitem>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment