mirror of
https://github.com/postgres/postgres.git
synced 2025-05-17 06:41:24 +03:00
Update release notes for security releases.
Security: CVE-2007-4769, CVE-2007-4772, CVE-2007-6067, CVE-2007-6600, CVE-2007-6601
This commit is contained in:
Tom Lane
parent
1f42e1cb68
commit
63ee91fc45
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.235.2.58 2007/09/16 03:03:55 tgl Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.235.2.59 2008/01/03 21:36:15 tgl Exp $ -->
|
||||
<!--
|
||||
|
||||
Typical markup:
|
||||
@ -26,7 +26,7 @@ non-ASCII characters convert to HTML4 entity (&) escapes
|
||||
wrap long lines
|
||||
|
||||
For new features, add links to the documentation sections. Use </link>
|
||||
so that perl can remove it so HISTORY.html can be created with no
|
||||
so that Perl can remove it so HISTORY.html can be created with no
|
||||
links to the main documentation. This was added only in 8.2, so don't
|
||||
do it for earlier branch release files.
|
||||
|
||||
@ -35,6 +35,158 @@ do it for earlier branch release files.
|
||||
<appendix id="release">
|
||||
<title>Release Notes</title>
|
||||
|
||||
<sect1 id="release-7-4-19">
|
||||
<title>Release 7.4.19</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2008-01-07</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 7.4.18,
|
||||
including fixes for significant security issues.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to Version 7.4.19</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
if you are upgrading from a version earlier than 7.4.11, see the release
|
||||
notes for 7.4.11.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes</title>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Prevent functions in indexes from executing with the privileges of
|
||||
the user running <command>VACUUM</>, <command>ANALYZE</>, etc (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Functions used in index expressions and partial-index
|
||||
predicates are evaluated whenever a new table entry is made. It has
|
||||
long been understood that this poses a risk of trojan-horse code
|
||||
execution if one modifies a table owned by an untrustworthy user.
|
||||
(Note that triggers, defaults, check constraints, etc. pose the
|
||||
same type of risk.) But functions in indexes pose extra danger
|
||||
because they will be executed by routine maintenance operations
|
||||
such as <command>VACUUM FULL</>, which are commonly performed
|
||||
automatically under a superuser account. For example, a nefarious user
|
||||
can execute code with superuser privileges by setting up a
|
||||
trojan-horse index definition and waiting for the next routine vacuum.
|
||||
The fix arranges for standard maintenance operations
|
||||
(including <command>VACUUM</>, <command>ANALYZE</>, <command>REINDEX</>,
|
||||
and <command>CLUSTER</>) to execute as the table owner rather than
|
||||
the calling user, using the same privilege-switching mechanism already
|
||||
used for <literal>SECURITY DEFINER</> functions. To prevent bypassing
|
||||
this security measure, execution of <command>SET SESSION
|
||||
AUTHORIZATION</> and <command>SET ROLE</> is now forbidden within a
|
||||
<literal>SECURITY DEFINER</> context. (CVE-2007-6600)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Repair assorted bugs in the regular-expression package (Tom, Will Drewry)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Suitably crafted regular-expression patterns could cause crashes,
|
||||
infinite or near-infinite looping, and/or massive memory consumption,
|
||||
all of which pose denial-of-service hazards for applications that
|
||||
accept regex search patterns from untrustworthy sources.
|
||||
(CVE-2007-4769, CVE-2007-4772, CVE-2007-6067)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Require non-superusers who use <filename>/contrib/dblink</> to use only
|
||||
password authentication, as a security measure (Joe)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The fix that appeared for this in 7.4.18 was incomplete, as it plugged
|
||||
the hole for only some <filename>dblink</> functions. (CVE-2007-6601,
|
||||
CVE-2007-3278)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix planner failure in some cases of <literal>WHERE false AND var IN
|
||||
(SELECT ...)</> (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix potential crash in <function>translate()</> when using a multibyte
|
||||
database encoding (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix PL/Python to not crash on long exception messages (Alvaro)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<application>ecpg</> parser fixes (Michael)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Make <filename>contrib/tablefunc</>'s <function>crosstab()</> handle
|
||||
NULL rowid as a category in its own right, rather than crashing (Joe)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix <type>tsvector</> and <type>tsquery</> output routines to
|
||||
escape backslashes correctly (Teodor, Bruce)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix crash of <function>to_tsvector()</> on huge input strings (Teodor)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Require a specific version of <productname>Autoconf</> to be used
|
||||
when re-generating the <command>configure</> script (Peter)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This affects developers and packagers only. The change was made
|
||||
to prevent accidental use of untested combinations of
|
||||
<productname>Autoconf</> and <productname>PostgreSQL</> versions.
|
||||
You can remove the version check if you really want to use a
|
||||
different <productname>Autoconf</> version, but it's
|
||||
your responsibility whether the result works or not.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-4-18">
|
||||
<title>Release 7.4.18</title>
|
||||
|
||||
@ -48,7 +200,7 @@ do it for earlier branch release files.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.18</title>
|
||||
<title>Migration to Version 7.4.18</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -123,7 +275,7 @@ do it for earlier branch release files.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.17</title>
|
||||
<title>Migration to Version 7.4.17</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -192,7 +344,7 @@ do it for earlier branch release files.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.16</title>
|
||||
<title>Migration to Version 7.4.16</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -260,7 +412,7 @@ do it for earlier branch release files.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.15</title>
|
||||
<title>Migration to Version 7.4.15</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -347,7 +499,7 @@ do it for earlier branch release files.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.14</title>
|
||||
<title>Migration to Version 7.4.14</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -393,7 +545,7 @@ ANYARRAY</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.13</title>
|
||||
<title>Migration to Version 7.4.13</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -497,7 +649,7 @@ Fuhr)</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.12</title>
|
||||
<title>Migration to Version 7.4.12</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -558,7 +710,7 @@ and <function>isinf</> during configure (Tom)</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.11</title>
|
||||
<title>Migration to Version 7.4.11</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -623,7 +775,7 @@ what's actually returned by the query (Joe)</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.10</title>
|
||||
<title>Migration to Version 7.4.10</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -674,7 +826,7 @@ table has been dropped</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.9</title>
|
||||
<title>Migration to Version 7.4.9</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -742,7 +894,7 @@ code</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.8</title>
|
||||
<title>Migration to Version 7.4.8</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -924,7 +1076,7 @@ holder of the lock released it within a very narrow window.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.7</title>
|
||||
<title>Migration to Version 7.4.7</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X.
|
||||
@ -982,7 +1134,7 @@ GMT</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.6</title>
|
||||
<title>Migration to Version 7.4.6</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X.
|
||||
@ -1052,7 +1204,7 @@ ECPG prepare statement</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.5</title>
|
||||
<title>Migration to Version 7.4.5</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X.
|
||||
@ -1088,7 +1240,7 @@ still worth a re-release. The bug does not exist in pre-7.4 releases.
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.4</title>
|
||||
<title>Migration to Version 7.4.4</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X.
|
||||
@ -1138,7 +1290,7 @@ aggregate plan</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.3</title>
|
||||
<title>Migration to Version 7.4.3</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X.
|
||||
@ -1194,7 +1346,7 @@ names from outer query levels.
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.2</title>
|
||||
<title>Migration to Version 7.4.2</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.4.X. However,
|
||||
@ -1335,7 +1487,7 @@ inconveniences associated with the <literal>i/I</> problem.</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4.1</title>
|
||||
<title>Migration to Version 7.4.1</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -1715,7 +1867,7 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.4</title>
|
||||
<title>Migration to Version 7.4</title>
|
||||
|
||||
<para>
|
||||
A dump/restore using <application>pg_dump</application> is
|
||||
@ -3293,6 +3445,118 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-3-21">
|
||||
<title>Release 7.3.21</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2008-01-07</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 7.3.20,
|
||||
including fixes for significant security issues.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This is expected to be the last <productname>PostgreSQL</> release
|
||||
in the 7.3.X series. Users are encouraged to update to a newer
|
||||
release branch soon.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to Version 7.3.21</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
if you are upgrading from a version earlier than 7.3.13, see the release
|
||||
notes for 7.3.13.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes</title>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Prevent functions in indexes from executing with the privileges of
|
||||
the user running <command>VACUUM</>, <command>ANALYZE</>, etc (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Functions used in index expressions and partial-index
|
||||
predicates are evaluated whenever a new table entry is made. It has
|
||||
long been understood that this poses a risk of trojan-horse code
|
||||
execution if one modifies a table owned by an untrustworthy user.
|
||||
(Note that triggers, defaults, check constraints, etc. pose the
|
||||
same type of risk.) But functions in indexes pose extra danger
|
||||
because they will be executed by routine maintenance operations
|
||||
such as <command>VACUUM FULL</>, which are commonly performed
|
||||
automatically under a superuser account. For example, a nefarious user
|
||||
can execute code with superuser privileges by setting up a
|
||||
trojan-horse index definition and waiting for the next routine vacuum.
|
||||
The fix arranges for standard maintenance operations
|
||||
(including <command>VACUUM</>, <command>ANALYZE</>, <command>REINDEX</>,
|
||||
and <command>CLUSTER</>) to execute as the table owner rather than
|
||||
the calling user, using the same privilege-switching mechanism already
|
||||
used for <literal>SECURITY DEFINER</> functions. To prevent bypassing
|
||||
this security measure, execution of <command>SET SESSION
|
||||
AUTHORIZATION</> and <command>SET ROLE</> is now forbidden within a
|
||||
<literal>SECURITY DEFINER</> context. (CVE-2007-6600)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Require non-superusers who use <filename>/contrib/dblink</> to use only
|
||||
password authentication, as a security measure (Joe)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The fix that appeared for this in 7.3.20 was incomplete, as it plugged
|
||||
the hole for only some <filename>dblink</> functions. (CVE-2007-6601,
|
||||
CVE-2007-3278)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix potential crash in <function>translate()</> when using a multibyte
|
||||
database encoding (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Make <filename>contrib/tablefunc</>'s <function>crosstab()</> handle
|
||||
NULL rowid as a category in its own right, rather than crashing (Joe)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Require a specific version of <productname>Autoconf</> to be used
|
||||
when re-generating the <command>configure</> script (Peter)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This affects developers and packagers only. The change was made
|
||||
to prevent accidental use of untested combinations of
|
||||
<productname>Autoconf</> and <productname>PostgreSQL</> versions.
|
||||
You can remove the version check if you really want to use a
|
||||
different <productname>Autoconf</> version, but it's
|
||||
your responsibility whether the result works or not.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-3-20">
|
||||
<title>Release 7.3.20</title>
|
||||
|
||||
@ -3306,7 +3570,7 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.20</title>
|
||||
<title>Migration to Version 7.3.20</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3368,7 +3632,7 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.19</title>
|
||||
<title>Migration to Version 7.3.19</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3424,7 +3688,7 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.18</title>
|
||||
<title>Migration to Version 7.3.18</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3485,7 +3749,7 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.17</title>
|
||||
<title>Migration to Version 7.3.17</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3541,7 +3805,7 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.16</title>
|
||||
<title>Migration to Version 7.3.16</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3584,7 +3848,7 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.15</title>
|
||||
<title>Migration to Version 7.3.15</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3675,7 +3939,7 @@ Fuhr)</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.14</title>
|
||||
<title>Migration to Version 7.3.14</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3732,7 +3996,7 @@ and <function>isinf</> during configure (Tom)</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.13</title>
|
||||
<title>Migration to Version 7.3.13</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3794,7 +4058,7 @@ what's actually returned by the query (Joe)</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.12</title>
|
||||
<title>Migration to Version 7.3.12</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3841,7 +4105,7 @@ table has been dropped</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.11</title>
|
||||
<title>Migration to Version 7.3.11</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -3893,7 +4157,7 @@ the variable is of pass-by-reference type</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.10</title>
|
||||
<title>Migration to Version 7.3.10</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X. However,
|
||||
@ -4019,7 +4283,7 @@ month-related formats</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.9</title>
|
||||
<title>Migration to Version 7.3.9</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X.
|
||||
@ -4075,7 +4339,7 @@ datestyles</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.8</title>
|
||||
<title>Migration to Version 7.3.8</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X.
|
||||
@ -4125,7 +4389,7 @@ concern since there is no reason for non-developers to use this script anyway.
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.7</title>
|
||||
<title>Migration to Version 7.3.7</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.3.X.
|
||||
@ -4165,7 +4429,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.6</title>
|
||||
<title>Migration to Version 7.3.6</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -4230,7 +4494,7 @@ operations on bytea columns (Joe)</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.5</title>
|
||||
<title>Migration to Version 7.3.5</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -4281,7 +4545,7 @@ operations on bytea columns (Joe)</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.4</title>
|
||||
<title>Migration to Version 7.3.4</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -4320,7 +4584,7 @@ operations on bytea columns (Joe)</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.3</title>
|
||||
<title>Migration to Version 7.3.3</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -4431,7 +4695,7 @@ operations on bytea columns (Joe)</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.2</title>
|
||||
<title>Migration to Version 7.3.2</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -4492,7 +4756,7 @@ operations on bytea columns (Joe)</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3.1</title>
|
||||
<title>Migration to Version 7.3.1</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -4661,7 +4925,7 @@ operations on bytea columns (Joe)</para></listitem>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.3</title>
|
||||
<title>Migration to Version 7.3</title>
|
||||
|
||||
<para>
|
||||
A dump/restore using <application>pg_dump</> is required for those
|
||||
@ -5178,7 +5442,7 @@ operations on bytea columns (Joe)</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.2.8</title>
|
||||
<title>Migration to Version 7.2.8</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.2.X.
|
||||
@ -5229,7 +5493,7 @@ month-related formats</para></listitem>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.2.7</title>
|
||||
<title>Migration to Version 7.2.7</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.2.X.
|
||||
@ -5277,7 +5541,7 @@ datestyles</para></listitem>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.2.6</title>
|
||||
<title>Migration to Version 7.2.6</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.2.X.
|
||||
@ -5328,7 +5592,7 @@ concern since there is no reason for non-developers to use this script anyway.
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.2.5</title>
|
||||
<title>Migration to Version 7.2.5</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 7.2.X.
|
||||
@ -5371,7 +5635,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.2.4</title>
|
||||
<title>Migration to Version 7.2.4</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -5410,7 +5674,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.2.3</title>
|
||||
<title>Migration to Version 7.2.3</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -5446,7 +5710,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.2.2</title>
|
||||
<title>Migration to Version 7.2.2</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -5489,7 +5753,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.2.1</title>
|
||||
<title>Migration to Version 7.2.1</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those
|
||||
@ -5620,7 +5884,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.2</title>
|
||||
<title>Migration to Version 7.2</title>
|
||||
|
||||
<para>
|
||||
A dump/restore using <command>pg_dump</command> is required for
|
||||
@ -6087,7 +6351,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
||||
</note>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.1.3</title>
|
||||
<title>Migration to Version 7.1.3</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -6130,7 +6394,7 @@ Cygwin build (Jason Tishler)
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.1.2</title>
|
||||
<title>Migration to Version 7.1.2</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -6168,7 +6432,7 @@ pg_dump cleanups
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.1.1</title>
|
||||
<title>Migration to Version 7.1.1</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -6295,7 +6559,7 @@ Subqueries in FROM are now supported.
|
||||
</variablelist>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.1</title>
|
||||
<title>Migration to Version 7.1</title>
|
||||
|
||||
<para>
|
||||
A dump/restore using pg_dump is required for those wishing to migrate
|
||||
@ -6513,7 +6777,7 @@ New FreeBSD tools ipc_check, start-scripts/freebsd
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.0.3</title>
|
||||
<title>Migration to Version 7.0.3</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -6585,7 +6849,7 @@ Fix for crash of backend, on abort (Tom)
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.0.2</title>
|
||||
<title>Migration to Version 7.0.2</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -6618,7 +6882,7 @@ Added documentation to tarball.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.0.1</title>
|
||||
<title>Migration to Version 7.0.1</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -6653,7 +6917,7 @@ Copy pg_ident.conf.sample into /lib directory in install (Bruce)
|
||||
Add SJIS UDC (NEC selection IBM kanji) support (Eiji Tokuya)
|
||||
Fix too long syslog message (Tatsuo)
|
||||
Fix problem with quoted indexes that are too long (Tom)
|
||||
JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu)
|
||||
JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu)
|
||||
ecpg changes (Michael)
|
||||
</programlisting>
|
||||
</para>
|
||||
@ -6738,7 +7002,7 @@ ecpg changes (Michael)
|
||||
</variablelist>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.0</title>
|
||||
<title>Migration to Version 7.0</title>
|
||||
|
||||
<para>
|
||||
A dump/restore using <application>pg_dump</application>
|
||||
@ -7144,7 +7408,7 @@ New multibyte encodings
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 6.5.3</title>
|
||||
<title>Migration to Version 6.5.3</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -7180,7 +7444,7 @@ Fix dumping rules on inherited tables
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 6.5.2</title>
|
||||
<title>Migration to Version 6.5.2</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -7236,7 +7500,7 @@ Updated version of pgaccess 0.98
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 6.5.1</title>
|
||||
<title>Migration to Version 6.5.1</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -7435,7 +7699,7 @@ Add Win1250 (Czech) support (Pavel Behal)
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 6.5</title>
|
||||
<title>Migration to Version 6.5</title>
|
||||
|
||||
<para>
|
||||
A dump/restore using <application>pg_dump</application>
|
||||
@ -7692,7 +7956,7 @@ bug fix.
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 6.4.2</title>
|
||||
<title>Migration to Version 6.4.2</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -7727,7 +7991,7 @@ problems reported by 6.4 users.
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 6.4.1</title>
|
||||
<title>Migration to Version 6.4.1</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is <emphasis>not</emphasis> required for those running
|
||||
@ -7861,7 +8125,7 @@ been.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 6.4</title>
|
||||
<title>Migration to Version 6.4</title>
|
||||
|
||||
<para>
|
||||
A dump/restore using <application>pg_dump</application>
|
||||
@ -8357,7 +8621,7 @@ Better identify tcl and tk libs and includes(Bruce)
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 6.3</title>
|
||||
<title>Migration to Version 6.3</title>
|
||||
|
||||
<para>
|
||||
A dump/restore using <application>pg_dump</application>
|
||||
@ -8505,7 +8769,7 @@ Source Tree Changes
|
||||
Add new html development tools, and flow chart in /tools/backend
|
||||
Fix for SCO compiles
|
||||
Stratus computer port Robert Gillies
|
||||
Added support for shlib for BSD44_derived & i386_solaris
|
||||
Added support for shlib for BSD44_derived & i386_solaris
|
||||
Make configure more automated(Brook)
|
||||
Add script to check regression test results
|
||||
Break parser functions into smaller files, group together(Bruce)
|
||||
@ -8691,7 +8955,7 @@ Enhancements
|
||||
------------
|
||||
Default genetic optimizer GEQO parameter is now 8(Bruce)
|
||||
Allow use parameters in target list having aggregates in functions(Vadim)
|
||||
Added JDBC driver as an interface(Adrian & Peter)
|
||||
Added JDBC driver as an interface(Adrian & Peter)
|
||||
pg_password utility
|
||||
Return number of rows inserted/affected by INSERT/UPDATE/DELETE etc.(Vadim)
|
||||
Triggers implemented with CREATE TRIGGER (SQL3)(Vadim)
|
||||
@ -8702,7 +8966,7 @@ Include reserved words for string handling, outer joins, and unions(Thomas)
|
||||
Implement extended comments ("/* ... */") using exclusive states(Thomas)
|
||||
Add "//" single-line comments(Bruce)
|
||||
Remove some restrictions on characters in operator names(Thomas)
|
||||
DEFAULT and CONSTRAINT for tables implemented (SQL92)(Vadim & Thomas)
|
||||
DEFAULT and CONSTRAINT for tables implemented (SQL92)(Vadim & Thomas)
|
||||
Add text concatenation operator and function (SQL92)(Thomas)
|
||||
Support WITH TIME ZONE syntax (SQL92)(Thomas)
|
||||
Support INTERVAL unit TO unit syntax (SQL92)(Thomas)
|
||||
@ -8724,7 +8988,7 @@ Replace distance operator "<===>" with "<->"(Thomas)
|
||||
Replace "above" operator "!^" with ">^" and "below" operator "!|" with "<^"(Thomas)
|
||||
Add routines for text trimming on both ends, substring, and string position(Thomas)
|
||||
Added conversion routines circle(box) and poly(circle)(Thomas)
|
||||
Allow internal sorts to be stored in memory rather than in files(Bruce & Vadim)
|
||||
Allow internal sorts to be stored in memory rather than in files(Bruce & Vadim)
|
||||
Allow functions and operators on internally-identical types to succeed(Bruce)
|
||||
Speed up backend start-up after profiling analysis(Bruce)
|
||||
Inline frequently called functions for performance(Bruce)
|
||||
@ -8757,7 +9021,7 @@ new interfaces directory(Marc)
|
||||
Replace fopen() calls with calls to fd.c functions(Bruce)
|
||||
Make functions static where possible(Bruce)
|
||||
enclose unused functions in #ifdef NOT_USED(Bruce)
|
||||
Remove call to difftime() in timestamp support to fix SunOS(Bruce & Thomas)
|
||||
Remove call to difftime() in timestamp support to fix SunOS(Bruce & Thomas)
|
||||
Changes for Digital Unix
|
||||
Portability fix for pg_dumpall(Bruce)
|
||||
Rename pg_attribute.attnvals to attdispersion(Bruce)
|
||||
@ -8765,12 +9029,12 @@ Rename pg_attribute.attnvals to attdispersion(Bruce)
|
||||
"built-in" manual page now "pgbuiltin"(Bruce)
|
||||
"drop" manual page now "drop_table"(Bruce)
|
||||
Add "create_trigger", "drop_trigger" manual pages(Thomas)
|
||||
Add constraints regression test(Vadim & Thomas)
|
||||
Add constraints regression test(Vadim & Thomas)
|
||||
Add comments syntax regression test(Thomas)
|
||||
Add PGINDENT and support program(Bruce)
|
||||
Massive commit to run PGINDENT on all *.c and *.h files(Bruce)
|
||||
Files moved to /src/tools directory(Bruce)
|
||||
SPI and Trigger programming guides (Vadim & D'Arcy)
|
||||
SPI and Trigger programming guides (Vadim & D'Arcy)
|
||||
</programlisting>
|
||||
</para>
|
||||
</sect2>
|
||||
@ -8877,7 +9141,7 @@ optimizer which uses <firstterm>genetic</firstterm>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 6.1</title>
|
||||
<title>Migration to Version 6.1</title>
|
||||
|
||||
<para>
|
||||
This migration requires a complete dump of the 6.0 database and a
|
||||
@ -9077,7 +9341,7 @@ Allow libpq to distinguish between text value '' and null(Bruce)
|
||||
Allow non-postgres users with createdb privs to destroydb's
|
||||
Allow restriction on who can create C functions(Bryan)
|
||||
Allow restriction on who can do backend COPY(Bryan)
|
||||
Can shrink tables, pg_time and pg_log(Vadim & Erich)
|
||||
Can shrink tables, pg_time and pg_log(Vadim & Erich)
|
||||
Change debug level 2 to print queries only, changed debug heading layout(Bruce)
|
||||
Change default decimal constant representation from float4 to float8(Bruce)
|
||||
European date format now set when postmaster is started
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user