Recreate HISTORY file to match release.sgml changes. Stamp 7.3 final in

configure/configure.in.
This commit is contained in:
Bruce Momjian 2002-11-26 22:04:03 +00:00
parent 80e6d99731
commit 75d1ed3392
2 changed files with 460 additions and 445 deletions

193
HISTORY
View File

@ -1,21 +1,28 @@
Release Notes
Release 7.3
7.4 Development Branch
Release date: 2002-11-??
Below is a subset of the changes that have gone into the development
branch of PostgreSQL since version 7.3. For a complete list of
changes, consult the CVS logs.
_________________________________________________________________
Overview
Release 7.3
Release date: 2002-11-27
_________________________________________________________________
Overview
Major changes in this release:
Schemas
Schemas allow users to create objects in their own namespace so
two people or applications can have tables with the same name.
There is also a public schema for shared tables. Table/index
creation can be restricted by removing permissions on the
public schema.
Schemas allow users to create objects in separate namespaces,
so two people or applications can have tables with the same
name. There is also a public schema for shared tables.
Table/index creation can be restricted by removing permissions
on the public schema.
Drop Column
PostgreSQL now supports the ALTER TABLE ... DROP COLUMN
@ -55,10 +62,13 @@ Overview
Functions/Identifiers
By default, functions can now take up to 32 parameters, and
identifiers can be up to 63 bytes long.
identifiers can be up to 63 bytes long. Also, OPAQUE is now
deprecated: there are specific "pseudo-datatypes" to represent
each of the former meanings of OPAQUE in function argument and
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
@ -71,24 +81,29 @@ Migration to version 7.3
* Pre-6.3 clients are no longer supported.
* "pg_hba.conf" now has a column for the user name and additional
features. Existing files need to be adjusted.
* Several "postgresql.conf" logging parameters have been renamed and
improved.
* Several "postgresql.conf" logging parameters have been renamed.
* LIMIT #,# has been disabled; use LIMIT # OFFSET #.
* "INSERT" statements with column lists must specify all values;
e.g., INSERT INTO tab (col1, col2) VALUES ('val1') is now invalid.
* An index is now not automatically created for serial columns.
* "INSERT" statements with column lists must specify a value for
each specified column. For example, INSERT INTO tab (col1, col2)
VALUES ('val1') is now invalid. It's still allowed to supply fewer
columns than expected if the "INSERT" does not have a column list.
* serial columns are no longer automatically UNIQUE; thus, an index
will not automatically be created.
* A "SET" command inside an aborted transaction is now rolled back.
* "COPY" no longer considers missing trailing columns to be null.
All columns need to be specified.
All columns need to be specified. (However, one may achieve a
similar effect by specifying a column list in the "COPY" command.)
* The data type timestamp is now equivalent to timestamp without
timezone, instead of timestamp with timezone.
time zone, instead of timestamp with time zone.
* Pre-7.3 databases loaded into 7.3 will not have the new object
dependencies for serial columns, unique constraints, and foreign
keys. See the directory "contrib/adddepend/" for a detailed
description and a script that will add such dependencies.
* An empty string ('') is no longer allowed as the input into an
integer field. Formerly, it was silently interpreted as 0.
_________________________________________________________________
Changes
Changes
Server Operation
@ -113,7 +128,7 @@ Performance
Speed improvement for large object restore (Mario Weilguni)
Mark expired index entries on first lookup, saving later heap fetches
(Tom)
Eliminate NULL bitmap padding when not required (Manfred)
Avoid excessive NULL bitmap padding (Manfred Koizar)
Add BSD-licensed qsort() for Solaris, for performance (Bruce)
Reduce per-row overhead by four bytes (Manfred Koizar)
Fix GEQO optimizer bug (Neil Conway)
@ -173,7 +188,7 @@ Queries
Disable LIMIT #,# syntax; now only LIMIT # OFFSET # supported (Bruce)
Increase identifier length to 63 (Neil, Bruce)
UNION fixes for merging >= 3 columns of different lengths (Tom)
Add DEFAULT keyword to INSERT, e.g., INSERT ... (..., DEFAULT, )
Add DEFAULT keyword to INSERT, e.g., INSERT ... (..., DEFAULT, ...)
(Rod)
Allow views to have default values using ALTER COLUMN ... SET DEFAULT
(Neil)
@ -195,7 +210,7 @@ Queries
Object Manipulation
Make equals signs optional in CREATE DATABASE (Gavin Sherry)
Make ALTER TABLE OWNER to change index ownership (Neil)
Make ALTER TABLE OWNER change index ownership too (Neil)
New ALTER TABLE tabname ALTER COLUMN colname SET STORAGE controls
TOAST storage, compression (John Gray)
Add schema support, CREATE/DROP SCHEMA (Tom)
@ -245,7 +260,7 @@ Utility Commands
(Rod)
Rollback SET commands in aborted transactions (Tom)
EXPLAIN now outputs as a query (Tom)
Display sort keys in EXPLAIN (Tom)
Display condition expressions and sort keys in EXPLAIN (Tom)
Add 'SET LOCAL var = value' to set configuration variables for a
single transaction (Tom)
Allow ANALYZE to run in a transaction (Bruce)
@ -335,7 +350,7 @@ Data Types and Functions
Internationalization
Add additional encodings (Korean (JOHAB), Thai (WIN874), Vietnamese
Add additional encodings: Korean (JOHAB), Thai (WIN874), Vietnamese
(TCVN), Arabic (WIN1256), Simplified Chinese (GBK), Korean (UHC)
(Eiji Tokuya)
Enable locale support by default (Peter)
@ -360,7 +375,7 @@ Server-side Languages
Change PL/Tcl build to use configured compiler and Makefile.shlib
(Peter)
Overhaul the PL/pgSQL FOUND variable to be more Oracle-compatible
(Tom, Neil)
(Neil, Tom)
Allow PL/pgSQL to handle quoted identifiers (Tom)
Allow set-returning PL/pgSQL functions (Neil)
Make PL/pgSQL schema-aware (Joe)
@ -514,7 +529,7 @@ Contrib
Add /contrib/tablefunc table function examples (Joe)
Add /contrib/ltree data type for tree structures (Teodor Sigaev,
Oleg Bartunov)
Move /contrib/pg_controldata into main tree (Bruce)
Move /contrib/pg_controldata, pg_resetxlog into main tree (Bruce)
Fixes to /contrib/cube (Bruno Wolff)
Improve /contrib/fulltextindex (Christopher)
_________________________________________________________________
@ -527,12 +542,12 @@ Contrib
possible data loss.
_________________________________________________________________
Migration to version 7.2.3
Migration to version 7.2.3
A dump/restore is *not* required for those running 7.2.X.
_________________________________________________________________
Changes
Changes
Prevent possible compressed transaction log loss (Tom)
Prevent non-superuser from increasing most recent vacuum info (Tom)
@ -549,12 +564,12 @@ Changes
This has a variety of fixes from 7.2.1.
_________________________________________________________________
Migration to version 7.2.2
Migration to version 7.2.2
A dump/restore is *not* required for those running 7.2.X.
_________________________________________________________________
Changes
Changes
Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)
Fix for compressed transaction log id wraparound (Tom)
@ -580,12 +595,12 @@ Changes
This has a variety of fixes from 7.2.
_________________________________________________________________
Migration to version 7.2.1
Migration to version 7.2.1
A dump/restore is *not* required for those running 7.2.
_________________________________________________________________
Changes
Changes
Ensure that sequence counters do not go backwards after a crash (Tom)
Fix pgaccess kanji-coversion key binding (Tatsuo)
@ -612,7 +627,7 @@ Changes
Release date: 2002-02-04
_________________________________________________________________
Overview
Overview
This release improves PostgreSQL for use in high-volume applications.
@ -650,7 +665,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.
@ -679,7 +694,7 @@ Migration to version 7.2
clauses, e.g. LIMIT 10 OFFSET 20.
_________________________________________________________________
Changes
Changes
Server Operation
@ -1061,12 +1076,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)
@ -1088,12 +1103,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
@ -1110,12 +1125,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)
@ -1178,13 +1193,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
---------
@ -1381,12 +1396,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)
@ -1437,12 +1452,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.
@ -1455,12 +1470,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)
@ -1521,7 +1536,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
@ -1552,7 +1567,7 @@ Migration to version 7.0
geometric types.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -1885,12 +1900,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
@ -1906,12 +1921,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)
@ -1950,12 +1965,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
@ -2053,7 +2068,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
@ -2099,7 +2114,7 @@ Multiversion Concurrency Control
referential integrity will be implemented.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -2276,12 +2291,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)
_________________________________________________________________
@ -2294,12 +2309,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)
@ -2372,13 +2387,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
---------
@ -2601,7 +2616,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)
@ -2644,7 +2659,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)
@ -2757,13 +2772,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
---------
@ -2951,7 +2966,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.
@ -2969,7 +2984,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)
@ -2993,7 +3008,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.
@ -3002,13 +3017,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
---------
@ -3129,14 +3144,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)
@ -3197,7 +3212,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.
@ -3206,7 +3221,7 @@ Migration to version 6.1
because the COPY output format was improved from the 1.02 release.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -3312,19 +3327,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
---------
@ -3447,7 +3462,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.
@ -3475,7 +3490,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
@ -3499,7 +3514,7 @@ create operator !~* (leftarg = varchar, rightarg = text, procedure = texticrege
xne);
_________________________________________________________________
Changes
Changes
Source code maintenance and development
* worldwide team of volunteers
@ -3511,7 +3526,7 @@ Enhancements
* pg_dump now output the schema and/or the data, with many fixes to
enhance completeness.
* psql used in place of monitor in administration shell scripts.
monitor to be depreciated in next release.
monitor to be deprecated in next release.
* date/time functions enhanced
* NULL insert/update/comparison fixed/enhanced
* TCL/TK lib and shell fixed to work with both tck7.4/tk4.0 and tcl7.5/tk4.1
@ -3533,7 +3548,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.
@ -3623,7 +3638,7 @@ create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne
);
_________________________________________________________________
Changes
Changes
Incompatibilities:
* 1.01 is backwards compatible with 1.0 database provided the user
@ -3664,7 +3679,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
@ -3712,7 +3727,7 @@ Bug fixes:
Release date: 1995-07-21
_________________________________________________________________
Changes
Changes
Incompatible changes:
* BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS VERSIONS
@ -3826,7 +3841,7 @@ New documentation:
Release date: 1995-05-25
_________________________________________________________________
Changes
Changes
Incompatible changes:
* The SQL statement for creating a database is 'CREATE DATABASE' instead

View File

@ -1,5 +1,5 @@
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.167 2002/11/23 03:59:06 momjian Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.168 2002/11/26 22:04:03 momjian Exp $
-->
<appendix id="release">
@ -33,7 +33,7 @@ worries about funny characters.
<note>
<title>Release date</title>
<simpara>2002-11-??</simpara>
<simpara>2002-11-27</simpara>
</note>
<sect2>