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

Split release notes up into smaller sections; easier to read.

parent e66d0c62
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.553 2007/11/20 05:23:20 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.554 2007/11/20 17:10:25 momjian Exp $ -->
<!--
Typical markup:
......@@ -232,6 +232,8 @@ do it for earlier branch release files.
Observe the following incompatibilities:
</para>
<sect3>
<title>General</title>
<itemizedlist>
<listitem>
......@@ -300,43 +302,23 @@ current_date &lt; 2017-11-17
<listitem>
<para>
Numerous changes in administrative server parameters
</para>
<para>
<varname>bgwriter_lru_percent</>,
<varname>bgwriter_all_percent</>,
<varname>bgwriter_all_maxpages</>,
<varname>stats_start_collector</>, and
<varname>stats_reset_on_server_start</> are removed.
<varname>redirect_stderr</> is renamed to
<varname>logging_collector</>.
<varname>stats_command_string</> is renamed to
<varname>track_activities</>.
<varname>stats_block_level</> and <varname>stats_row_level</>
are merged into <varname>track_counts</>.
A new boolean configuration parameter, <varname>archive_mode</>,
controls archiving. Autovacuum's default settings have changed.
<literal>ARRAY(SELECT ...)</literal>, where the <command>SELECT</>
returns no rows, now returns an empty array, rather than NULL
(Tom)
</para>
</listitem>
<listitem>
<para>
Commenting out a parameter in <filename>postgresql.conf</> now
causes it to revert to its default value (Joachim Wieland)
</para>
<para>
Previously, commenting out an entry left the parameter's value unchanged
until the next server restart.
The array type name for a base data type is no longer always the base
type's name with an underscore prefix
</para>
</listitem>
<listitem>
<para>
<literal>ARRAY(SELECT ...)</literal>, where the <command>SELECT</>
returns no rows, now returns an empty array, rather than NULL
(Tom)
The old naming convention is still honored when possible, but
application code should no longer depend on it. Instead
use the new <literal>pg_type.typarray</literal> column to
identify the array data type associated with a given type.
</para>
</listitem>
......@@ -352,20 +334,6 @@ current_date &lt; 2017-11-17
</para>
</listitem>
<listitem>
<para>
The array type name for a base data type is no longer always the base
type's name with an underscore prefix
</para>
<para>
The old naming convention is still honored when possible, but
application code should no longer depend on it. Instead
use the new <literal>pg_type.typarray</literal> column to
identify the array data type associated with a given type.
</para>
</listitem>
<listitem>
<para>
<command>SET LOCAL</command> changes now persist until
......@@ -410,6 +378,25 @@ current_date &lt; 2017-11-17
</para>
</listitem>
<listitem>
<para>
<command>ALTER SEQUENCE</> no longer affects <function>currval()</>
(Tom)
</para>
</listitem>
<listitem>
<para>
Foreign keys now must match indexable conditions for
cross-data-type references (Tom)
</para>
<para>
This improves semantic consistency and helps avoid
performance problems.
</para>
</listitem>
<listitem>
<para>
Restrict object size functions to users who have reasonable
......@@ -427,43 +414,69 @@ current_date &lt; 2017-11-17
<listitem>
<para>
Internal hashing functions are now more uniformly-distributed (Tom)
Remove the undocumented <literal>!!=</> (not in) operator (Tom)
</para>
<para>
If application code was computing and storing hash values using
internal <productname>PostgreSQL</> hashing functions, the hash
values must be regenerated.
<literal>NOT IN (SELECT ...)</literal> is the proper way to
perform this operation.
</para>
</listitem>
<listitem>
<para>
<command>ALTER SEQUENCE</> no longer affects <function>currval()</>
(Tom)
Internal hashing functions are now more uniformly-distributed (Tom)
</para>
<para>
If application code was computing and storing hash values using
internal <productname>PostgreSQL</> hashing functions, the hash
values must be regenerated.
</para>
</listitem>
<listitem>
<para>
Foreign keys now must match indexable conditions for
cross-data-type references (Tom)
C-code conventions for handling variable-length data values
have changed (Greg Stark, Tom)
</para>
<para>
This improves semantic consistency and helps avoid
performance problems.
The new <function>SET_VARSIZE()</> macro <emphasis>must</> be used
to set the length of generated <type>varlena</> values. Also, it
might be necessary to expand (<quote>de-TOAST</quote>) input values
in more cases.
</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Configuration Parameters</title>
<itemizedlist>
<listitem>
<para>
Remove the undocumented <literal>!!=</> (not in) operator (Tom)
Numerous changes in administrative server parameters
</para>
<para>
<literal>NOT IN (SELECT ...)</literal> is the proper way to
perform this operation.
<varname>bgwriter_lru_percent</>,
<varname>bgwriter_all_percent</>,
<varname>bgwriter_all_maxpages</>,
<varname>stats_start_collector</>, and
<varname>stats_reset_on_server_start</> are removed.
<varname>redirect_stderr</> is renamed to
<varname>logging_collector</>.
<varname>stats_command_string</> is renamed to
<varname>track_activities</>.
<varname>stats_block_level</> and <varname>stats_row_level</>
are merged into <varname>track_counts</>.
A new boolean configuration parameter, <varname>archive_mode</>,
controls archiving. Autovacuum's default settings have changed.
</para>
</listitem>
......@@ -491,24 +504,23 @@ current_date &lt; 2017-11-17
<listitem>
<para>
C-code conventions for handling variable-length data values
have changed (Greg Stark, Tom)
Commenting out a parameter in <filename>postgresql.conf</> now
causes it to revert to its default value (Joachim Wieland)
</para>
<para>
The new <function>SET_VARSIZE()</> macro <emphasis>must</> be used
to set the length of generated <type>varlena</> values. Also, it
might be necessary to expand (<quote>de-TOAST</quote>) input values
in more cases.
Previously, commenting out an entry left the parameter's value unchanged
until the next server restart.
</para>
</listitem>
</itemizedlist>
</sect3>
<para>
The following incompatibilities relate to character encodings:
</para>
<sect3>
<title>Character Encodings</title>
<itemizedlist>
......@@ -603,6 +615,8 @@ current_date &lt; 2017-11-17
</itemizedlist>
</sect3>
</sect2>
<sect2>
......@@ -888,6 +902,14 @@ current_date &lt; 2017-11-17
</para>
</listitem>
<listitem>
<para>
Change server startup log message from <quote>database system is
ready</quote> to <quote>database system is ready to accept
connections</quote>
</para>
</listitem>
</itemizedlist>
</sect3>
......@@ -1034,6 +1056,13 @@ current_date &lt; 2017-11-17
</para>
</listitem>
<listitem>
<para>
Fix pgstats counting of live and dead tuples to recognize that
committed and aborted transactions have different effects (Tom)
</para>
</listitem>
</itemizedlist>
</sect3>
......@@ -2128,17 +2157,9 @@ current_date &lt; 2017-11-17
</sect3>
<sect3>
<title>Source Code</title>
<title>Server Programming Interface (<acronym>SPI</>)</title>
<itemizedlist>
<listitem>
<para>
Rename macro <literal>DLLIMPORT</> to <literal>PGDLLIMPORT</> to
avoid conflicting with third party includes (like Tcl) that
define <literal>DLLIMPORT</> (Magnus)
</para>
</listitem>
<listitem>
<para>
Allow execution of cursor commands through
......@@ -2174,6 +2195,14 @@ current_date &lt; 2017-11-17
</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Build Options</title>
<itemizedlist>
<listitem>
<para>
Add <application>configure</> <literal>--enable-profiling</>
......@@ -2191,8 +2220,9 @@ current_date &lt; 2017-11-17
<listitem>
<para>
Create <quote>operator families</quote> to improve planning of
queries involving cross-data-type comparisons (Tom)
Fix <acronym>PGXS</> so extensions can be built against PostgreSQL
installations whose <application>pg_config</> program does not
appear first in the <varname>PATH</> (Tom)
</para>
</listitem>
......@@ -2203,42 +2233,50 @@ current_date &lt; 2017-11-17
</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Source Code</title>
<itemizedlist>
<listitem>
<para>
Update GIN <function>extractQuery()</> API to allow signalling
that nothing can satisfy the query (Teodor)
Rename macro <literal>DLLIMPORT</> to <literal>PGDLLIMPORT</> to
avoid conflicting with third party includes (like Tcl) that
define <literal>DLLIMPORT</> (Magnus)
</para>
</listitem>
<listitem>
<para>
Move <literal>NAMEDATALEN</> definition from
<filename>postgres_ext.h</> to <filename>pg_config_manual.h</>
(Peter)
Create <quote>operator families</quote> to improve planning of
queries involving cross-data-type comparisons (Tom)
</para>
</listitem>
<listitem>
<para>
Change server startup log message from <quote>database system is
ready</quote> to <quote>database system is ready to accept
connections</quote>
Update GIN <function>extractQuery()</> API to allow signalling
that nothing can satisfy the query (Teodor)
</para>
</listitem>
<listitem>
<para>
Provide <function>strlcpy()</function> and
<function>strlcat()</function> on all platforms, and replace
error-prone uses of <function>strncpy()</function>,
<function>strncat()</function>, etc (Peter)
Move <literal>NAMEDATALEN</> definition from
<filename>postgres_ext.h</> to <filename>pg_config_manual.h</>
(Peter)
</para>
</listitem>
<listitem>
<para>
Fix pgstats counting of live and dead tuples to recognize that
committed and aborted transactions have different effects (Tom)
Provide <function>strlcpy()</function> and
<function>strlcat()</function> on all platforms, and replace
error-prone uses of <function>strncpy()</function>,
<function>strncat()</function>, etc (Peter)
</para>
</listitem>
......@@ -2266,20 +2304,12 @@ current_date &lt; 2017-11-17
<listitem>
<para>
Have <function>quote_identifier()</function> and
<application>pg_dump</application> not quote keywords that are
<function>quote_identifier()</function> and
<application>pg_dump</application> no longer quote keywords that are
unreserved according to the grammar (Tom)
</para>
</listitem>
<listitem>
<para>
Fix <acronym>PGXS</> so extensions can be built against PostgreSQL
installations whose <application>pg_config</> program does not
appear first in the <varname>PATH</> (Tom)
</para>
</listitem>
<listitem>
<para>
Change the on-disk representation of the <type>NUMERIC</type>
......
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