Commit de8113fc authored by Tom Lane's avatar Tom Lane

Update release notes for recent changes; also minor editorialization.

parent 294c34bb
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.311 2004/11/22 00:37:59 tgl Exp $
--> -->
<appendix id="release"> <appendix id="release">
...@@ -10,7 +10,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp ...@@ -10,7 +10,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<note> <note>
<title>Release date</title> <title>Release date</title>
<simpara>2004-??-??, current as of 2004-11-06</simpara> <simpara>2004-??-??, current as of 2004-11-21</simpara>
</note> </note>
<sect2> <sect2>
...@@ -352,8 +352,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp ...@@ -352,8 +352,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<para> <para>
Syntax checking of array input values has been tightened up Syntax checking of array input values has been tightened up
considerably. Junk that was previously allowed in odd places with considerably. Junk that was previously allowed in odd places with
odd results now causes an <literal>ERROR. Empty-string element odd results now causes an error. Empty-string element values
values must now be written as ""</>, rather than writing nothing. must now be written as <literal>""</>, rather than writing nothing.
Also changed behavior with respect to whitespace surrounding Also changed behavior with respect to whitespace surrounding
array elements: trailing whitespace is now ignored, for symmetry array elements: trailing whitespace is now ignored, for symmetry
with leading whitespace (which has always been ignored). with leading whitespace (which has always been ignored).
...@@ -610,7 +610,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp ...@@ -610,7 +610,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
(Manfred Koizar) (Manfred Koizar)
</para> </para>
<para> <para>
This gives better statistics for asymmetric data distributions. This gives better statistics when the density of valid rows is very
different in different regions of a table.
</para> </para>
</listitem> </listitem>
...@@ -765,12 +766,24 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp ...@@ -765,12 +766,24 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Some logging-related configuration parameters could formerly be adjusted
by ordinary users, but only in the <quote>more verbose</> direction.
They are now treated more strictly: only superusers can set them.
However, a superuser may use <command>ALTER USER</> to provide per-user
settings of these values for non-superusers. Also, it is now possible
for superusers to set values of superuser-only configuration parameters
via <literal>PGOPTIONS</>.
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Allow configuration files to be placed outside the data directory (mlw) Allow configuration files to be placed outside the data directory (mlw)
</para> </para>
<para> <para>
By default, configuration files sit in the top server directory. By default, configuration files are kept in the cluster's top directory.
With this addition, configuration files can be placed outside the With this addition, configuration files can be placed outside the
data directory, easing administration. data directory, easing administration.
</para> </para>
...@@ -1070,7 +1083,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp ...@@ -1070,7 +1083,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
columns (Tom) columns (Tom)
</para> </para>
<para> <para>
This is related to the new capability of adding defaults for new This falls out from the new capability of specifying defaults for new
columns. columns.
</para> </para>
</listitem> </listitem>
...@@ -1141,7 +1154,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp ...@@ -1141,7 +1154,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<listitem> <listitem>
<para> <para>
Have <command>ALTER TABLE OWNER</> change dependent sequence Make <command>ALTER TABLE OWNER</> change dependent sequence
ownership too (Alvaro) ownership too (Alvaro)
</para> </para>
</listitem> </listitem>
...@@ -1471,7 +1484,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp ...@@ -1471,7 +1484,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<listitem> <listitem>
<para> <para>
Fix <function>to_char(year)</> for BC dates (previously it Fix <function>date_part(year)</> for BC dates (previously it
returned one less than the correct year) (Bruce) returned one less than the correct year) (Bruce)
</para> </para>
</listitem> </listitem>
...@@ -1831,6 +1844,10 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp ...@@ -1831,6 +1844,10 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
Use dependency information to improve the reliability of Use dependency information to improve the reliability of
<application>pg_dump</> (Tom) <application>pg_dump</> (Tom)
</para> </para>
<para>
This should solve the longstanding problems with related objects
sometimes being dumped in the wrong order.
</para>
</listitem> </listitem>
<listitem> <listitem>
...@@ -1937,15 +1954,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp ...@@ -1937,15 +1954,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<listitem> <listitem>
<para> <para>
Many ecpg improvements, including <command>SET DESCRIPTOR</> (Michael) Add <function>PQprepare/PQsendPrepared()</> functions to support
preparing statements without necessarily specifying the data types
of their parameters (Abhijit Menon-Sen)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Add <function>PQprepare/PQsendPrepared()</> functions to support Many ecpg improvements, including <command>SET DESCRIPTOR</> (Michael)
preparing statements without necessarily specifying the data types
of their parameters (Abhijit Menon-Sen)
</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