Commit 75d1ed33 authored by Bruce Momjian's avatar Bruce Momjian

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

configure/configure.in.
parent 80e6d997
Release Notes Release Notes
7.4 Development Branch
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.
_________________________________________________________________
Release 7.3 Release 7.3
Release date: 2002-11-?? Release date: 2002-11-27
_________________________________________________________________ _________________________________________________________________
Overview Overview
Major changes in this release: Major changes in this release:
Schemas Schemas
Schemas allow users to create objects in their own namespace so Schemas allow users to create objects in separate namespaces,
two people or applications can have tables with the same name. so two people or applications can have tables with the same
There is also a public schema for shared tables. Table/index name. There is also a public schema for shared tables.
creation can be restricted by removing permissions on the Table/index creation can be restricted by removing permissions
public schema. on the public schema.
Drop Column Drop Column
PostgreSQL now supports the ALTER TABLE ... DROP COLUMN PostgreSQL now supports the ALTER TABLE ... DROP COLUMN
functionality. functionality.
Table Functions Table Functions
Functions returning multiple rows and/or multiple columns are Functions returning multiple rows and/or multiple columns are
now much easier to use than before. You can call such a "table now much easier to use than before. You can call such a "table
function" in the SELECT FROM clause, treating its output like a function" in the SELECT FROM clause, treating its output like a
table. Also, PL/pgSQL functions can now return sets. table. Also, PL/pgSQL functions can now return sets.
Prepared Queries Prepared Queries
PostgreSQL now supports prepared queries, for improved PostgreSQL now supports prepared queries, for improved
performance. performance.
Dependency Tracking Dependency Tracking
PostgreSQL now records object dependencies, which allows PostgreSQL now records object dependencies, which allows
improvements in many areas. "DROP" statements now take either improvements in many areas. "DROP" statements now take either
CASCADE or RESTRICT to control whether dependent objects are CASCADE or RESTRICT to control whether dependent objects are
also dropped. also dropped.
Privileges Privileges
Functions and procedural languages now have privileges, and Functions and procedural languages now have privileges, and
functions can be defined to run with the privileges of their functions can be defined to run with the privileges of their
creator. creator.
Internationalization Internationalization
Both multibyte and locale support are now always enabled. Both multibyte and locale support are now always enabled.
Logging Logging
A variety of logging options have been enhanced. A variety of logging options have been enhanced.
Interfaces Interfaces
A large number of interfaces have been moved to A large number of interfaces have been moved to
http://gborg.postgresql.org where they can be developed and http://gborg.postgresql.org where they can be developed and
released independently. released independently.
Functions/Identifiers Functions/Identifiers
By default, functions can now take up to 32 parameters, and 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
Migration to version 7.3 result types.
_________________________________________________________________
Migration to version 7.3
A dump/restore using pg_dump is required for those wishing to migrate A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release. If your application examines the data from any previous release. If your application examines the
system catalogs, additional changes will be required due to the system catalogs, additional changes will be required due to the
introduction of schemas in 7.3; for more information, see: introduction of schemas in 7.3; for more information, see:
http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3. http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3.
Observe the following incompatibilities: Observe the following incompatibilities:
* Pre-6.3 clients are no longer supported. * Pre-6.3 clients are no longer supported.
* "pg_hba.conf" now has a column for the user name and additional * "pg_hba.conf" now has a column for the user name and additional
features. Existing files need to be adjusted. features. Existing files need to be adjusted.
* Several "postgresql.conf" logging parameters have been renamed and * Several "postgresql.conf" logging parameters have been renamed.
improved.
* LIMIT #,# has been disabled; use LIMIT # OFFSET #. * LIMIT #,# has been disabled; use LIMIT # OFFSET #.
* "INSERT" statements with column lists must specify all values; * "INSERT" statements with column lists must specify a value for
e.g., INSERT INTO tab (col1, col2) VALUES ('val1') is now invalid. each specified column. For example, INSERT INTO tab (col1, col2)
* An index is now not automatically created for serial columns. 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. * A "SET" command inside an aborted transaction is now rolled back.
* "COPY" no longer considers missing trailing columns to be null. * "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 * 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 * Pre-7.3 databases loaded into 7.3 will not have the new object
dependencies for serial columns, unique constraints, and foreign dependencies for serial columns, unique constraints, and foreign
keys. See the directory "contrib/adddepend/" for a detailed keys. See the directory "contrib/adddepend/" for a detailed
description and a script that will add such dependencies. 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 Server Operation
Add pg_locks view to show locks (Neil) Add pg_locks view to show locks (Neil)
...@@ -99,7 +114,7 @@ Server Operation ...@@ -99,7 +114,7 @@ Server Operation
Reserve the last few backend slots for superusers, add parameter Reserve the last few backend slots for superusers, add parameter
superuser_reserved_connections to control this (Nigel J. Andrews) superuser_reserved_connections to control this (Nigel J. Andrews)
_________________________________________________________________ _________________________________________________________________
Performance Performance
Improve startup by calling localtime() only once (Tom) Improve startup by calling localtime() only once (Tom)
...@@ -113,7 +128,7 @@ Performance ...@@ -113,7 +128,7 @@ Performance
Speed improvement for large object restore (Mario Weilguni) Speed improvement for large object restore (Mario Weilguni)
Mark expired index entries on first lookup, saving later heap fetches Mark expired index entries on first lookup, saving later heap fetches
(Tom) (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) Add BSD-licensed qsort() for Solaris, for performance (Bruce)
Reduce per-row overhead by four bytes (Manfred Koizar) Reduce per-row overhead by four bytes (Manfred Koizar)
Fix GEQO optimizer bug (Neil Conway) Fix GEQO optimizer bug (Neil Conway)
...@@ -125,7 +140,7 @@ Performance ...@@ -125,7 +140,7 @@ Performance
Tom) Tom)
Improved WAL write concurrency (Tom) Improved WAL write concurrency (Tom)
_________________________________________________________________ _________________________________________________________________
Privileges Privileges
Add privileges on functions and procedural languages (Peter) Add privileges on functions and procedural languages (Peter)
...@@ -137,7 +152,7 @@ Privileges ...@@ -137,7 +152,7 @@ Privileges
Allow functions to be executed with the privilege of the function Allow functions to be executed with the privilege of the function
owner (Peter) owner (Peter)
_________________________________________________________________ _________________________________________________________________
Server Configuration Server Configuration
Server log messages now tagged with LOG, not DEBUG (Bruce) Server log messages now tagged with LOG, not DEBUG (Bruce)
...@@ -166,14 +181,14 @@ Server Configuration ...@@ -166,14 +181,14 @@ Server Configuration
Add param log_min_error_statement to print commands to logs on error Add param log_min_error_statement to print commands to logs on error
(Gavin) (Gavin)
_________________________________________________________________ _________________________________________________________________
Queries Queries
Make cursors insensitive, meaning their contents do not change (Tom) Make cursors insensitive, meaning their contents do not change (Tom)
Disable LIMIT #,# syntax; now only LIMIT # OFFSET # supported (Bruce) Disable LIMIT #,# syntax; now only LIMIT # OFFSET # supported (Bruce)
Increase identifier length to 63 (Neil, Bruce) Increase identifier length to 63 (Neil, Bruce)
UNION fixes for merging >= 3 columns of different lengths (Tom) 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) (Rod)
Allow views to have default values using ALTER COLUMN ... SET DEFAULT Allow views to have default values using ALTER COLUMN ... SET DEFAULT
(Neil) (Neil)
...@@ -191,11 +206,11 @@ Queries ...@@ -191,11 +206,11 @@ Queries
Allow FOR UPDATE to appear after LIMIT/OFFSET (Bruce) Allow FOR UPDATE to appear after LIMIT/OFFSET (Bruce)
Add variable autocommit (Tom, David Van Wie) Add variable autocommit (Tom, David Van Wie)
_________________________________________________________________ _________________________________________________________________
Object Manipulation Object Manipulation
Make equals signs optional in CREATE DATABASE (Gavin Sherry) 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 New ALTER TABLE tabname ALTER COLUMN colname SET STORAGE controls
TOAST storage, compression (John Gray) TOAST storage, compression (John Gray)
Add schema support, CREATE/DROP SCHEMA (Tom) Add schema support, CREATE/DROP SCHEMA (Tom)
...@@ -230,7 +245,7 @@ Object Manipulation ...@@ -230,7 +245,7 @@ Object Manipulation
Add /contrib/adddepend to handle pre-7.3 object dependencies (Rod) Add /contrib/adddepend to handle pre-7.3 object dependencies (Rod)
Allow better casting when inserting/updating values (Tom) Allow better casting when inserting/updating values (Tom)
_________________________________________________________________ _________________________________________________________________
Utility Commands Utility Commands
Have COPY TO output embedded carriage returns and newlines as \r and Have COPY TO output embedded carriage returns and newlines as \r and
...@@ -245,7 +260,7 @@ Utility Commands ...@@ -245,7 +260,7 @@ Utility Commands
(Rod) (Rod)
Rollback SET commands in aborted transactions (Tom) Rollback SET commands in aborted transactions (Tom)
EXPLAIN now outputs as a query (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 Add 'SET LOCAL var = value' to set configuration variables for a
single transaction (Tom) single transaction (Tom)
Allow ANALYZE to run in a transaction (Bruce) Allow ANALYZE to run in a transaction (Bruce)
...@@ -275,7 +290,7 @@ Utility Commands ...@@ -275,7 +290,7 @@ Utility Commands
Fix rare index corruption when a page split affects bulk delete (Tom) Fix rare index corruption when a page split affects bulk delete (Tom)
Fix ALTER TABLE ... ADD COLUMN for inheritance (Alvaro Herrera) Fix ALTER TABLE ... ADD COLUMN for inheritance (Alvaro Herrera)
_________________________________________________________________ _________________________________________________________________
Data Types and Functions Data Types and Functions
Fix factorial(0) to return 1 (Bruce) Fix factorial(0) to return 1 (Bruce)
...@@ -332,10 +347,10 @@ Data Types and Functions ...@@ -332,10 +347,10 @@ Data Types and Functions
Fix trigger/type/language functions returning OPAQUE to return Fix trigger/type/language functions returning OPAQUE to return
proper type (Tom) proper type (Tom)
_________________________________________________________________ _________________________________________________________________
Internationalization 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) (TCVN), Arabic (WIN1256), Simplified Chinese (GBK), Korean (UHC)
(Eiji Tokuya) (Eiji Tokuya)
Enable locale support by default (Peter) Enable locale support by default (Peter)
...@@ -353,20 +368,20 @@ Internationalization ...@@ -353,20 +368,20 @@ Internationalization
aware (Peter) aware (Peter)
New and updated translations New and updated translations
_________________________________________________________________ _________________________________________________________________
Server-side Languages Server-side Languages
Allow recursive SQL function (Peter) Allow recursive SQL function (Peter)
Change PL/Tcl build to use configured compiler and Makefile.shlib Change PL/Tcl build to use configured compiler and Makefile.shlib
(Peter) (Peter)
Overhaul the PL/pgSQL FOUND variable to be more Oracle-compatible Overhaul the PL/pgSQL FOUND variable to be more Oracle-compatible
(Tom, Neil) (Neil, Tom)
Allow PL/pgSQL to handle quoted identifiers (Tom) Allow PL/pgSQL to handle quoted identifiers (Tom)
Allow set-returning PL/pgSQL functions (Neil) Allow set-returning PL/pgSQL functions (Neil)
Make PL/pgSQL schema-aware (Joe) Make PL/pgSQL schema-aware (Joe)
Remove some memory leaks (Nigel J. Andrews, Tom) Remove some memory leaks (Nigel J. Andrews, Tom)
_________________________________________________________________ _________________________________________________________________
Psql Psql
Don't lowercase psql \connect database name for 7.2.0 compatibility Don't lowercase psql \connect database name for 7.2.0 compatibility
...@@ -382,7 +397,7 @@ Psql ...@@ -382,7 +397,7 @@ Psql
Have psql reports its version number on startup (Tom) Have psql reports its version number on startup (Tom)
Allow \copy to specify column names (Tom) Allow \copy to specify column names (Tom)
_________________________________________________________________ _________________________________________________________________
Libpq Libpq
Add $HOME/.pgpass to store host/user password combinations (Alvaro Add $HOME/.pgpass to store host/user password combinations (Alvaro
...@@ -397,7 +412,7 @@ Libpq ...@@ -397,7 +412,7 @@ Libpq
Fix for SSL with non-blocking connections (Jack Bates) Fix for SSL with non-blocking connections (Jack Bates)
Add libpq connection timeout parameter (Denis A Ustimenko) Add libpq connection timeout parameter (Denis A Ustimenko)
_________________________________________________________________ _________________________________________________________________
JDBC JDBC
Allow JDBC to compile with JDK 1.4 (Dave) Allow JDBC to compile with JDK 1.4 (Dave)
...@@ -412,7 +427,7 @@ JDBC ...@@ -412,7 +427,7 @@ JDBC
Fix MD5 encryption handling for multibyte servers (Jun Kawai) Fix MD5 encryption handling for multibyte servers (Jun Kawai)
Add support for prepared statements (Barry) Add support for prepared statements (Barry)
_________________________________________________________________ _________________________________________________________________
Miscellaneous Interfaces Miscellaneous Interfaces
Fixed ECPG bug concerning octal numbers in single quotes (Michael) Fixed ECPG bug concerning octal numbers in single quotes (Michael)
...@@ -432,7 +447,7 @@ Miscellaneous Interfaces ...@@ -432,7 +447,7 @@ Miscellaneous Interfaces
Add pg_on_connection_loss command to libpgtcl (Gerhard Hintermayer, Add pg_on_connection_loss command to libpgtcl (Gerhard Hintermayer,
Tom) Tom)
_________________________________________________________________ _________________________________________________________________
Source Code Source Code
Fix for parallel make (Peter) Fix for parallel make (Peter)
...@@ -491,7 +506,7 @@ Source Code ...@@ -491,7 +506,7 @@ Source Code
Remove parameter wal_files because WAL files are now recycled (Bruce) Remove parameter wal_files because WAL files are now recycled (Bruce)
Add version numbers to heap pages (Tom) Add version numbers to heap pages (Tom)
_________________________________________________________________ _________________________________________________________________
Contrib Contrib
Allow inet arrays in /contrib/array (Neil) Allow inet arrays in /contrib/array (Neil)
...@@ -514,26 +529,26 @@ Contrib ...@@ -514,26 +529,26 @@ Contrib
Add /contrib/tablefunc table function examples (Joe) Add /contrib/tablefunc table function examples (Joe)
Add /contrib/ltree data type for tree structures (Teodor Sigaev, Add /contrib/ltree data type for tree structures (Teodor Sigaev,
Oleg Bartunov) 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) Fixes to /contrib/cube (Bruno Wolff)
Improve /contrib/fulltextindex (Christopher) Improve /contrib/fulltextindex (Christopher)
_________________________________________________________________ _________________________________________________________________
Release 7.2.3 Release 7.2.3
Release date: 2002-10-01 Release date: 2002-10-01
This has a variety of fixes from 7.2.2, including fixes to prevent This has a variety of fixes from 7.2.2, including fixes to prevent
possible data loss. 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. A dump/restore is *not* required for those running 7.2.X.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Prevent possible compressed transaction log loss (Tom) Prevent possible compressed transaction log loss (Tom)
Prevent non-superuser from increasing most recent vacuum info (Tom) Prevent non-superuser from increasing most recent vacuum info (Tom)
Handle pre-1970 date values in newer versions of glibc (Tom) Handle pre-1970 date values in newer versions of glibc (Tom)
...@@ -541,21 +556,21 @@ Changes ...@@ -541,21 +556,21 @@ Changes
Prevent spinlock hangs on SMP PPC machines (Tomoyuki Niijima) Prevent spinlock hangs on SMP PPC machines (Tomoyuki Niijima)
Fix pg_dump to properly dump FULL JOIN USING (Tom) Fix pg_dump to properly dump FULL JOIN USING (Tom)
_________________________________________________________________ _________________________________________________________________
Release 7.2.2 Release 7.2.2
Release date: 2002-08-23 Release date: 2002-08-23
This has a variety of fixes from 7.2.1. 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. 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) Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)
Fix for compressed transaction log id wraparound (Tom) Fix for compressed transaction log id wraparound (Tom)
Fix PQescapeBytea/PQunescapeBytea so that they handle bytes > 0x7f (Ta Fix PQescapeBytea/PQunescapeBytea so that they handle bytes > 0x7f (Ta
...@@ -572,21 +587,21 @@ Changes ...@@ -572,21 +587,21 @@ Changes
Fix for crash with long DATA strings (Thomes, Neil) Fix for crash with long DATA strings (Thomes, Neil)
Fix for repeat(), lpad(), rpad() and long strings (Neil) Fix for repeat(), lpad(), rpad() and long strings (Neil)
_________________________________________________________________ _________________________________________________________________
Release 7.2.1 Release 7.2.1
Release date: 2002-03-21 Release date: 2002-03-21
This has a variety of fixes from 7.2. 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. 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) Ensure that sequence counters do not go backwards after a crash (Tom)
Fix pgaccess kanji-coversion key binding (Tatsuo) Fix pgaccess kanji-coversion key binding (Tatsuo)
Optimizer improvements (Tom) Optimizer improvements (Tom)
...@@ -606,57 +621,57 @@ Changes ...@@ -606,57 +621,57 @@ Changes
Fix for array subscripts handling (Tom) Fix for array subscripts handling (Tom)
Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom) Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)
_________________________________________________________________ _________________________________________________________________
Release 7.2 Release 7.2
Release date: 2002-02-04 Release date: 2002-02-04
_________________________________________________________________ _________________________________________________________________
Overview Overview
This release improves PostgreSQL for use in high-volume applications. This release improves PostgreSQL for use in high-volume applications.
Major changes in this release: Major changes in this release:
VACUUM VACUUM
Vacuuming no longer locks tables, thus allowing normal user Vacuuming no longer locks tables, thus allowing normal user
access during the vacuum. A new "VACUUM FULL" command does access during the vacuum. A new "VACUUM FULL" command does
old-style vacuum by locking the table and shrinking the on-disk old-style vacuum by locking the table and shrinking the on-disk
copy of the table. copy of the table.
Transactions Transactions
There is no longer a problem with installations that exceed There is no longer a problem with installations that exceed
four billion transactions. four billion transactions.
OIDs OIDs
OIDs are now optional. Users can now create tables without OIDs OIDs are now optional. Users can now create tables without OIDs
for cases where OID usage is excessive. for cases where OID usage is excessive.
Optimizer Optimizer
The system now computes histogram column statistics during The system now computes histogram column statistics during
"ANALYZE", allowing much better optimizer choices. "ANALYZE", allowing much better optimizer choices.
Security Security
A new MD5 encryption option allows more secure storage and A new MD5 encryption option allows more secure storage and
transfer of passwords. A new Unix-domain socket authentication transfer of passwords. A new Unix-domain socket authentication
option is available on Linux and BSD systems. option is available on Linux and BSD systems.
Statistics Statistics
Administrators can use the new table access statistics module Administrators can use the new table access statistics module
to get fine-grained information about table and index usage. to get fine-grained information about table and index usage.
Internationalization Internationalization
Program and library messages can now be displayed in several Program and library messages can now be displayed in several
languages. languages.
_________________________________________________________________ _________________________________________________________________
Migration to version 7.2 Migration to version 7.2
A dump/restore using "pg_dump" is required for those wishing to A dump/restore using "pg_dump" is required for those wishing to
migrate data from any previous release. migrate data from any previous release.
Observe the following incompatibilities: Observe the following incompatibilities:
* The semantics of the "VACUUM" command have changed in this * The semantics of the "VACUUM" command have changed in this
release. You may wish to update your maintenance procedures release. You may wish to update your maintenance procedures
accordingly. accordingly.
...@@ -673,14 +688,14 @@ Migration to version 7.2 ...@@ -673,14 +688,14 @@ Migration to version 7.2
need to rewrite your applications. need to rewrite your applications.
* The timestamp(), time(), and interval() functions are no longer * The timestamp(), time(), and interval() functions are no longer
available. Instead of timestamp(), use timestamp 'string' or CAST. available. Instead of timestamp(), use timestamp 'string' or CAST.
The SELECT ... LIMIT #,# syntax will be removed in the next release. The SELECT ... LIMIT #,# syntax will be removed in the next release.
You should change your queries to use separate LIMIT and OFFSET You should change your queries to use separate LIMIT and OFFSET
clauses, e.g. LIMIT 10 OFFSET 20. clauses, e.g. LIMIT 10 OFFSET 20.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Server Operation Server Operation
Create temporary files in a separate directory (Bruce) Create temporary files in a separate directory (Bruce)
...@@ -705,7 +720,7 @@ Server Operation ...@@ -705,7 +720,7 @@ Server Operation
Superuser ID now fixed at 1 (Peter E) Superuser ID now fixed at 1 (Peter E)
New pg_ctl "reload" option (Tom) New pg_ctl "reload" option (Tom)
_________________________________________________________________ _________________________________________________________________
Performance Performance
Optimizer improvements (Tom) Optimizer improvements (Tom)
...@@ -719,7 +734,7 @@ Performance ...@@ -719,7 +734,7 @@ Performance
R-tree performance improvements (Kenneth Been) R-tree performance improvements (Kenneth Been)
B-tree splits more efficient (Tom) B-tree splits more efficient (Tom)
_________________________________________________________________ _________________________________________________________________
Privileges Privileges
Change UPDATE, DELETE permissions to be distinct (Peter E) Change UPDATE, DELETE permissions to be distinct (Peter E)
...@@ -732,7 +747,7 @@ Privileges ...@@ -732,7 +747,7 @@ Privileges
Disallow access to pg_statistic for non-superuser, add user-accessible Disallow access to pg_statistic for non-superuser, add user-accessible
views (Tom) views (Tom)
_________________________________________________________________ _________________________________________________________________
Client Authentication Client Authentication
Fork postmaster before doing authentication to prevent hangs (Peter E) Fork postmaster before doing authentication to prevent hangs (Peter E)
...@@ -743,7 +758,7 @@ Client Authentication ...@@ -743,7 +758,7 @@ Client Authentication
PAM authentication (Dominic J. Eidson) PAM authentication (Dominic J. Eidson)
Load pg_hba.conf and pg_ident.conf only on startup and SIGHUP (Bruce) Load pg_hba.conf and pg_ident.conf only on startup and SIGHUP (Bruce)
_________________________________________________________________ _________________________________________________________________
Server Configuration Server Configuration
Interpretation of some time zone abbreviations as Australian rather th Interpretation of some time zone abbreviations as Australian rather th
...@@ -755,7 +770,7 @@ Server Configuration ...@@ -755,7 +770,7 @@ Server Configuration
New parameter to set client authentication timeout (Tom) New parameter to set client authentication timeout (Tom)
New parameter to set maximum number of open files (Tom) New parameter to set maximum number of open files (Tom)
_________________________________________________________________ _________________________________________________________________
Queries Queries
Statements added by INSERT rules now execute after the INSERT (Jan) Statements added by INSERT rules now execute after the INSERT (Jan)
...@@ -769,7 +784,7 @@ Queries ...@@ -769,7 +784,7 @@ Queries
Fix for LIMIT, DISTINCT ON pushed into subqueries (Tom) Fix for LIMIT, DISTINCT ON pushed into subqueries (Tom)
Fix nested EXCEPT/INTERSECT (Tom) Fix nested EXCEPT/INTERSECT (Tom)
_________________________________________________________________ _________________________________________________________________
Schema Manipulation Schema Manipulation
Fix SERIAL in temporary tables (Bruce) Fix SERIAL in temporary tables (Bruce)
...@@ -797,7 +812,7 @@ Schema Manipulation ...@@ -797,7 +812,7 @@ Schema Manipulation
, Teodor Sigaev, Tom) , Teodor Sigaev, Tom)
Enable partial indexes (Martijn van Oosterhout) Enable partial indexes (Martijn van Oosterhout)
_________________________________________________________________ _________________________________________________________________
Utility Commands Utility Commands
Add RESET ALL, SHOW ALL (Marko Kreen) Add RESET ALL, SHOW ALL (Marko Kreen)
...@@ -813,7 +828,7 @@ Utility Commands ...@@ -813,7 +828,7 @@ Utility Commands
Fix permission checks for CREATE INDEX (Tom) Fix permission checks for CREATE INDEX (Tom)
Disallow inappropriate use of CREATE/DROP INDEX/TRIGGER/VIEW (Tom) Disallow inappropriate use of CREATE/DROP INDEX/TRIGGER/VIEW (Tom)
_________________________________________________________________ _________________________________________________________________
Data Types and Functions Data Types and Functions
SUM(), AVG(), COUNT() now uses int8 internally for speed (Tom) SUM(), AVG(), COUNT() now uses int8 internally for speed (Tom)
...@@ -859,7 +874,7 @@ Data Types and Functions ...@@ -859,7 +874,7 @@ Data Types and Functions
Some datatype() function calls now evaluated differently Some datatype() function calls now evaluated differently
Add support for Julian and ISO time specifications (Thomas) Add support for Julian and ISO time specifications (Thomas)
_________________________________________________________________ _________________________________________________________________
Internationalization Internationalization
National language support in psql, pg_dump, libpq, and server (Peter E National language support in psql, pg_dump, libpq, and server (Peter E
...@@ -875,7 +890,7 @@ Internationalization ...@@ -875,7 +890,7 @@ Internationalization
Make mic2ascii() non-ASCII aware (Tatsuo) Make mic2ascii() non-ASCII aware (Tatsuo)
Reject invalid multibyte character sequences (Tatsuo) Reject invalid multibyte character sequences (Tatsuo)
_________________________________________________________________ _________________________________________________________________
PL/pgSQL PL/pgSQL
Now uses portals for SELECT loops, allowing huge result sets (Jan) Now uses portals for SELECT loops, allowing huge result sets (Jan)
...@@ -891,25 +906,25 @@ PL/pgSQL ...@@ -891,25 +906,25 @@ PL/pgSQL
Memory leak fix (Jan, Tom) Memory leak fix (Jan, Tom)
Make trailing semicolon optional (Tom) Make trailing semicolon optional (Tom)
_________________________________________________________________ _________________________________________________________________
PL/Perl PL/Perl
New untrusted PL/Perl (Alex Pilosov) New untrusted PL/Perl (Alex Pilosov)
PL/Perl is now built on some platforms even if libperl is not shared ( PL/Perl is now built on some platforms even if libperl is not shared (
Peter E) Peter E)
_________________________________________________________________ _________________________________________________________________
PL/Tcl PL/Tcl
Now reports errorInfo (Vsevolod Lobko) Now reports errorInfo (Vsevolod Lobko)
Add spi_lastoid function (bob@redivi.com) Add spi_lastoid function (bob@redivi.com)
_________________________________________________________________ _________________________________________________________________
PL/Python PL/Python
...is new (Andrew Bosma) ...is new (Andrew Bosma)
_________________________________________________________________ _________________________________________________________________
Psql Psql
\d displays indexes in unique, primary groupings (Christopher Kings-Ly \d displays indexes in unique, primary groupings (Christopher Kings-Ly
...@@ -920,7 +935,7 @@ Psql ...@@ -920,7 +935,7 @@ Psql
) )
Format the correct number of columns for Unicode (Patrice) Format the correct number of columns for Unicode (Patrice)
_________________________________________________________________ _________________________________________________________________
Libpq Libpq
New function PQescapeString() to escape quotes in command strings (Flo New function PQescapeString() to escape quotes in command strings (Flo
...@@ -928,7 +943,7 @@ Libpq ...@@ -928,7 +943,7 @@ Libpq
New function PQescapeBytea() escapes binary strings for use as SQL str New function PQescapeBytea() escapes binary strings for use as SQL str
ing literals ing literals
_________________________________________________________________ _________________________________________________________________
JDBC JDBC
Return OID of INSERT (Ken K) Return OID of INSERT (Ken K)
...@@ -966,7 +981,7 @@ JDBC ...@@ -966,7 +981,7 @@ JDBC
MD5 password encryption support (Jeremy Wohl) MD5 password encryption support (Jeremy Wohl)
Fix to actually use type cache (Ned Wolpert) Fix to actually use type cache (Ned Wolpert)
_________________________________________________________________ _________________________________________________________________
ODBC ODBC
Remove query size limit (Hiroshi) Remove query size limit (Hiroshi)
...@@ -980,7 +995,7 @@ ODBC ...@@ -980,7 +995,7 @@ ODBC
MD5 password encryption support (Bruce) MD5 password encryption support (Bruce)
Add more compatibility functions to odbc.sql (Peter E) Add more compatibility functions to odbc.sql (Peter E)
_________________________________________________________________ _________________________________________________________________
ECPG ECPG
EXECUTE ... INTO implemented (Christof Petig) EXECUTE ... INTO implemented (Christof Petig)
...@@ -994,7 +1009,7 @@ ECPG ...@@ -994,7 +1009,7 @@ ECPG
All function names with external linkage are now prefixed by ECPG All function names with external linkage are now prefixed by ECPG
Fixes for arrays of structures (Michael) Fixes for arrays of structures (Michael)
_________________________________________________________________ _________________________________________________________________
Misc. Interfaces Misc. Interfaces
Python fix fetchone() (Gerhard Haring) Python fix fetchone() (Gerhard Haring)
...@@ -1004,7 +1019,7 @@ Misc. Interfaces ...@@ -1004,7 +1019,7 @@ Misc. Interfaces
Prevent output of default index op class in pg_dump (Tom) Prevent output of default index op class in pg_dump (Tom)
Fix libpgeasy memory leak (Bruce) Fix libpgeasy memory leak (Bruce)
_________________________________________________________________ _________________________________________________________________
Build and Install Build and Install
Configure, dynamic loader, and shared library fixes (Peter E) Configure, dynamic loader, and shared library fixes (Peter E)
...@@ -1023,7 +1038,7 @@ Build and Install ...@@ -1023,7 +1038,7 @@ Build and Install
Rename config.h to pg_config.h (Peter E) Rename config.h to pg_config.h (Peter E)
Reorganize installation layout of header files (Peter E) Reorganize installation layout of header files (Peter E)
_________________________________________________________________ _________________________________________________________________
Source Code Source Code
Remove SEP_CHAR (Bruce) Remove SEP_CHAR (Bruce)
...@@ -1039,7 +1054,7 @@ Source Code ...@@ -1039,7 +1054,7 @@ Source Code
Add 'volatile' usage in spinlock structures Add 'volatile' usage in spinlock structures
Improve signal handling logic (Tom) Improve signal handling logic (Tom)
_________________________________________________________________ _________________________________________________________________
Contrib Contrib
New contrib/rtree_gist (Oleg Bartunov, Teodor Sigaev) New contrib/rtree_gist (Oleg Bartunov, Teodor Sigaev)
...@@ -1055,19 +1070,19 @@ Contrib ...@@ -1055,19 +1070,19 @@ Contrib
New pg_upgrade utility (Bruce) New pg_upgrade utility (Bruce)
Add new pg_resetxlog options (Bruce, Tom) Add new pg_resetxlog options (Bruce, Tom)
_________________________________________________________________ _________________________________________________________________
Release 7.1.3 Release 7.1.3
Release date: 2001-08-15 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. A dump/restore is *not* required for those running 7.1.X.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Remove unused WAL segements of large transactions (Tom) Remove unused WAL segements of large transactions (Tom)
Multiaction rule fix (Tom) Multiaction rule fix (Tom)
PL/pgSQL memory allocation fix (Jan) PL/pgSQL memory allocation fix (Jan)
...@@ -1080,21 +1095,21 @@ Disable COPY TO/FROM a view (Tom) ...@@ -1080,21 +1095,21 @@ Disable COPY TO/FROM a view (Tom)
Cygwin build (Jason Tishler) Cygwin build (Jason Tishler)
_________________________________________________________________ _________________________________________________________________
Release 7.1.2 Release 7.1.2
Release date: 2001-05-11 Release date: 2001-05-11
This has one fix from 7.1.1. 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. A dump/restore is *not* required for those running 7.1.X.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Fix PL/pgSQL SELECTs when returning no rows Fix PL/pgSQL SELECTs when returning no rows
Fix for psql backslash core dump Fix for psql backslash core dump
Referential integrity permission fix Referential integrity permission fix
...@@ -1102,21 +1117,21 @@ Optimizer fixes ...@@ -1102,21 +1117,21 @@ Optimizer fixes
pg_dump cleanups pg_dump cleanups
_________________________________________________________________ _________________________________________________________________
Release 7.1.1 Release 7.1.1
Release date: 2001-05-05 Release date: 2001-05-05
This has a variety of fixes from 7.1. 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. A dump/restore is *not* required for those running 7.1.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Fix for numeric MODULO operator (Tom) Fix for numeric MODULO operator (Tom)
pg_dump fixes (Philip) pg_dump fixes (Philip)
pg_dump can dump 7.0 databases (Philip) pg_dump can dump 7.0 databases (Philip)
...@@ -1133,16 +1148,16 @@ EXTRACT can now take string argument (Thomas) ...@@ -1133,16 +1148,16 @@ EXTRACT can now take string argument (Thomas)
Python fixes (Darcy) Python fixes (Darcy)
_________________________________________________________________ _________________________________________________________________
Release 7.1 Release 7.1
Release date: 2001-04-13 Release date: 2001-04-13
This release focuses on removing limitations that have existed in the This release focuses on removing limitations that have existed in the
PostgreSQL code for many years. PostgreSQL code for many years.
Major changes in this release: Major changes in this release:
Write-ahead Log (WAL) Write-ahead Log (WAL)
To maintain database consistency in case of an operating system To maintain database consistency in case of an operating system
crash, previous releases of PostgreSQL have forced all data crash, previous releases of PostgreSQL have forced all data
...@@ -1151,25 +1166,25 @@ Python fixes (Darcy) ...@@ -1151,25 +1166,25 @@ Python fixes (Darcy)
performance. If you have been using -F in previous releases to performance. If you have been using -F in previous releases to
disable disk flushes, you may want to consider discontinuing disable disk flushes, you may want to consider discontinuing
its use. its use.
TOAST TOAST
TOAST - Previous releases had a compiled-in row length limit, TOAST - Previous releases had a compiled-in row length limit,
typically 8k - 32k. This limit made storage of long text fields typically 8k - 32k. This limit made storage of long text fields
difficult. With TOAST, long rows of any length can be stored difficult. With TOAST, long rows of any length can be stored
with good performance. with good performance.
Outer Joins Outer Joins
We now support outer joins. The UNION/NOT IN workaround for We now support outer joins. The UNION/NOT IN workaround for
outer joins is no longer required. We use the SQL92 outer join outer joins is no longer required. We use the SQL92 outer join
syntax. syntax.
Function Manager Function Manager
The previous C function manager did not handle null values The previous C function manager did not handle null values
properly, nor did it support 64-bit CPU's (Alpha). The new properly, nor did it support 64-bit CPU's (Alpha). The new
function manager does. You can continue using your old custom function manager does. You can continue using your old custom
functions, but you may want to rewrite them in the future to functions, but you may want to rewrite them in the future to
use the new function manager call interface. use the new function manager call interface.
Complex Queries Complex Queries
A large number of complex queries that were unsupported in A large number of complex queries that were unsupported in
previous releases now work. Many combinations of views, previous releases now work. Many combinations of views,
...@@ -1177,15 +1192,15 @@ Python fixes (Darcy) ...@@ -1177,15 +1192,15 @@ Python fixes (Darcy)
tables now work properly. Inherited tables are now accessed by tables now work properly. Inherited tables are now accessed by
default. Subqueries in FROM are now supported. 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 A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release. data from any previous release.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Bug Fixes Bug Fixes
--------- ---------
Many multibyte/Unicode/locale fixes (Tatsuo and others) Many multibyte/Unicode/locale fixes (Tatsuo and others)
...@@ -1373,21 +1388,21 @@ New contrib/pg_control utility (Oliver) ...@@ -1373,21 +1388,21 @@ New contrib/pg_control utility (Oliver)
New FreeBSD tools ipc_check, start-scripts/freebsd New FreeBSD tools ipc_check, start-scripts/freebsd
_________________________________________________________________ _________________________________________________________________
Release 7.0.3 Release 7.0.3
Release date: 2000-11-11 Release date: 2000-11-11
This has a variety of fixes from 7.0.2. 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.*. A dump/restore is *not* required for those running 7.0.*.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Jdbc fixes (Peter) Jdbc fixes (Peter)
Large object fix (Tom) Large object fix (Tom)
Fix lean in COPY WITH OIDS leak (Tom) Fix lean in COPY WITH OIDS leak (Tom)
...@@ -1429,39 +1444,39 @@ Fix for inserting/copying longer multibyte strings into char() data ...@@ -1429,39 +1444,39 @@ Fix for inserting/copying longer multibyte strings into char() data
Fix for crash of backend, on abort (Tom) Fix for crash of backend, on abort (Tom)
_________________________________________________________________ _________________________________________________________________
Release 7.0.2 Release 7.0.2
Release date: 2000-06-05 Release date: 2000-06-05
This is a repackaging of 7.0.1 with added documentation. 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.*. A dump/restore is *not* required for those running 7.*.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Added documentation to tarball. Added documentation to tarball.
_________________________________________________________________ _________________________________________________________________
Release 7.0.1 Release 7.0.1
Release date: 2000-06-01 Release date: 2000-06-01
This is a cleanup release for 7.0. 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. A dump/restore is *not* required for those running 7.0.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Fix many CLUSTER failures (Tom) Fix many CLUSTER failures (Tom)
Allow ALTER TABLE RENAME works on indexes (Tom) Allow ALTER TABLE RENAME works on indexes (Tom)
Fix plpgsql to handle datetime->timestamp and timespan->interval (Bruce) Fix plpgsql to handle datetime->timestamp and timespan->interval (Bruce)
...@@ -1488,50 +1503,50 @@ JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu) ...@@ -1488,50 +1503,50 @@ JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu)
ecpg changes (Michael) ecpg changes (Michael)
_________________________________________________________________ _________________________________________________________________
Release 7.0 Release 7.0
Release date: 2000-05-08 Release date: 2000-05-08
This release contains improvements in many areas, demonstrating the This release contains improvements in many areas, demonstrating the
continued growth of PostgreSQL. There are more improvements and fixes continued growth of PostgreSQL. There are more improvements and fixes
in 7.0 than in any previous release. The developers have confidence in 7.0 than in any previous release. The developers have confidence
that this is the best release yet; we do our best to put out only that this is the best release yet; we do our best to put out only
solid releases, and this one is no exception. solid releases, and this one is no exception.
Major changes in this release: Major changes in this release:
Foreign Keys Foreign Keys
Foreign keys are now implemented, with the exception of PARTIAL Foreign keys are now implemented, with the exception of PARTIAL
MATCH foreign keys. Many users have been asking for this MATCH foreign keys. Many users have been asking for this
feature, and we are pleased to offer it. feature, and we are pleased to offer it.
Optimizer Overhaul Optimizer Overhaul
Continuing on work started a year ago, the optimizer has been Continuing on work started a year ago, the optimizer has been
improved, allowing better query plan selection and faster improved, allowing better query plan selection and faster
performance with less memory usage. performance with less memory usage.
Updated psql Updated psql
psql, our interactive terminal monitor, has been updated with a psql, our interactive terminal monitor, has been updated with a
variety of new features. See the psql manual page for details. variety of new features. See the psql manual page for details.
Join Syntax Join Syntax
SQL92 join syntax is now supported, though only as INNER JOIN SQL92 join syntax is now supported, though only as INNER JOIN
for this release. JOIN, NATURAL JOIN, JOIN/USING, and JOIN/ON for this release. JOIN, NATURAL JOIN, JOIN/USING, and JOIN/ON
are available, as are column correlation names. 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 A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release of PostgreSQL. For those upgrading from data from any previous release of PostgreSQL. For those upgrading from
6.5.*, you may instead use pg_upgrade to upgrade to this release; 6.5.*, you may instead use pg_upgrade to upgrade to this release;
however, a full dump/reload installation is always the most robust however, a full dump/reload installation is always the most robust
method for upgrades. method for upgrades.
Interface and compatibility issues to consider for the new release Interface and compatibility issues to consider for the new release
include: include:
* The date/time types datetime and timespan have been superseded by * The date/time types datetime and timespan have been superseded by
the SQL92-defined types timestamp and interval. Although there has the SQL92-defined types timestamp and interval. Although there has
been some effort to ease the transition by allowing PostgreSQL to been some effort to ease the transition by allowing PostgreSQL to
...@@ -1551,9 +1566,9 @@ Migration to version 7.0 ...@@ -1551,9 +1566,9 @@ Migration to version 7.0
in ambiguity with other types implementing LENGTH such as the in ambiguity with other types implementing LENGTH such as the
geometric types. geometric types.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Bug Fixes Bug Fixes
--------- ---------
Prevent function calls exceeding maximum number of arguments (Tom) Prevent function calls exceeding maximum number of arguments (Tom)
...@@ -1876,43 +1891,43 @@ Fixes for Alpha compiles ...@@ -1876,43 +1891,43 @@ Fixes for Alpha compiles
New multibyte encodings New multibyte encodings
_________________________________________________________________ _________________________________________________________________
Release 6.5.3 Release 6.5.3
Release date: 1999-10-13 Release date: 1999-10-13
This is basically a cleanup release for 6.5.2. We have added a new This is basically a cleanup release for 6.5.2. We have added a new
PgAccess that was missing in 6.5.2, and installed an NT-specific fix. 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.*. A dump/restore is *not* required for those running 6.5.*.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Updated version of pgaccess 0.98 Updated version of pgaccess 0.98
NT-specific patch NT-specific patch
Fix dumping rules on inherited tables Fix dumping rules on inherited tables
_________________________________________________________________ _________________________________________________________________
Release 6.5.2 Release 6.5.2
Release date: 1999-09-15 Release date: 1999-09-15
This is basically a cleanup release for 6.5.1. We have fixed a variety This is basically a cleanup release for 6.5.1. We have fixed a variety
of problems reported by 6.5.1 users. 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.*. A dump/restore is *not* required for those running 6.5.*.
_________________________________________________________________ _________________________________________________________________
Changes Changes
subselect+CASE fixes(Tom) subselect+CASE fixes(Tom)
Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik) Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik)
Fixes for CASE in WHERE join clauses(Tom) Fixes for CASE in WHERE join clauses(Tom)
...@@ -1941,22 +1956,22 @@ Repair incorrect cleanup of heap memory allocation during transaction abort(Tom ...@@ -1941,22 +1956,22 @@ Repair incorrect cleanup of heap memory allocation during transaction abort(Tom
Updated version of pgaccess 0.98 Updated version of pgaccess 0.98
_________________________________________________________________ _________________________________________________________________
Release 6.5.1 Release 6.5.1
Release date: 1999-07-15 Release date: 1999-07-15
This is basically a cleanup release for 6.5. We have fixed a variety This is basically a cleanup release for 6.5. We have fixed a variety
of problems reported by 6.5 users. 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. A dump/restore is *not* required for those running 6.5.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Add NT README file Add NT README file
Portability fixes for linux_ppc, IRIX, linux_alpha, OpenBSD, alpha Portability fixes for linux_ppc, IRIX, linux_alpha, OpenBSD, alpha
Remove QUERY_LIMIT, use SELECT...LIMIT Remove QUERY_LIMIT, use SELECT...LIMIT
...@@ -1982,18 +1997,18 @@ Fix some compiler warnings (Tomoaki Nishiyama) ...@@ -1982,18 +1997,18 @@ Fix some compiler warnings (Tomoaki Nishiyama)
Add Win1250 (Czech) support (Pavel Behal) Add Win1250 (Czech) support (Pavel Behal)
_________________________________________________________________ _________________________________________________________________
Release 6.5 Release 6.5
Release date: 1999-06-09 Release date: 1999-06-09
This release marks a major step in the development team's mastery of This release marks a major step in the development team's mastery of
the source code we inherited from Berkeley. You will see we are now the source code we inherited from Berkeley. You will see we are now
easily adding major features, thanks to the increasing size and easily adding major features, thanks to the increasing size and
experience of our world-wide development team. experience of our world-wide development team.
Here is a brief summary of the more notable changes: Here is a brief summary of the more notable changes:
Multiversion concurrency control(MVCC) Multiversion concurrency control(MVCC)
This removes our old table-level locking, and replaces it with This removes our old table-level locking, and replaces it with
a locking system that is superior to most commercial database a locking system that is superior to most commercial database
...@@ -2007,38 +2022,38 @@ Add Win1250 (Czech) support (Pavel Behal) ...@@ -2007,38 +2022,38 @@ Add Win1250 (Czech) support (Pavel Behal)
systems. So, basically, we no longer are restricted by simple systems. So, basically, we no longer are restricted by simple
table-level locking; we have something better than row-level table-level locking; we have something better than row-level
locking. locking.
Hot backups from pg_dump Hot backups from pg_dump
pg_dump takes advantage of the new MVCC features to give a pg_dump takes advantage of the new MVCC features to give a
consistent database dump/backup while the database stays online consistent database dump/backup while the database stays online
and available for queries. and available for queries.
Numeric data type Numeric data type
We now have a true numeric data type, with user-specified We now have a true numeric data type, with user-specified
precision. precision.
Temporary tables Temporary tables
Temporary tables are guaranteed to have unique names within a Temporary tables are guaranteed to have unique names within a
database session, and are destroyed on session exit. database session, and are destroyed on session exit.
New SQL features New SQL features
We now have CASE, INTERSECT, and EXCEPT statement support. We We now have CASE, INTERSECT, and EXCEPT statement support. We
have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL, SELECT have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL, SELECT
... FOR UPDATE, and an improved LOCK TABLE command. ... FOR UPDATE, and an improved LOCK TABLE command.
Speedups Speedups
We continue to speed up PostgreSQL, thanks to the variety of We continue to speed up PostgreSQL, thanks to the variety of
talents within our team. We have sped up memory allocation, talents within our team. We have sped up memory allocation,
optimization, table joins, and row transfer routines. optimization, table joins, and row transfer routines.
Ports Ports
We continue to expand our port list, this time including We continue to expand our port list, this time including
Windows NT/ix86 and NetBSD/arm32. Windows NT/ix86 and NetBSD/arm32.
Interfaces Interfaces
Most interfaces have new versions, and existing functionality Most interfaces have new versions, and existing functionality
has been improved. has been improved.
Documentation Documentation
New and updated material is present throughout the New and updated material is present throughout the
documentation. New FAQs have been contributed for SGI and AIX documentation. New FAQs have been contributed for SGI and AIX
...@@ -2052,20 +2067,20 @@ Add Win1250 (Czech) support (Pavel Behal) ...@@ -2052,20 +2067,20 @@ Add Win1250 (Czech) support (Pavel Behal)
on obtaining the PostgreSQL source tree via anonymous CVS and on obtaining the PostgreSQL source tree via anonymous CVS and
CVSup. CVSup.
_________________________________________________________________ _________________________________________________________________
Migration to version 6.5 Migration to version 6.5
A dump/restore using pg_dump is required for those wishing to migrate 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 data from any previous release of PostgreSQL. pg_upgrade can *not* be
used to upgrade to this release because the on-disk structure of the used to upgrade to this release because the on-disk structure of the
tables has changed compared to previous releases. tables has changed compared to previous releases.
The new Multiversion Concurrency Control (MVCC) features can give The new Multiversion Concurrency Control (MVCC) features can give
somewhat different behaviors in multiuser environments. *Read and somewhat different behaviors in multiuser environments. *Read and
understand the following section to ensure that your existing understand the following section to ensure that your existing
applications will give you the behavior you need.* applications will give you the behavior you need.*
_________________________________________________________________ _________________________________________________________________
Multiversion Concurrency Control Multiversion Concurrency Control
Because readers in 6.5 don't lock data, regardless of transaction Because readers in 6.5 don't lock data, regardless of transaction
...@@ -2075,32 +2090,32 @@ Multiversion Concurrency Control ...@@ -2075,32 +2090,32 @@ Multiversion Concurrency Control
sometime after the statement or transaction began) nor that the row is sometime after the statement or transaction began) nor that the row is
protected from being deleted or updated by concurrent transactions protected from being deleted or updated by concurrent transactions
before the current transaction does a commit or rollback. before the current transaction does a commit or rollback.
To ensure the actual existence of a row and protect it against To ensure the actual existence of a row and protect it against
concurrent updates one must use "SELECT FOR UPDATE" or an appropriate concurrent updates one must use "SELECT FOR UPDATE" or an appropriate
"LOCK TABLE" statement. This should be taken into account when porting "LOCK TABLE" statement. This should be taken into account when porting
applications from previous releases of PostgreSQL and other applications from previous releases of PostgreSQL and other
environments. environments.
Keep the above in mind if you are using "contrib/refint.*" triggers Keep the above in mind if you are using "contrib/refint.*" triggers
for referential integrity. Additional techniques are required now. One for referential integrity. Additional techniques are required now. One
way is to use "LOCK parent_table IN SHARE ROW EXCLUSIVE MODE" command way is to use "LOCK parent_table IN SHARE ROW EXCLUSIVE MODE" command
if a transaction is going to update/delete a primary key and use "LOCK if a transaction is going to update/delete a primary key and use "LOCK
parent_table IN SHARE MODE" command if a transaction is going to parent_table IN SHARE MODE" command if a transaction is going to
update/insert a foreign key. update/insert a foreign key.
Note: Note that if you run a transaction in SERIALIZABLE mode then Note: Note that if you run a transaction in SERIALIZABLE mode then
you must execute the "LOCK" commands above before execution of any you must execute the "LOCK" commands above before execution of any
DML statement ("SELECT/INSERT/DELETE/UPDATE/FETCH/COPY_TO") in the DML statement ("SELECT/INSERT/DELETE/UPDATE/FETCH/COPY_TO") in the
transaction. transaction.
These inconveniences will disappear in the future when the ability to These inconveniences will disappear in the future when the ability to
read dirty (uncommitted) data (regardless of isolation level) and true read dirty (uncommitted) data (regardless of isolation level) and true
referential integrity will be implemented. referential integrity will be implemented.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Bug Fixes Bug Fixes
--------- ---------
Fix text<->float8 and text<->float4 conversion functions(Thomas) Fix text<->float8 and text<->float4 conversion functions(Thomas)
...@@ -2267,40 +2282,40 @@ Improve file handling to be more uniform, prevent file descriptor leak(Tom) ...@@ -2267,40 +2282,40 @@ Improve file handling to be more uniform, prevent file descriptor leak(Tom)
New install commands for plpgsql(Jan) New install commands for plpgsql(Jan)
_________________________________________________________________ _________________________________________________________________
Release 6.4.2 Release 6.4.2
Release date: 1998-12-20 Release date: 1998-12-20
The 6.4.1 release was improperly packaged. This also has one The 6.4.1 release was improperly packaged. This also has one
additional bug fix. 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.*. A dump/restore is *not* required for those running 6.4.*.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Fix for datetime constant problem on some platforms(Thomas) Fix for datetime constant problem on some platforms(Thomas)
_________________________________________________________________ _________________________________________________________________
Release 6.4.1 Release 6.4.1
Release date: 1998-12-18 Release date: 1998-12-18
This is basically a cleanup release for 6.4. We have fixed a variety This is basically a cleanup release for 6.4. We have fixed a variety
of problems reported by 6.4 users. 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. 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 Add pg_dump -N flag to force double quotes around identifiers. This is
the default(Thomas) the default(Thomas)
Fix for NOT in where clause causing crash(Bruce) Fix for NOT in where clause causing crash(Bruce)
...@@ -2332,16 +2347,16 @@ Add routines to help with single-byte (internal) character type(Thomas) ...@@ -2332,16 +2347,16 @@ Add routines to help with single-byte (internal) character type(Thomas)
Compilation of libpq for Win32 fixes(Magnus) Compilation of libpq for Win32 fixes(Magnus)
Upgrade to PyGreSQL 2.2(D'Arcy) Upgrade to PyGreSQL 2.2(D'Arcy)
_________________________________________________________________ _________________________________________________________________
Release 6.4 Release 6.4
Release date: 1998-10-30 Release date: 1998-10-30
There are *many* new features and improvements in this release. Thanks There are *many* new features and improvements in this release. Thanks
to our developers and maintainers, nearly every aspect of the system to our developers and maintainers, nearly every aspect of the system
has received some attention since the previous release. Here is a has received some attention since the previous release. Here is a
brief, incomplete summary: brief, incomplete summary:
* Views and rules are now functional thanks to extensive new code in * Views and rules are now functional thanks to extensive new code in
the rewrite rules system from Jan Wieck. He also wrote a chapter the rewrite rules system from Jan Wieck. He also wrote a chapter
on it for the Programmer's Guide. on it for the Programmer's Guide.
...@@ -2371,15 +2386,15 @@ Upgrade to PyGreSQL 2.2(D'Arcy) ...@@ -2371,15 +2386,15 @@ Upgrade to PyGreSQL 2.2(D'Arcy)
some attention, and should be more robust for more platforms than some attention, and should be more robust for more platforms than
it has ever been. 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 A dump/restore using pg_dump or pg_dumpall is required for those
wishing to migrate data from any previous release of PostgreSQL. wishing to migrate data from any previous release of PostgreSQL.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Bug Fixes Bug Fixes
--------- ---------
Fix for a tiny memory leak in PQsetdb/PQfinish(Bryan) Fix for a tiny memory leak in PQsetdb/PQfinish(Bryan)
...@@ -2576,33 +2591,33 @@ smarter perl configuration(Brook) ...@@ -2576,33 +2591,33 @@ smarter perl configuration(Brook)
configure uses supplied install-sh if no install script found(Tom) configure uses supplied install-sh if no install script found(Tom)
new Makefile.shlib for shared library configuration(Tom) new Makefile.shlib for shared library configuration(Tom)
_________________________________________________________________ _________________________________________________________________
Release 6.3.2 Release 6.3.2
Release date: 1998-04-07 Release date: 1998-04-07
This is a bug-fix release for 6.3.x. Refer to the release notes for This is a bug-fix release for 6.3.x. Refer to the release notes for
version 6.3 for a more complete summary of new features. version 6.3 for a more complete summary of new features.
Summary: Summary:
* Repairs automatic configuration support for some platforms, * Repairs automatic configuration support for some platforms,
including Linux, from breakage inadvertently introduced in version including Linux, from breakage inadvertently introduced in version
6.3.1. 6.3.1.
* Correctly handles function calls on the left side of BETWEEN and * Correctly handles function calls on the left side of BETWEEN and
LIKE clauses. LIKE clauses.
A dump/restore is NOT required for those running 6.3 or 6.3.1. A make A dump/restore is NOT required for those running 6.3 or 6.3.1. A make
distclean, make, and make install is all that is required. This last distclean, make, and make install is all that is required. This last
step should be performed while the postmaster is not running. You step should be performed while the postmaster is not running. You
should re-link any custom applications that use PostgreSQL libraries. should re-link any custom applications that use PostgreSQL libraries.
For upgrades from pre-6.3 installations, refer to the installation and For upgrades from pre-6.3 installations, refer to the installation and
migration instructions for version 6.3. migration instructions for version 6.3.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Configure detection improvements for tcl/tk(Brook Milligan, Alvin) Configure detection improvements for tcl/tk(Brook Milligan, Alvin)
Manual page improvements(Bruce) Manual page improvements(Bruce)
BETWEEN and LIKE fix(Thomas) BETWEEN and LIKE fix(Thomas)
...@@ -2623,29 +2638,29 @@ Makefile dependency cleanup(Jeroen van Vianen) ...@@ -2623,29 +2638,29 @@ Makefile dependency cleanup(Jeroen van Vianen)
ASSERT fixes(Bruce) ASSERT fixes(Bruce)
_________________________________________________________________ _________________________________________________________________
Release 6.3.1 Release 6.3.1
Release date: 1998-03-23 Release date: 1998-03-23
Summary: Summary:
* Additional support for multibyte character sets. * Additional support for multibyte character sets.
* Repair byte ordering for mixed-endian clients and servers. * Repair byte ordering for mixed-endian clients and servers.
* Minor updates to allowed SQL syntax. * Minor updates to allowed SQL syntax.
* Improvements to the configuration autodetection for installation. * Improvements to the configuration autodetection for installation.
A dump/restore is NOT required for those running 6.3. A make A dump/restore is NOT required for those running 6.3. A make
distclean, make, and make install is all that is required. This last distclean, make, and make install is all that is required. This last
step should be performed while the postmaster is not running. You step should be performed while the postmaster is not running. You
should re-link any custom applications that use PostgreSQL libraries. should re-link any custom applications that use PostgreSQL libraries.
For upgrades from pre-6.3 installations, refer to the installation and For upgrades from pre-6.3 installations, refer to the installation and
migration instructions for version 6.3. migration instructions for version 6.3.
_________________________________________________________________ _________________________________________________________________
Changes Changes
ecpg cleanup/fixes, now version 1.1(Michael Meskes) ecpg cleanup/fixes, now version 1.1(Michael Meskes)
pg_user cleanup(Bruce) pg_user cleanup(Bruce)
large object fix for pg_dump and tclsh (alvin) large object fix for pg_dump and tclsh (alvin)
...@@ -2675,14 +2690,14 @@ Solaris compile fix(Albert Chin-A-Young) ...@@ -2675,14 +2690,14 @@ Solaris compile fix(Albert Chin-A-Young)
Better identify tcl and tk libs and includes(Bruce) Better identify tcl and tk libs and includes(Bruce)
_________________________________________________________________ _________________________________________________________________
Release 6.3 Release 6.3
Release date: 1998-03-01 Release date: 1998-03-01
There are *many* new features and improvements in this release. Here There are *many* new features and improvements in this release. Here
is a brief, incomplete summary: is a brief, incomplete summary:
* Many new SQL features, including full SQL92 subselect capability * Many new SQL features, including full SQL92 subselect capability
(everything is here but target-list subselects). (everything is here but target-list subselects).
* Support for client-side environment variables to specify time zone * Support for client-side environment variables to specify time zone
...@@ -2693,14 +2708,14 @@ Better identify tcl and tk libs and includes(Bruce) ...@@ -2693,14 +2708,14 @@ Better identify tcl and tk libs and includes(Bruce)
permissions have changed. permissions have changed.
* Old-style time travel has been removed. Performance has been * Old-style time travel has been removed. Performance has been
improved. improved.
Note: Bruce Momjian wrote the following notes to introduce the new Note: Bruce Momjian wrote the following notes to introduce the new
release. release.
There are some general 6.3 issues that I want to mention. These are There are some general 6.3 issues that I want to mention. These are
only the big items that can not be described in one sentence. A review only the big items that can not be described in one sentence. A review
of the detailed changes list is still needed. of the detailed changes list is still needed.
First, we now have subselects. Now that we have them, I would like to First, we now have subselects. Now that we have them, I would like to
mention that without subselects, SQL is a very limited language. mention that without subselects, SQL is a very limited language.
Subselects are a major feature, and you should review your code for Subselects are a major feature, and you should review your code for
...@@ -2709,12 +2724,12 @@ Better identify tcl and tk libs and includes(Bruce) ...@@ -2709,12 +2724,12 @@ Better identify tcl and tk libs and includes(Bruce)
may think. Vadim has put us on the big SQL map with subselects, and may think. Vadim has put us on the big SQL map with subselects, and
fully functional ones too. The only thing you can't do with subselects fully functional ones too. The only thing you can't do with subselects
is to use them in the target list. is to use them in the target list.
Second, 6.3 uses Unix domain sockets rather than TCP/IP by default. To Second, 6.3 uses Unix domain sockets rather than TCP/IP by default. To
enable connections from other machines, you have to use the new enable connections from other machines, you have to use the new
postmaster -i option, and of course edit "pg_hba.conf". Also, for this postmaster -i option, and of course edit "pg_hba.conf". Also, for this
reason, the format of "pg_hba.conf" has changed. reason, the format of "pg_hba.conf" has changed.
Third, char() fields will now allow faster access than varchar() or Third, char() fields will now allow faster access than varchar() or
text. Specifically, the text and varchar() have a penalty for access text. Specifically, the text and varchar() have a penalty for access
to any columns after the first column of this type. char() used to to any columns after the first column of this type. char() used to
...@@ -2722,7 +2737,7 @@ Better identify tcl and tk libs and includes(Bruce) ...@@ -2722,7 +2737,7 @@ Better identify tcl and tk libs and includes(Bruce)
that you redesign some of your tables, especially if you have short that you redesign some of your tables, especially if you have short
character columns that you have defined as varchar() or text. This and character columns that you have defined as varchar() or text. This and
other changes make 6.3 even faster than earlier releases. other changes make 6.3 even faster than earlier releases.
We now have passwords definable independent of any Unix file. There We now have passwords definable independent of any Unix file. There
are new SQL USER commands. See the Administrator's Guide for more are new SQL USER commands. See the Administrator's Guide for more
information. There is a new table, pg_shadow, which is used to store information. There is a new table, pg_shadow, which is used to store
...@@ -2730,41 +2745,41 @@ Better identify tcl and tk libs and includes(Bruce) ...@@ -2730,41 +2745,41 @@ Better identify tcl and tk libs and includes(Bruce)
SELECT-able by the postgres super-user. pg_user is now a view of SELECT-able by the postgres super-user. pg_user is now a view of
pg_shadow, and is SELECT-able by PUBLIC. You should keep using pg_user pg_shadow, and is SELECT-able by PUBLIC. You should keep using pg_user
in your application without changes. in your application without changes.
User-created tables now no longer have SELECT permission to PUBLIC by User-created tables now no longer have SELECT permission to PUBLIC by
default. This was done because the ANSI standard requires it. You can default. This was done because the ANSI standard requires it. You can
of course GRANT any permissions you want after the table is created. of course GRANT any permissions you want after the table is created.
System tables continue to be SELECT-able by PUBLIC. System tables continue to be SELECT-able by PUBLIC.
We also have real deadlock detection code. No more sixty-second We also have real deadlock detection code. No more sixty-second
timeouts. And the new locking code implements a FIFO better, so there timeouts. And the new locking code implements a FIFO better, so there
should be less resource starvation during heavy use. should be less resource starvation during heavy use.
Many complaints have been made about inadequate documentation in Many complaints have been made about inadequate documentation in
previous releases. Thomas has put much effort into many new manuals previous releases. Thomas has put much effort into many new manuals
for this release. Check out the doc/ directory. for this release. Check out the doc/ directory.
For performance reasons, time travel is gone, but can be implemented For performance reasons, time travel is gone, but can be implemented
using triggers (see "pgsql/contrib/spi/README"). Please check out the using triggers (see "pgsql/contrib/spi/README"). Please check out the
new \d command for types, operators, etc. Also, views have their own new \d command for types, operators, etc. Also, views have their own
permissions now, not based on the underlying tables, so permissions on permissions now, not based on the underlying tables, so permissions on
them have to be set separately. Check "/pgsql/interfaces" for some new them have to be set separately. Check "/pgsql/interfaces" for some new
ways to talk to PostgreSQL. ways to talk to PostgreSQL.
This is the first release that really required an explanation for This is the first release that really required an explanation for
existing users. In many ways, this was necessary because the new existing users. In many ways, this was necessary because the new
release removes many limitations, and the work-arounds people were release removes many limitations, and the work-arounds people were
using are no longer needed. 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 A dump/restore using pg_dump or pg_dumpall is required for those
wishing to migrate data from any previous release of PostgreSQL. wishing to migrate data from any previous release of PostgreSQL.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Bug Fixes Bug Fixes
--------- ---------
Fix binary cursors broken by MOVE implementation(Vadim) Fix binary cursors broken by MOVE implementation(Vadim)
...@@ -2933,33 +2948,33 @@ Add string functions to regression suite(Thomas) ...@@ -2933,33 +2948,33 @@ Add string functions to regression suite(Thomas)
Expand a few function names formerly truncated to 16 characters(Thomas) Expand a few function names formerly truncated to 16 characters(Thomas)
Remove un-needed malloc() calls and replace with palloc()(Bruce) Remove un-needed malloc() calls and replace with palloc()(Bruce)
_________________________________________________________________ _________________________________________________________________
Release 6.2.1 Release 6.2.1
Release date: 1997-10-17 Release date: 1997-10-17
6.2.1 is a bug-fix and usability release on 6.2. 6.2.1 is a bug-fix and usability release on 6.2.
Summary: Summary:
* Allow strings to span lines, per SQL92. * Allow strings to span lines, per SQL92.
* Include example trigger function for inserting user names on table * Include example trigger function for inserting user names on table
updates. updates.
This is a minor bug-fix release on 6.2. For upgrades from pre-6.2 This is a minor bug-fix release on 6.2. For upgrades from pre-6.2
systems, a full dump/reload is required. Refer to the 6.2 release systems, a full dump/reload is required. Refer to the 6.2 release
notes for instructions. 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 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. version 6.2, but is required from any release prior to 6.2.
In upgrading from version 6.2, if you choose to dump/reload you will In upgrading from version 6.2, if you choose to dump/reload you will
find that avg(money) is now calculated correctly. All other bug fixes find that avg(money) is now calculated correctly. All other bug fixes
take effect upon updating the executables. take effect upon updating the executables.
Another way to avoid dump/reload is to use the following SQL command Another way to avoid dump/reload is to use the following SQL command
from "psql" to update the existing system table: from "psql" to update the existing system table:
update pg_aggregate set aggfinalfn = 'cash_div_flt8' update pg_aggregate set aggfinalfn = 'cash_div_flt8'
...@@ -2968,9 +2983,9 @@ Migration from version 6.2 to version 6.2.1 ...@@ -2968,9 +2983,9 @@ Migration from version 6.2 to version 6.2.1
This will need to be done to every existing database, including This will need to be done to every existing database, including
template1. template1.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Allow TIME and TYPE column names(Thomas) Allow TIME and TYPE column names(Thomas)
Allow larger range of true/false as boolean values(Thomas) Allow larger range of true/false as boolean values(Thomas)
Support output of "now" and "current"(Thomas) Support output of "now" and "current"(Thomas)
...@@ -2984,32 +2999,32 @@ Documented new libpq function to return affected rows, PQcmdTuples(Bruce) ...@@ -2984,32 +2999,32 @@ Documented new libpq function to return affected rows, PQcmdTuples(Bruce)
Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan) Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
_________________________________________________________________ _________________________________________________________________
Release 6.2 Release 6.2
Release date: 1997-10-02 Release date: 1997-10-02
A dump/restore is required for those wishing to migrate data from A dump/restore is required for those wishing to migrate data from
previous releases of PostgreSQL. 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 This migration requires a complete dump of the 6.1 database and a
restore of the database in 6.2. restore of the database in 6.2.
Note that the "pg_dump" and "pg_dumpall" utility from 6.2 should be Note that the "pg_dump" and "pg_dumpall" utility from 6.2 should be
used to dump the 6.1 database. 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 Those migrating from earlier 1.* releases should first upgrade to 1.09
because the COPY output format was improved from the 1.02 release. because the COPY output format was improved from the 1.02 release.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Bug Fixes Bug Fixes
--------- ---------
Fix problems with pg_dump for inheritance, sequences, archive tables(Bruce) Fix problems with pg_dump for inheritance, sequences, archive tables(Bruce)
...@@ -3123,21 +3138,21 @@ Massive commit to run PGINDENT on all *.c and *.h files(Bruce) ...@@ -3123,21 +3138,21 @@ Massive commit to run PGINDENT on all *.c and *.h files(Bruce)
Files moved to /src/tools directory(Bruce) Files moved to /src/tools directory(Bruce)
SPI and Trigger programming guides (Vadim & D'Arcy) SPI and Trigger programming guides (Vadim & D'Arcy)
_________________________________________________________________ _________________________________________________________________
Release 6.1.1 Release 6.1.1
Release date: 1997-07-22 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 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 version 6.1, but is required from any release prior to 6.1. Refer to
the release notes for 6.1 for more details. the release notes for 6.1 for more details.
_________________________________________________________________ _________________________________________________________________
Changes Changes
fix for SET with options (Thomas) fix for SET with options (Thomas)
allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce) allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce)
new psql \connect option allows changing usernames without changing databases new psql \connect option allows changing usernames without changing databases
...@@ -3157,20 +3172,20 @@ allow underscores in usernames(Bruce) ...@@ -3157,20 +3172,20 @@ allow underscores in usernames(Bruce)
pg_dumpall now returns proper status, portability fix(Bruce) pg_dumpall now returns proper status, portability fix(Bruce)
_________________________________________________________________ _________________________________________________________________
Release 6.1 Release 6.1
Release date: 1997-06-08 Release date: 1997-06-08
The regression tests have been adapted and extensively modified for The regression tests have been adapted and extensively modified for
the 6.1 release of PostgreSQL. the 6.1 release of PostgreSQL.
Three new data types (datetime, timespan, and circle) have been added Three new data types (datetime, timespan, and circle) have been added
to the native set of PostgreSQL types. Points, boxes, paths, and to the native set of PostgreSQL types. Points, boxes, paths, and
polygons have had their output formats made consistent across the data polygons have had their output formats made consistent across the data
types. The polygon output in misc.out has only been spot-checked for types. The polygon output in misc.out has only been spot-checked for
correctness relative to the original regression output. correctness relative to the original regression output.
PostgreSQL 6.1 introduces a new, alternate optimizer which uses PostgreSQL 6.1 introduces a new, alternate optimizer which uses
genetic algorithms. These algorithms introduce a random behavior in genetic algorithms. These algorithms introduce a random behavior in
the ordering of query results when the query contains multiple the ordering of query results when the query contains multiple
...@@ -3181,33 +3196,33 @@ pg_dumpall now returns proper status, portability fix(Bruce) ...@@ -3181,33 +3196,33 @@ pg_dumpall now returns proper status, portability fix(Bruce)
inherently unordered (e.g. points and time intervals) and tests inherently unordered (e.g. points and time intervals) and tests
involving those types are explicitly bracketed with "set geqo to involving those types are explicitly bracketed with "set geqo to
'off'" and "reset geqo". 'off'" and "reset geqo".
The interpretation of array specifiers (the curly braces around atomic The interpretation of array specifiers (the curly braces around atomic
values) appears to have changed sometime after the original regression values) appears to have changed sometime after the original regression
tests were generated. The current "./expected/*.out" files reflect tests were generated. The current "./expected/*.out" files reflect
this new interpretation, which may not be correct! this new interpretation, which may not be correct!
The float8 regression test fails on at least some platforms. This is The float8 regression test fails on at least some platforms. This is
due to differences in implementations of pow() and exp() and the due to differences in implementations of pow() and exp() and the
signaling mechanisms used for overflow and underflow conditions. signaling mechanisms used for overflow and underflow conditions.
The "random" results in the random test should cause the "random" test The "random" results in the random test should cause the "random" test
to be "failed", since the regression tests are evaluated using a to be "failed", since the regression tests are evaluated using a
simple diff. However, "random" does not seem to produce random results simple diff. However, "random" does not seem to produce random results
on my test machine (Linux/gcc/i686). 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 This migration requires a complete dump of the 6.0 database and a
restore of the database in 6.1. restore of the database in 6.1.
Those migrating from earlier 1.* releases should first upgrade to 1.09 Those migrating from earlier 1.* releases should first upgrade to 1.09
because the COPY output format was improved from the 1.02 release. because the COPY output format was improved from the 1.02 release.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Bug Fixes Bug Fixes
--------- ---------
packet length checking in library routines packet length checking in library routines
...@@ -3303,29 +3318,29 @@ c++ include file cleanup(Bruce) ...@@ -3303,29 +3318,29 @@ c++ include file cleanup(Bruce)
warn about buggy flex(Bruce) warn about buggy flex(Bruce)
DG/UX, Ultrix, IRIX, AIX portability fixes DG/UX, Ultrix, IRIX, AIX portability fixes
_________________________________________________________________ _________________________________________________________________
Release 6.0 Release 6.0
Release date: 1997-01-29 Release date: 1997-01-29
A dump/restore is required for those wishing to migrate data from A dump/restore is required for those wishing to migrate data from
previous releases of PostgreSQL. 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 This migration requires a complete dump of the 1.09 database and a
restore of the database in 6.0. 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 Those migrating from earlier 1.* releases should first upgrade to 1.09
because the COPY output format was improved from the 1.02 release. because the COPY output format was improved from the 1.02 release.
_________________________________________________________________ _________________________________________________________________
Changes Changes
Bug Fixes Bug Fixes
--------- ---------
ALTER TABLE bug - running postgress process needs to re-read table definition ALTER TABLE bug - running postgress process needs to re-read table definition
...@@ -3432,33 +3447,33 @@ Restructured object file generation/location(Bryan, Marc) ...@@ -3432,33 +3447,33 @@ Restructured object file generation/location(Bryan, Marc)
Restructured port-specific file locations(Bryan, Marc) Restructured port-specific file locations(Bryan, Marc)
Unused/uninialized variables corrected Unused/uninialized variables corrected
_________________________________________________________________ _________________________________________________________________
Release 1.09 Release 1.09
Release date: 1996-11-04 Release date: 1996-11-04
Sorry, we didn't keep track of changes from 1.02 to 1.09. Some of the Sorry, we didn't keep track of changes from 1.02 to 1.09. Some of the
changes listed in 6.0 were actually included in the 1.02.1 to 1.09 changes listed in 6.0 were actually included in the 1.02.1 to 1.09
releases. releases.
_________________________________________________________________ _________________________________________________________________
Release 1.02 Release 1.02
Release date: 1996-08-01 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 Here is a new migration file for 1.02.1. It includes the 'copy' change
and a script to convert old ASCII files. and a script to convert old ASCII files.
Note: The following notes are for the benefit of users who want to Note: The following notes are for the benefit of users who want to
migrate databases from Postgres95 1.01 and 1.02 to Postgres95 migrate databases from Postgres95 1.01 and 1.02 to Postgres95
1.02.1. 1.02.1.
If you are starting afresh with Postgres95 1.02.1 and do not need If you are starting afresh with Postgres95 1.02.1 and do not need
to migrate old databases, you do not need to read any further. to migrate old databases, you do not need to read any further.
In order to upgrade older Postgres95 version 1.01 or 1.02 databases to In order to upgrade older Postgres95 version 1.01 or 1.02 databases to
version 1.02.1, the following steps are required: version 1.02.1, the following steps are required:
1. Start up a new 1.02.1 postmaster 1. Start up a new 1.02.1 postmaster
...@@ -3474,9 +3489,9 @@ Migration from version 1.02 to version 1.02.1 ...@@ -3474,9 +3489,9 @@ Migration from version 1.02 to version 1.02.1
the last two statements in the file because they are already the last two statements in the file because they are already
present in 1.02. This is not a cause for concern. 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 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 stdout generated with a previous version, you will need to run the
attached "sed" script on the ASCII file before loading it into the attached "sed" script on the ASCII file before loading it into the
...@@ -3498,9 +3513,9 @@ eq); ...@@ -3498,9 +3513,9 @@ eq);
create operator !~* (leftarg = varchar, rightarg = text, procedure = texticrege create operator !~* (leftarg = varchar, rightarg = text, procedure = texticrege
xne); xne);
_________________________________________________________________ _________________________________________________________________
Changes Changes
Source code maintenance and development Source code maintenance and development
* worldwide team of volunteers * worldwide team of volunteers
* the source tree now in CVS at ftp.ki.net * the source tree now in CVS at ftp.ki.net
...@@ -3511,7 +3526,7 @@ Enhancements ...@@ -3511,7 +3526,7 @@ Enhancements
* pg_dump now output the schema and/or the data, with many fixes to * pg_dump now output the schema and/or the data, with many fixes to
enhance completeness. enhance completeness.
* psql used in place of monitor in administration shell scripts. * 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 * date/time functions enhanced
* NULL insert/update/comparison fixed/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 * TCL/TK lib and shell fixed to work with both tck7.4/tk4.0 and tcl7.5/tk4.1
...@@ -3527,20 +3542,20 @@ New Ports ...@@ -3527,20 +3542,20 @@ New Ports
* added BSD/OS 2.1 port * added BSD/OS 2.1 port
* added DG/UX port * added DG/UX port
_________________________________________________________________ _________________________________________________________________
Release 1.01 Release 1.01
Release date: 1996-02-23 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 The following notes are for the benefit of users who want to migrate
databases from Postgres95 1.0 to Postgres95 1.01. databases from Postgres95 1.0 to Postgres95 1.01.
If you are starting afresh with Postgres95 1.01 and do not need to If you are starting afresh with Postgres95 1.01 and do not need to
migrate old databases, you do not need to read any further. migrate old databases, you do not need to read any further.
In order to Postgres95 version 1.01 with databases created with In order to Postgres95 version 1.01 with databases created with
Postgres95 version 1.0, the following steps are required: Postgres95 version 1.0, the following steps are required:
1. Set the definition of NAMEDATALEN in "src/Makefile.global" to 16 1. Set the definition of NAMEDATALEN in "src/Makefile.global" to 16
...@@ -3622,9 +3637,9 @@ create operator ~* (leftarg = text, rightarg = text, procedure = texticregexeq) ...@@ -3622,9 +3637,9 @@ create operator ~* (leftarg = text, rightarg = text, procedure = texticregexeq)
create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne
); );
_________________________________________________________________ _________________________________________________________________
Changes Changes
Incompatibilities: Incompatibilities:
* 1.01 is backwards compatible with 1.0 database provided the user * 1.01 is backwards compatible with 1.0 database provided the user
follow the steps outlined in the MIGRATION_from_1.0_to_1.01 file. follow the steps outlined in the MIGRATION_from_1.0_to_1.01 file.
...@@ -3658,14 +3673,14 @@ Bug fixes: ...@@ -3658,14 +3673,14 @@ Bug fixes:
* psql now returns non-zero status on errors when using -c * psql now returns non-zero status on errors when using -c
* applied public patches 1-14 * applied public patches 1-14
_________________________________________________________________ _________________________________________________________________
Release 1.0 Release 1.0
Release date: 1995-09-05 Release date: 1995-09-05
_________________________________________________________________ _________________________________________________________________
Changes Changes
Copyright change: Copyright change:
* The copyright of Postgres 1.0 has been loosened to be freely modifiable * The copyright of Postgres 1.0 has been loosened to be freely modifiable
and modifiable for any purpose. Please read the COPYRIGHT file. and modifiable for any purpose. Please read the COPYRIGHT file.
...@@ -3706,14 +3721,14 @@ Bug fixes: ...@@ -3706,14 +3721,14 @@ Bug fixes:
* btrees with multiple index never worked, now we tell you they don't * btrees with multiple index never worked, now we tell you they don't
work when you try to use them work when you try to use them
_________________________________________________________________ _________________________________________________________________
Postgres95 Release 0.03 Postgres95 Release 0.03
Release date: 1995-07-21 Release date: 1995-07-21
_________________________________________________________________ _________________________________________________________________
Changes Changes
Incompatible changes: Incompatible changes:
* BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS VERSIONS * BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS VERSIONS
(due to system catalog changes and indexing structure changes). (due to system catalog changes and indexing structure changes).
...@@ -3820,14 +3835,14 @@ New utilities: ...@@ -3820,14 +3835,14 @@ New utilities:
New documentation: New documentation:
* the user manual has been revised and libpq documentation added. * the user manual has been revised and libpq documentation added.
_________________________________________________________________ _________________________________________________________________
Postgres95 Release 0.02 Postgres95 Release 0.02
Release date: 1995-05-25 Release date: 1995-05-25
_________________________________________________________________ _________________________________________________________________
Changes Changes
Incompatible changes: Incompatible changes:
* The SQL statement for creating a database is 'CREATE DATABASE' instead * The SQL statement for creating a database is 'CREATE DATABASE' instead
of 'CREATEDB'. Similarly, dropping a database is 'DROP DATABASE' instead of 'CREATEDB'. Similarly, dropping a database is 'DROP DATABASE' instead
...@@ -3862,9 +3877,9 @@ The following bugs have been fixed in postgres95-beta-0.02: ...@@ -3862,9 +3877,9 @@ The following bugs have been fixed in postgres95-beta-0.02:
* CREATE TYPE doesn't accept 'variable' as the internallength * CREATE TYPE doesn't accept 'variable' as the internallength
* wrong result using more than 1 aggregate in a SELECT * wrong result using more than 1 aggregate in a SELECT
_________________________________________________________________ _________________________________________________________________
Postgres95 Release 0.01 Postgres95 Release 0.01
Release date: 1995-05-01 Release date: 1995-05-01
Initial release. Initial release.
<!-- <!--
$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"> <appendix id="release">
...@@ -33,7 +33,7 @@ worries about funny characters. ...@@ -33,7 +33,7 @@ worries about funny characters.
<note> <note>
<title>Release date</title> <title>Release date</title>
<simpara>2002-11-??</simpara> <simpara>2002-11-27</simpara>
</note> </note>
<sect2> <sect2>
......
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