Commit 3eedb9a1 authored by Bruce Momjian's avatar Bruce Momjian

More release note adjustments, reordering.

parent e604c8b5
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.617 2009/03/30 19:59:19 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.618 2009/03/30 20:32:49 momjian Exp $ -->
<!-- <!--
Typical markup: Typical markup:
...@@ -125,10 +125,29 @@ do it for earlier branch release files. ...@@ -125,10 +125,29 @@ do it for earlier branch release files.
<para> <para>
This was available previously via a configure This was available previously via a configure
--enable-integer-datetimes. --enable-integer-datetimes option.
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Remove <application>ipcclean</> utility command (Bruce)
</para>
<para>
The utility only worked on a few platforms; users should use
their operating system tools instead.
</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Server Settings</title>
<itemizedlist>
<listitem> <listitem>
<para> <para>
Change <filename>postgresql.conf</> default for log_min_messages Change <filename>postgresql.conf</> default for log_min_messages
...@@ -204,19 +223,9 @@ do it for earlier branch release files. ...@@ -204,19 +223,9 @@ do it for earlier branch release files.
<listitem> <listitem>
<para> <para>
Remove <application>ipcclean</> utility command (Bruce) The <link
</para> linkend="release-8-4-pg-hba-conf"><filename>pg_hba.conf</></link>
section below also has extensive changes related to migration.
<para>
The utility only worked on a few platforms; users should use
their operating system tools instead.
</para>
</listitem>
<listitem>
<para>
The <filename>pg_hba.conf</> section below also has extensive
changes related to migration.
</para> </para>
</listitem> </listitem>
...@@ -288,7 +297,7 @@ do it for earlier branch release files. ...@@ -288,7 +297,7 @@ do it for earlier branch release files.
<sect3> <sect3>
<title>Functions and Operators</title> <title>General Functions and Operators</title>
<itemizedlist> <itemizedlist>
...@@ -323,6 +332,31 @@ do it for earlier branch release files. ...@@ -323,6 +332,31 @@ do it for earlier branch release files.
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Remove <literal>~=~</> and <literal>~&lt;&gt;~</> operators
used for <literal>LIKE</> index comparisons (Tom) bjm: needed,
pg_upgrade impact?
</para>
<para>
A not-immediately-obvious incompatibility is that the sort
order within <literal>bpchar_pattern_ops</> indexes changes
--- it had been identical to plain <function>strcmp()</>, but
is now trailing-blank-insensitive. This will impact in-place
upgrades, if those ever happen.
</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Temporal Functions and Operators</title>
<itemizedlist>
<listitem> <listitem>
<para> <para>
Have <function>to_char()</>'s localized month/day names depend Have <function>to_char()</>'s localized month/day names depend
...@@ -381,22 +415,6 @@ do it for earlier branch release files. ...@@ -381,22 +415,6 @@ do it for earlier branch release files.
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Remove <literal>~=~</> and <literal>~&lt;&gt;~</> operators
used for <literal>LIKE</> index comparisons (Tom) bjm: needed,
pg_upgrade impact?
</para>
<para>
A not-immediately-obvious incompatibility is that the sort
order within <literal>bpchar_pattern_ops</> indexes changes
--- it had been identical to plain <function>strcmp()</>, but
is now trailing-blank-insensitive. This will impact in-place
upgrades, if those ever happen.
</para>
</listitem>
</itemizedlist> </itemizedlist>
</sect3> </sect3>
...@@ -547,27 +565,29 @@ do it for earlier branch release files. ...@@ -547,27 +565,29 @@ do it for earlier branch release files.
</sect3> </sect3>
<sect3> <sect3>
<title>Wide-Value Storage (<acronym>TOAST</>)</title> <title>Server Settings</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Consider <acronym>TOAST</> compression on values as short as Convert many <filename>postgresql.conf</> settings to enumerated
32 bytes (previously 256 bytes) (Tom) values so <literal>pg_settings</> can easily display valid
values (Magnus)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Require 25% of space savings before using <acronym>TOAST</> Add <varname>cursor_tuple_fraction</> parameter to control the
compression (previously 20%) (Tom) fraction of a cursor's rows expected to be requested by the
user (Robert Hell)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Be more aggressive in storing <literal>EXTERNAL</> and Allow underscores in <filename>postgresql.conf</> custom variable
<literal>EXTENDED</> column values in <acronym>TOAST</>(Tom) classes (Tom)
</para> </para>
</listitem> </listitem>
...@@ -576,29 +596,27 @@ do it for earlier branch release files. ...@@ -576,29 +596,27 @@ do it for earlier branch release files.
</sect3> </sect3>
<sect3> <sect3>
<title>Server Settings</title> <title>Authentication</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Convert many <filename>postgresql.conf</> settings to enumerated Report appropriate error message for combination of <literal>MD5</>
values so <literal>pg_settings</> can easily display valid authentication and <varname>db_user_namespace</> enabled (Bruce)
values (Magnus)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add <varname>cursor_tuple_fraction</> parameter to control the Support regular expressions in <filename>pg_ident.conf</>
fraction of a cursor's rows expected to be requested by the (Magnus)
user (Robert Hell)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow underscores in <filename>postgresql.conf</> custom variable Allow <productname>Kerberos</>/<acronym>GSSAPI</> parameters
classes (Tom) to be changed without restarting the postmaster (Magnus)
</para> </para>
</listitem> </listitem>
...@@ -606,88 +624,109 @@ do it for earlier branch release files. ...@@ -606,88 +624,109 @@ do it for earlier branch release files.
</sect3> </sect3>
<sect3> <sect3 id="release-8-4-pg-hba-conf">
<title>Monitoring</title> <title><filename>pg_hba.conf</></title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Add <function>pg_conf_load_time()</> to report when Parse <filename>pg_hba.conf</> in the postmaster so errors are
the Postgres configuration files were last loaded (George reported on reload (Magnus)
Gensure)
</para> </para>
</listitem>
<listitem>
<para> <para>
Add <function>pg_terminate_backend()</> to safely terminate a Previously errors in the file wouldn't be detected until clients
backend (the <literal>SIGTERM</> signal works also) (Tom, Bruce) tried to connect, which could leave the system with a broken
file loaded.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add ability to track user-defined functions call counts and Remove the <literal>sameuser</> option, making it the default
runtimes via parameter <varname>track_functions</> (Martin if no usermap is specified (Magnus)
Pihlak)
</para> </para>
</listitem>
<listitem>
<para> <para>
Function statistics appear in a new system table, Change all authentication options to be <literal>name=value</>
<literal>pg_stat_user_functions</>. However, inlined settings (Magnus)
<acronym>SQL</> functions are not tracked.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow specification of the maximum <literal>pg_stat_activity</> Allow usermap parameter for all external authentication methods
query string size via <varname>track_activity_query_size</> (Magnus)
parameter (Thomas Lee) </para>
<para>
Previously this was only supported for <literal>ident</>
authentication.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Improve syslog performance by increasing the maximum line length Allow <literal>ident</> authentication over Unix-domain sockets
(Tom) on <productname>Solaris</> (Garick Hamlin)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add read-only <filename>postgresql.conf</> variables <varname>segment_size</>, Add <literal>clientcert</> option to control requesting of a
<varname>wal_block_size</>, and <varname>wal_segment_size</> (Bernd Helmle) client certificate (Magnus)
</para>
<para>
Previously this was controlled by the presence of a root
certificate file in the server's data directory.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
When reporting a deadlock, report all session queries involved Add <literal>cert</> authentication method to allow user
in the deadlock to the server log (Itagaki Takahiro) authentication via <acronym>SSL</> certificates (Magnus)
</para>
<para>
Previously <acronym>SSL</> certificates could only verify that
the client had access to a certificate, not authenticate a
user.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
New <function>pg_stat_get_activity(pid)</> function to return Allow <literal>krb5</>, <literal>gssapi</> and <literal>sspi</>
information about a specific process id (Magnus) realm and <literal>krb5</> host settings to be specified in
<filename>pg_hba.conf</> (Magnus)
</para>
<para>
These override the settings in <filename>postgresql.conf</>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Move the server statistics file into the subdirectory Add <literal>krb5</>, <literal>gssapi</>, and <literal>sspi</>
<filename>pg_stat_tmp</> and allow its location to be specified <varname>include_realm</> parameter (Magnus)
via <varname>stats_temp_directory</> (Magnus)
</para> </para>
<para> <para>
This allows the statistics file to be placed in a This allows identical usernames from different realms to be
<acronym>RAM</>-resident directory to reduce I/O requirements. authenticated as different database users using usermaps.
On startup/shutdown, the file is copied to the top-level </para>
<literal>$PGDATA</> directory so it is preserved between </listitem>
restarts.
<listitem>
<para>
Show all parsing errors instead of aborting after the first
one (Selena Deckelmann)
</para> </para>
</listitem> </listitem>
...@@ -738,137 +777,87 @@ do it for earlier branch release files. ...@@ -738,137 +777,87 @@ do it for earlier branch release files.
</sect3> </sect3>
<sect3> <sect3>
<title>Authentication</title> <title>Monitoring</title>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Report appropriate error message for combination of <literal>MD5</> Add <function>pg_conf_load_time()</> to report when
authentication and <varname>db_user_namespace</> enabled (Bruce) the Postgres configuration files were last loaded (George
</para> Gensure)
</listitem>
<listitem>
<para>
Support regular expressions in <filename>pg_ident.conf</>
(Magnus)
</para>
</listitem>
<listitem>
<para>
Allow <productname>Kerberos</>/<acronym>GSSAPI</> parameters
to be changed without restarting the postmaster (Magnus)
</para> </para>
</listitem> </listitem>
</itemizedlist>
</sect3>
<sect3>
<title><filename>pg_hba.conf</></title>
<itemizedlist>
<listitem> <listitem>
<para> <para>
Parse <filename>pg_hba.conf</> in the postmaster so errors are Add <function>pg_terminate_backend()</> to safely terminate a
reported on reload (Magnus) backend (the <literal>SIGTERM</> signal works also) (Tom, Bruce)
</para>
<para>
Previously errors in the file wouldn't be detected until clients
tried to connect, which could leave the system with a broken
file loaded.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Remove the <literal>sameuser</> option, making it the default Add ability to track user-defined functions call counts and
if no usermap is specified (Magnus) runtimes via parameter <varname>track_functions</> (Martin
Pihlak)
</para> </para>
</listitem>
<listitem>
<para> <para>
Change all authentication options to be <literal>name=value</> Function statistics appear in a new system table,
settings (Magnus) <literal>pg_stat_user_functions</>. However, inlined
<acronym>SQL</> functions are not tracked.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow usermap parameter for all external authentication methods Allow specification of the maximum <literal>pg_stat_activity</>
(Magnus) query string size via <varname>track_activity_query_size</>
</para> parameter (Thomas Lee)
<para>
Previously this was only supported for <literal>ident</>
authentication.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow <literal>ident</> authentication over Unix-domain sockets Improve syslog performance by increasing the maximum line length
on <productname>Solaris</> (Garick Hamlin) (Tom)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add <literal>clientcert</> option to control requesting of a Add read-only <filename>postgresql.conf</> variables <varname>segment_size</>,
client certificate (Magnus) <varname>wal_block_size</>, and <varname>wal_segment_size</> (Bernd Helmle)
</para>
<para>
Previously this was controlled by the presence of a root
certificate file in the server's data directory.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add <literal>cert</> authentication method to allow user When reporting a deadlock, report all session queries involved
authentication via <acronym>SSL</> certificates (Magnus) in the deadlock to the server log (Itagaki Takahiro)
</para>
<para>
Previously <acronym>SSL</> certificates could only verify that
the client had access to a certificate, not authenticate a
user.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow <literal>krb5</>, <literal>gssapi</> and <literal>sspi</> New <function>pg_stat_get_activity(pid)</> function to return
realm and <literal>krb5</> host settings to be specified in information about a specific process id (Magnus)
<filename>pg_hba.conf</> (Magnus)
</para>
<para>
These override the settings in <filename>postgresql.conf</>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add <literal>krb5</>, <literal>gssapi</>, and <literal>sspi</> Move the server statistics file into the subdirectory
<varname>include_realm</> parameter (Magnus) <filename>pg_stat_tmp</> and allow its location to be specified
</para> via <varname>stats_temp_directory</> (Magnus)
<para>
This allows identical usernames from different realms to be
authenticated as different database users using usermaps.
</para> </para>
</listitem>
<listitem>
<para> <para>
Show all parsing errors instead of aborting after the first This allows the statistics file to be placed in a
one (Selena Deckelmann) <acronym>RAM</>-resident directory to reduce I/O requirements.
On startup/shutdown, the file is copied to the top-level
<literal>$PGDATA</> directory so it is preserved between
restarts.
</para> </para>
</listitem> </listitem>
...@@ -979,8 +968,7 @@ do it for earlier branch release files. ...@@ -979,8 +968,7 @@ do it for earlier branch release files.
<listitem> <listitem>
<para> <para>
Improve the parser's ability to report the error location of Improve the parser's ability to report error locations (Tom)
a query (Tom)
</para> </para>
</listitem> </listitem>
...@@ -1683,6 +1671,35 @@ do it for earlier branch release files. ...@@ -1683,6 +1671,35 @@ do it for earlier branch release files.
</sect3> </sect3>
<sect3>
<title>Wide-Value Storage (<acronym>TOAST</>)</title>
<itemizedlist>
<listitem>
<para>
Consider <acronym>TOAST</> compression on values as short as
32 bytes (previously 256 bytes) (Tom)
</para>
</listitem>
<listitem>
<para>
Require 25% of space savings before using <acronym>TOAST</>
compression (previously 20%) (Tom)
</para>
</listitem>
<listitem>
<para>
Be more aggressive in storing <literal>EXTERNAL</> and
<literal>EXTENDED</> column values in <acronym>TOAST</>(Tom)
</para>
</listitem>
</itemizedlist>
</sect3>
<sect3> <sect3>
<title>General Functions</title> <title>General Functions</title>
<itemizedlist> <itemizedlist>
......
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