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