mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update release notes for 7.3.6.

Browse Source
This commit is contained in:
Tom Lane 2004-03-02 00:38:46 +00:00
parent 3811d7a08f
commit 340d44686b
2 changed files with 560 additions and 452 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

211
HISTORY
View File

@ -8,7 +8,7 @@
This release contains a variety of fixes from 7.4.
_________________________________________________________________
Migration to version 7.4.1
Migration to version 7.4.1
A dump/restore is *not* required for those running 7.4.
@ -23,7 +23,7 @@ DROP SCHEMA information_schema CASCADE;
Substitute your installation path in the second command.
_________________________________________________________________
Changes
Changes
* Fixed bug in "CREATE SCHEMA" parsing in ECPG (Michael)
* Fix compile error when "--enable-thread-safety" and "--with-perl"
@ -86,7 +86,7 @@ Changes
Release date: 2003-11-17
_________________________________________________________________
Overview
Overview
Major changes in this release:
@ -187,7 +187,7 @@ Overview
more like fully-supported data types.
_________________________________________________________________
Migration to version 7.4
Migration to version 7.4
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release.
@ -251,7 +251,7 @@ Migration to version 7.4
adjacent to operators.
_________________________________________________________________
Changes
Changes
Below you will find a detailed account of the changes between release
7.4 and the previous major release.
@ -847,6 +847,49 @@ Contrib Changes
* Remove array module because features now included by default (Joe)
_________________________________________________________________
Release 7.3.6
Release date: 2004-03-02
This release contains a variety of fixes from 7.3.5.
_________________________________________________________________
Migration to version 7.3.6
A dump/restore is *not* required for those running 7.3.*.
_________________________________________________________________
Changes
* Revert erroneous changes in rule permissions checking
A patch applied in 7.3.3 to fix a corner case in rule permissions
checks turns out to have disabled rule-related permissions checks
in many not-so-corner cases. This would for example allow users to
insert into views they weren't supposed to have permission to
insert into. We have therefore reverted the 7.3.3 patch. The
original bug will be fixed in 7.5.
* Repair incorrect order of operations in GetNewTransactionId()
This bug could result in failure under out-of-disk-space
conditions, including inability to restart even after disk space
is freed.
* Ensure configure selects -fno-strict-aliasing even when an
external value for CFLAGS is supplied
On some platforms, building with -fstrict-aliasing causes bugs.
* Make pg_restore handle 64-bit off_t correctly
This bug prevented proper restoration from archive files exceeding
4Gb.
* Make contrib/dblink not assume that local and remote type OIDs
match (Joe)
* Quote connectby()'s start_with argument properly (Joe)
* Don't crash when a rowtype argument to a plpgsql function is NULL
* Avoid generating invalid character encoding sequences in corner
cases when planning LIKE operations
* Ensure text_position() cannot scan past end of source string in
multibyte cases (Korea PostgreSQL Users' Group)
* Fix index optimization and selectivity estimates for LIKE
operations on bytea columns (Joe)
_________________________________________________________________
Release 7.3.5
Release date: 2003-12-03
@ -854,12 +897,12 @@ Contrib Changes
This has a variety of fixes from 7.3.4.
_________________________________________________________________
Migration to version 7.3.5
Migration to version 7.3.5
A dump/restore is *not* required for those running 7.3.*.
_________________________________________________________________
Changes
Changes
* Force zero_damaged_pages to be on during recovery from WAL
* Prevent some obscure cases of "variable not in subplan target
@ -901,12 +944,12 @@ Changes
This has a variety of fixes from 7.3.3.
_________________________________________________________________
Migration to version 7.3.4
Migration to version 7.3.4
A dump/restore is *not* required for those running 7.3.*.
_________________________________________________________________
Changes
Changes
* Repair breakage in timestamp-to-date conversion for dates before
2000
@ -925,15 +968,15 @@ Changes
Release date: 2003-05-22
This release contains of variety of fixes for version 7.3.2.
This release contains a variety of fixes for version 7.3.2.
_________________________________________________________________
Migration to version 7.3.3
Migration to version 7.3.3
A dump/restore is *not* required for those running version 7.3.*.
_________________________________________________________________
Changes
Changes
* Repair sometimes-incorrect computation of StartUpID after a crash
* Avoid slowness with lots of deferred triggers in one transaction
@ -1051,12 +1094,12 @@ Changes
This release contains a variety of fixes for version 7.3.1.
_________________________________________________________________
Migration to version 7.3.2
Migration to version 7.3.2
A dump/restore is *not* required for those running version 7.3.*.
_________________________________________________________________
Changes
Changes
* Restore creation of OID column in CREATE TABLE AS / SELECT INTO
* Fix pg_dump core dump when dumping views having comments
@ -1107,7 +1150,7 @@ Changes
This release contains a variety of fixes for version 7.3.
_________________________________________________________________
Migration to version 7.3.1
Migration to version 7.3.1
A dump/restore is *not* required for those running version 7.3.
However, it should be noted that the main PostgreSQL interface
@ -1115,7 +1158,7 @@ Migration to version 7.3.1
may require recompilation of client code in certain cases.
_________________________________________________________________
Changes
Changes
* Fix a core dump of COPY TO when client/server encodings don't
match (Tom)
@ -1143,7 +1186,7 @@ Changes
Release date: 2002-11-27
_________________________________________________________________
Overview
Overview
Major changes in this release:
@ -1198,7 +1241,7 @@ Overview
result types.
_________________________________________________________________
Migration to version 7.3
Migration to version 7.3
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release. If your application examines the
@ -1233,7 +1276,7 @@ Migration to version 7.3
integer field. Formerly, it was silently interpreted as 0.
_________________________________________________________________
Changes
Changes
Server Operation
@ -1691,12 +1734,12 @@ Contrib
fixes to prevent possible data loss.
_________________________________________________________________
Migration to version 7.2.4
Migration to version 7.2.4
A dump/restore is *not* required for those running version 7.2.*.
_________________________________________________________________
Changes
Changes
* Fix some additional cases of VACUUM "No one parent tuple was
found" error
@ -1722,12 +1765,12 @@ Changes
fixes to prevent possible data loss.
_________________________________________________________________
Migration to version 7.2.3
Migration to version 7.2.3
A dump/restore is *not* required for those running version 7.2.*.
_________________________________________________________________
Changes
Changes
* Prevent possible compressed transaction log loss (Tom)
* Prevent non-superuser from increasing most recent vacuum info
@ -1745,12 +1788,12 @@ Changes
This release contains a variety of fixes for version 7.2.1.
_________________________________________________________________
Migration to version 7.2.2
Migration to version 7.2.2
A dump/restore is *not* required for those running version 7.2.*.
_________________________________________________________________
Changes
Changes
* Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)
* Fix for compressed transaction log id wraparound (Tom)
@ -1776,12 +1819,12 @@ Changes
This release contains a variety of fixes for version 7.2.
_________________________________________________________________
Migration to version 7.2.1
Migration to version 7.2.1
A dump/restore is *not* required for those running version 7.2.
_________________________________________________________________
Changes
Changes
* Ensure that sequence counters do not go backwards after a crash
(Tom)
@ -1811,7 +1854,7 @@ Changes
Release date: 2002-02-04
_________________________________________________________________
Overview
Overview
This release improves PostgreSQL for use in high-volume applications.
@ -1849,7 +1892,7 @@ Overview
languages.
_________________________________________________________________
Migration to version 7.2
Migration to version 7.2
A dump/restore using "pg_dump" is required for those wishing to
migrate data from any previous release.
@ -1878,7 +1921,7 @@ Migration to version 7.2
clauses, e.g. LIMIT 10 OFFSET 20.
_________________________________________________________________
Changes
Changes
Server Operation
@ -2277,12 +2320,12 @@ Contrib
Release date: 2001-08-15
_________________________________________________________________
Migration to version 7.1.3
Migration to version 7.1.3
A dump/restore is *not* required for those running 7.1.X.
_________________________________________________________________
Changes
Changes
Remove unused WAL segements of large transactions (Tom)
Multiaction rule fix (Tom)
@ -2304,12 +2347,12 @@ Cygwin build (Jason Tishler)
This has one fix from 7.1.1.
_________________________________________________________________
Migration to version 7.1.2
Migration to version 7.1.2
A dump/restore is *not* required for those running 7.1.X.
_________________________________________________________________
Changes
Changes
Fix PL/pgSQL SELECTs when returning no rows
Fix for psql backslash core dump
@ -2326,12 +2369,12 @@ pg_dump cleanups
This has a variety of fixes from 7.1.
_________________________________________________________________
Migration to version 7.1.1
Migration to version 7.1.1
A dump/restore is *not* required for those running 7.1.
_________________________________________________________________
Changes
Changes
Fix for numeric MODULO operator (Tom)
pg_dump fixes (Philip)
@ -2394,13 +2437,13 @@ Python fixes (Darcy)
default. Subqueries in FROM are now supported.
_________________________________________________________________
Migration to version 7.1
Migration to version 7.1
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -2597,12 +2640,12 @@ New FreeBSD tools ipc_check, start-scripts/freebsd
This has a variety of fixes from 7.0.2.
_________________________________________________________________
Migration to version 7.0.3
Migration to version 7.0.3
A dump/restore is *not* required for those running 7.0.*.
_________________________________________________________________
Changes
Changes
Jdbc fixes (Peter)
Large object fix (Tom)
@ -2653,12 +2696,12 @@ Fix for crash of backend, on abort (Tom)
This is a repackaging of 7.0.1 with added documentation.
_________________________________________________________________
Migration to version 7.0.2
Migration to version 7.0.2
A dump/restore is *not* required for those running 7.*.
_________________________________________________________________
Changes
Changes
Added documentation to tarball.
@ -2671,12 +2714,12 @@ Added documentation to tarball.
This is a cleanup release for 7.0.
_________________________________________________________________
Migration to version 7.0.1
Migration to version 7.0.1
A dump/restore is *not* required for those running 7.0.
_________________________________________________________________
Changes
Changes
Fix many CLUSTER failures (Tom)
Allow ALTER TABLE RENAME works on indexes (Tom)
@ -2737,7 +2780,7 @@ ecpg changes (Michael)
are available, as are column correlation names.
_________________________________________________________________
Migration to version 7.0
Migration to version 7.0
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release of PostgreSQL. For those upgrading from
@ -2768,7 +2811,7 @@ Migration to version 7.0
geometric types.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -3101,12 +3144,12 @@ New multibyte encodings
PgAccess that was missing in 6.5.2, and installed an NT-specific fix.
_________________________________________________________________
Migration to version 6.5.3
Migration to version 6.5.3
A dump/restore is *not* required for those running 6.5.*.
_________________________________________________________________
Changes
Changes
Updated version of pgaccess 0.98
NT-specific patch
@ -3122,12 +3165,12 @@ Fix dumping rules on inherited tables
of problems reported by 6.5.1 users.
_________________________________________________________________
Migration to version 6.5.2
Migration to version 6.5.2
A dump/restore is *not* required for those running 6.5.*.
_________________________________________________________________
Changes
Changes
subselect+CASE fixes(Tom)
Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik)
@ -3166,12 +3209,12 @@ Updated version of pgaccess 0.98
of problems reported by 6.5 users.
_________________________________________________________________
Migration to version 6.5.1
Migration to version 6.5.1
A dump/restore is *not* required for those running 6.5.
_________________________________________________________________
Changes
Changes
Add NT README file
Portability fixes for linux_ppc, IRIX, linux_alpha, OpenBSD, alpha
@ -3269,7 +3312,7 @@ Add Win1250 (Czech) support (Pavel Behal)
CVSup.
_________________________________________________________________
Migration to version 6.5
Migration to version 6.5
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release of PostgreSQL. pg_upgrade can *not* be
@ -3315,7 +3358,7 @@ Multiversion Concurrency Control
referential integrity will be implemented.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -3492,12 +3535,12 @@ New install commands for plpgsql(Jan)
additional bug fix.
_________________________________________________________________
Migration to version 6.4.2
Migration to version 6.4.2
A dump/restore is *not* required for those running 6.4.*.
_________________________________________________________________
Changes
Changes
Fix for datetime constant problem on some platforms(Thomas)
_________________________________________________________________
@ -3510,12 +3553,12 @@ Fix for datetime constant problem on some platforms(Thomas)
of problems reported by 6.4 users.
_________________________________________________________________
Migration to version 6.4.1
Migration to version 6.4.1
A dump/restore is *not* required for those running 6.4.
_________________________________________________________________
Changes
Changes
Add pg_dump -N flag to force double quotes around identifiers. This is
the default(Thomas)
@ -3588,13 +3631,13 @@ Upgrade to PyGreSQL 2.2(D'Arcy)
it has ever been.
_________________________________________________________________
Migration to version 6.4
Migration to version 6.4
A dump/restore using pg_dump or pg_dumpall is required for those
wishing to migrate data from any previous release of PostgreSQL.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -3817,7 +3860,7 @@ new Makefile.shlib for shared library configuration(Tom)
migration instructions for version 6.3.
_________________________________________________________________
Changes
Changes
Configure detection improvements for tcl/tk(Brook Milligan, Alvin)
Manual page improvements(Bruce)
@ -3860,7 +3903,7 @@ ASSERT fixes(Bruce)
migration instructions for version 6.3.
_________________________________________________________________
Changes
Changes
ecpg cleanup/fixes, now version 1.1(Michael Meskes)
pg_user cleanup(Bruce)
@ -3973,13 +4016,13 @@ Better identify tcl and tk libs and includes(Bruce)
using are no longer needed.
_________________________________________________________________
Migration to version 6.3
Migration to version 6.3
A dump/restore using pg_dump or pg_dumpall is required for those
wishing to migrate data from any previous release of PostgreSQL.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -4167,7 +4210,7 @@ Remove un-needed malloc() calls and replace with palloc()(Bruce)
notes for instructions.
_________________________________________________________________
Migration from version 6.2 to version 6.2.1
Migration from version 6.2 to version 6.2.1
This is a minor bug-fix release. A dump/reload is not required from
version 6.2, but is required from any release prior to 6.2.
@ -4185,7 +4228,7 @@ Migration from version 6.2 to version 6.2.1
template1.
_________________________________________________________________
Changes
Changes
Allow TIME and TYPE column names(Thomas)
Allow larger range of true/false as boolean values(Thomas)
@ -4209,7 +4252,7 @@ Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
previous releases of PostgreSQL.
_________________________________________________________________
Migration from version 6.1 to version 6.2
Migration from version 6.1 to version 6.2
This migration requires a complete dump of the 6.1 database and a
restore of the database in 6.2.
@ -4218,13 +4261,13 @@ Migration from version 6.1 to version 6.2
used to dump the 6.1 database.
_________________________________________________________________
Migration from version 1.x to version 6.2
Migration from version 1.x to version 6.2
Those migrating from earlier 1.* releases should first upgrade to 1.09
because the COPY output format was improved from the 1.02 release.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -4345,14 +4388,14 @@ SPI and Trigger programming guides (Vadim & D'Arcy)
Release date: 1997-07-22
_________________________________________________________________
Migration from version 6.1 to version 6.1.1
Migration from version 6.1 to version 6.1.1
This is a minor bug-fix release. A dump/reload is not required from
version 6.1, but is required from any release prior to 6.1. Refer to
the release notes for 6.1 for more details.
_________________________________________________________________
Changes
Changes
fix for SET with options (Thomas)
allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce)
@ -4413,7 +4456,7 @@ pg_dumpall now returns proper status, portability fix(Bruce)
on my test machine (Linux/gcc/i686).
_________________________________________________________________
Migration to version 6.1
Migration to version 6.1
This migration requires a complete dump of the 6.0 database and a
restore of the database in 6.1.
@ -4422,7 +4465,7 @@ Migration to version 6.1
because the COPY output format was improved from the 1.02 release.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -4528,19 +4571,19 @@ DG/UX, Ultrix, IRIX, AIX portability fixes
previous releases of PostgreSQL.
_________________________________________________________________
Migration from version 1.09 to version 6.0
Migration from version 1.09 to version 6.0
This migration requires a complete dump of the 1.09 database and a
restore of the database in 6.0.
_________________________________________________________________
Migration from pre-1.09 to version 6.0
Migration from pre-1.09 to version 6.0
Those migrating from earlier 1.* releases should first upgrade to 1.09
because the COPY output format was improved from the 1.02 release.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -4663,7 +4706,7 @@ Unused/uninialized variables corrected
Release date: 1996-08-01
_________________________________________________________________
Migration from version 1.02 to version 1.02.1
Migration from version 1.02 to version 1.02.1
Here is a new migration file for 1.02.1. It includes the 'copy' change
and a script to convert old ASCII files.
@ -4691,7 +4734,7 @@ Migration from version 1.02 to version 1.02.1
present in 1.02. This is not a cause for concern.
_________________________________________________________________
Dump/Reload Procedure
Dump/Reload Procedure
If you are trying to reload a pg_dump or text-mode, copy tablename to
stdout generated with a previous version, you will need to run the
@ -4715,7 +4758,7 @@ create operator !~* (leftarg = varchar, rightarg = text, procedure = texticrege
xne);
_________________________________________________________________
Changes
Changes
Source code maintenance and development
* worldwide team of volunteers
@ -4749,7 +4792,7 @@ New Ports
Release date: 1996-02-23
_________________________________________________________________
Migration from version 1.0 to version 1.01
Migration from version 1.0 to version 1.01
The following notes are for the benefit of users who want to migrate
databases from Postgres95 1.0 to Postgres95 1.01.
@ -4839,7 +4882,7 @@ create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne
);
_________________________________________________________________
Changes
Changes
Incompatibilities:
* 1.01 is backwards compatible with 1.0 database provided the user
@ -4880,7 +4923,7 @@ Bug fixes:
Release date: 1995-09-05
_________________________________________________________________
Changes
Changes
Copyright change:
* The copyright of Postgres 1.0 has been loosened to be freely modifiable
@ -4928,7 +4971,7 @@ Bug fixes:
Release date: 1995-07-21
_________________________________________________________________
Changes
Changes
Incompatible changes:
* BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS VERSIONS
@ -5042,7 +5085,7 @@ New documentation:
Release date: 1995-05-25
_________________________________________________________________
Changes
Changes
Incompatible changes:
* The SQL statement for creating a database is 'CREATE DATABASE' instead

69
doc/src/sgml/release.sgml
View File

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.255 2004/02/13 04:40:06 momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.256 2004/03/02 00:38:46 tgl Exp $
-->
<appendix id="release">
@ -1971,6 +1971,71 @@ DROP SCHEMA information_schema CASCADE;
</sect2>
</sect1>
<sect1 id="release-7-3-6">
<title>Release 7.3.6</title>
<note>
<title>Release date</title>
<simpara>2004-03-02</simpara>
</note>
<para>
This release contains a variety of fixes from 7.3.5.
</para>
<sect2>
<title>Migration to version 7.3.6</title>
<para>
A dump/restore is <emphasis>not</emphasis> required for those
running 7.3.*.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem><para>Revert erroneous changes in rule permissions checking</para>
<para>A patch applied in 7.3.3 to fix a corner case in rule permissions checks
turns out to have disabled rule-related permissions checks in many
not-so-corner cases. This would for example allow users to insert into views
they weren't supposed to have permission to insert into. We have therefore
reverted the 7.3.3 patch. The original bug will be fixed in 7.5.
</para></listitem>
<listitem><para>Repair incorrect order of operations in
GetNewTransactionId()</para>
<para>
This bug could result in failure under out-of-disk-space conditions, including
inability to restart even after disk space is freed.
</para></listitem>
<listitem><para>Ensure configure selects -fno-strict-aliasing even when
an external value for CFLAGS is supplied</para>
<para>
On some platforms, building with -fstrict-aliasing causes bugs.
</para></listitem>
<listitem><para>Make pg_restore handle 64-bit off_t correctly</para>
<para>
This bug prevented proper restoration from archive files exceeding 4Gb.
</para></listitem>
<listitem><para>Make contrib/dblink not assume that local and remote type OIDs
match (Joe)</para></listitem>
<listitem><para>Quote connectby()'s start_with argument properly (Joe)</para></listitem>
<listitem><para>Don't crash when a rowtype argument to a plpgsql function is
NULL</para></listitem>
<listitem><para>Avoid generating invalid character encoding sequences in
corner cases when planning LIKE operations</para></listitem>
<listitem><para>Ensure text_position() cannot scan past end of source string
in multibyte cases (Korea PostgreSQL Users' Group)</para></listitem>
<listitem><para>Fix index optimization and selectivity estimates for LIKE
operations on bytea columns (Joe)</para></listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-7-3-5">
<title>Release 7.3.5</title>
@ -2071,7 +2136,7 @@ DROP SCHEMA information_schema CASCADE;
</note>
<para>
This release contains of variety of fixes for version 7.3.2.
This release contains a variety of fixes for version 7.3.2.
</para>
<sect2>