Skip to content

P
Postgres FD Implementation
Commit e1c96527 authored by Peter Eisentraut's avatar Peter Eisentraut
Browse files
Options

Finalize 8.5alpha2 release notes, with updates from Josh Berkus

parent 7bd93589
Show whitespace changes
Inline Side-by-side
Showing with 74 additions and 68 deletions
doc/src/sgml/release-8.5.sgml
View file @ e1c96527
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.5.sgml,v 1.5 2009/10/20 19:52:58 petere Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.5.sgml,v 1.6 2009/10/21 19:43:06 petere Exp $ -->
<sect1 id="release-8-5"> <sect1 id="release-8-5">
<title>Release 8.5alpha2</title> <title>Release 8.5alpha2</title>
...@@ -52,60 +52,51 @@ ...@@ -52,60 +52,51 @@
reported. reported.
</para> </para>
</sect2> </sect2>
<sect2>
<title>Testing</title>
<para>
The primary reason we release alphas is to get users to test new
features as early as possible. If you are interested in helping
with organized testing, please see
<ulink url="http://wiki.postgresql.org/wiki/HowToBetaTest">the
testing information page</ulink>.
</para>
</sect2>
<sect2> <sect2>
<title>Changes</title> <title>Changes</title>
<sect3> <sect3>
<title>SQL Features</title> <title>SQL Features</title>
<itemizedlist> <itemizedlist>
<listitem override="box">
<para>
<emphasis>Modify the definition of window-function PARTITION
BY and ORDER BY clauses so that their elements are always
taken as simple expressions over the query's input
columns.</>
</para>
</listitem>
<listitem> <listitem>
<para> <para>
<emphasis>Fix bug with WITH RECURSIVE immediately inside WITH <emphasis>Add SQL-compliant triggers on columns, which fire only if
RECURSIVE.</> certain columns are named in the UPDATE's SET list.</>
</para>
</listitem>
<listitem>
<para>
<emphasis>Define a new, more extensible syntax for COPY options.</>
</para>
</listitem>
<listitem>
<para>
<emphasis>Add ALTER DEFAULT PRIVILEGES command, which allows
users to adjust the privileges that will be applied to
subsequently-created objects.</>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
<emphasis>Support use of function argument names to identify which <emphasis>Add CREATE LIKE INCLUDING COMMENTS and STORAGE, and INCLUDING
actual arguments match which function parameters. The syntax ALL shortcut to allow users to make an exact copy of a table including
uses AS, for example funcname(value AS arg1, anothervalue AS all options and features.</>
arg2).</>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
<emphasis>Add CREATE LIKE INCLUDING COMMENTS and STORAGE, and INCLUDING <emphasis>Define a new, more extensible syntax for COPY options
ALL shortcut.</> in order to support additional COPY options in the future.</>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
<emphasis>Add GRANT/REVOKE ON ALL TABLES/SEQUENCES/FUNCTIONS IN SCHEMA.</> <emphasis>Modify the definition of window-function PARTITION
BY and ORDER BY clauses so that their elements are always
taken as simple expressions over the query's input
columns. This fixes a bug.</>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
<emphasis>Add SQL-compliant triggers on columns, ie fire only if <emphasis>Fix bug with nested WITH RECURSIVE statements.</>
certain columns are named in the UPDATE's SET list.</>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
...@@ -171,7 +162,16 @@ ...@@ -171,7 +162,16 @@
<listitem> <listitem>
<para> <para>
<emphasis>Implement &quot;join removal&quot; for cases where the inner side <emphasis>Implement &quot;join removal&quot; for cases where the inner side
of a left join is unique and is not referenced above the join.</> of a left join is unique and is not referenced above the join. This should
speed up many ORM-generated and reporting tool queries.</emphasis>
</para>
</listitem>
<listitem>
<para>
<emphasis>Remove the use of the flat files pg_auth and
pg_database in order to improve performance. (Warning: pgbouncer
and possibly other tools currently suggest referring to the pg_auth
file for its user database. Such schemes will no longer work.)</emphasis>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
...@@ -249,7 +249,7 @@ ...@@ -249,7 +249,7 @@
<listitem> <listitem>
<para> <para>
<emphasis>Make it possibly to specify server configuration parameters <emphasis>Make it possibly to specify server configuration parameters
per user and per database. psql has gained a drds command to per user-database combination. Add a \drds command to psql to
display the settings.</> display the settings.</>
</para> </para>
</listitem> </listitem>
...@@ -257,6 +257,14 @@ ...@@ -257,6 +257,14 @@
<para> <para>
<emphasis>Allow the collection of statistics on sequences.</> <emphasis>Allow the collection of statistics on sequences.</>
</para> </para>
</listitem>
<listitem>
<para>
<emphasis>Increase the maximum value of extra_float_digits to
3, and have pg_dump use that value when the backend is new
enough to allow it, because it is possible to need 3 extra
digits for float4 values (but not for float8 values).</>
</para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
...@@ -275,25 +283,26 @@ ...@@ -275,25 +283,26 @@
</itemizedlist> </itemizedlist>
</sect3> </sect3>
<sect3> <sect3>
<title>Server Configuration</title> <title>Security</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
<emphasis>Increase the maximum value of extra_float_digits to <emphasis>Add ALTER DEFAULT PRIVILEGES command, which allows
3, and have pg_dump use that value when the backend is new users to adjust the privileges that will be applied to
enough to allow it, because it is possible to need 3 extra subsequently-created objects.</>
digits for float4 values (but not for float8 values).</> </para>
</listitem>
<listitem>
<para>
<emphasis>Add GRANT/REVOKE ON ALL TABLES/SEQUENCES/FUNCTIONS IN SCHEMA.
This makes it easier to manage permissions on database objects.</emphasis>
</para> </para>
</listitem> </listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Security</title>
<itemizedlist>
<listitem> <listitem>
<para> <para>
<emphasis>Support &quot;samehost&quot; and &quot;samenet&quot; specifications <emphasis>Support &quot;samehost&quot; and &quot;samenet&quot; specifications
in pg_hba.conf.</emphasis> in pg_hba.conf. This allows users with dynamic server addresses to run
PostgreSQL without frequently modifying pg_hba.conf</emphasis>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
...@@ -374,14 +383,6 @@ ...@@ -374,14 +383,6 @@
the postmaster from a boot-time script.</emphasis> the postmaster from a boot-time script.</emphasis>
</para> </para>
</listitem> </listitem>
<listitem>
<para>
<emphasis>Remove the use of the flat files pg_auth and
pg_database. (At least pgbouncer currently suggests referring
to the pg_auth file for its user database. Such schemes will
no longer work.)</emphasis>
</para>
</listitem>
<listitem> <listitem>
<para> <para>
pg_dump/pg_restore --clean now drops large objects. pg_dump/pg_restore --clean now drops large objects.
...@@ -434,6 +435,14 @@ ...@@ -434,6 +435,14 @@
code without having to create a function for it.</> code without having to create a function for it.</>
</para> </para>
</listitem> </listitem>
<listitem>
<para>
<emphasis>Support use of function argument names to identify which
actual arguments match which function parameters. The syntax
uses AS, for example funcname(value AS arg1, anothervalue AS
arg2).</>
</para>
</listitem>
<listitem> <listitem>
<para> <para>
<emphasis>Fix/improve bytea and boolean support in PL/Python. Data type <emphasis>Fix/improve bytea and boolean support in PL/Python. Data type
...@@ -459,7 +468,7 @@ ...@@ -459,7 +468,7 @@
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
<emphasis>Allow plpgsql IN parameters to be assigned to.</> <emphasis>PL/pgSQL IN parameters now accept value assignments.</>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
...@@ -470,8 +479,8 @@ ...@@ -470,8 +479,8 @@
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
<emphasis>Allow MOVE FORWARD n, MOVE BACKWARD n, MOVE FORWARD ALL, MOVE <emphasis>Allow cursor commands MOVE FORWARD n, MOVE BACKWARD n,
BACKWARD ALL in PL/pgSQL.</> MOVE FORWARD ALL, MOVE BACKWARD ALL in PL/pgSQL.</>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
...@@ -498,7 +507,9 @@ ...@@ -498,7 +507,9 @@
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
<emphasis>Assorted improvements in contrib/hstore.</> <emphasis>Multiple improvements in contrib/hstore, including
raising limits on keys and values, conversions to and from
records and arrays, and support for GROUP BY and DISTINCT.</emphasis>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
...@@ -528,7 +539,7 @@ ...@@ -528,7 +539,7 @@
</itemizedlist> </itemizedlist>
</sect3> </sect3>
<sect3> <sect3>
<title>Programming Tools</title> <title>Development</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
...@@ -543,14 +554,9 @@ ...@@ -543,14 +554,9 @@
<listitem> <listitem>
<para> <para>
<emphasis>Make libpq reject non-numeric and out-of-range port numbers with a <emphasis>Make libpq reject non-numeric and out-of-range port numbers with a
suitable error message.</> suitable error message.</emphasis>
</para> </para>
</listitem> </listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Development</title>
<itemizedlist>
<listitem> <listitem>
<para> <para>
Functions which conflict with C++ reserved words have been renamed, Functions which conflict with C++ reserved words have been renamed,
......
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