database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-26 12:21:12 +03:00
Code Activity

First update of release notes for 7.4.2. Still needs work.

Browse Source
This commit is contained in:
Bruce Momjian
2004-03-05 19:52:39 +00:00
parent 5b6d0a4df7
commit aeda110cb9
2 changed files with 595 additions and 510 deletions
Download Patch File Download Diff File Expand all files Collapse all files

211
HISTORY
View File

@ -1,6 +1,47 @@
Release Notes
Release 7.4.2
Release date: 2004-03-??
This release contains a variety of fixes from 7.4.1.
_________________________________________________________________
Migration to version 7.4.2
A dump/restore is *not* required for those running 7.4.X.
_________________________________________________________________
Changes
As of 2004-03-02
* Fix problems with ALTER TABLE during concurrent access (Tom)
* Improve hash build reliability (Tom)
* Fix statistics alignment bug that could affect optimizer, initdb
required (Tom)
* Optimizer improvements (Tom)
* Permission fix for view updates (Tom)
* Allow non-super users to update pg_settings (Tom)
* Fix for multibyte handling in position() (Korea PostgreSQL Users'
Group)
* Various multibyte fixes
* Fix problem with hitting open file limit, especially on OS X (Tom)
* Have pg_dump set client encoding on restore (Tom)
* Allow ecpg to again use C keywords as column names (Michael)
* Added ecpg WHENEVER NOT_FOUND to SELECT/INSERT/UPDATE/DELETE
(Michael)
* Fix ecpg crash for queries calling set-returning functions
(Michael)
* Various ecpg fixes (Michael)
* Fixes for Borland compiler
* Thread build improvements (Bruce)
* Fix for configure --disable-shared support (Tom)
* Various build fixes
* Various jdbc fixes
_________________________________________________________________
Release 7.4.1
Release date: 2003-12-22
@ -8,7 +49,7 @@
This release contains a variety of fixes from 7.4.
_________________________________________________________________
Migration to version 7.4.1
Migration to version 7.4.1
A dump/restore is *not* required for those running 7.4.
@ -23,7 +64,7 @@ DROP SCHEMA information_schema CASCADE;
Substitute your installation path in the second command.
_________________________________________________________________
Changes
Changes
* Fixed bug in "CREATE SCHEMA" parsing in ECPG (Michael)
* Fix compile error when "--enable-thread-safety" and "--with-perl"
@ -86,7 +127,7 @@ DROP SCHEMA information_schema CASCADE;
Release date: 2003-11-17
_________________________________________________________________
Overview
Overview
Major changes in this release:
@ -187,7 +228,7 @@ DROP SCHEMA information_schema CASCADE;
more like fully-supported data types.
_________________________________________________________________
Migration to version 7.4
Migration to version 7.4
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release.
@ -251,7 +292,7 @@ DROP SCHEMA information_schema CASCADE;
adjacent to operators.
_________________________________________________________________
Changes
Changes
Below you will find a detailed account of the changes between release
7.4 and the previous major release.
@ -854,12 +895,12 @@ Contrib Changes
This release contains a variety of fixes from 7.3.5.
_________________________________________________________________
Migration to version 7.3.6
Migration to version 7.3.6
A dump/restore is *not* required for those running 7.3.*.
_________________________________________________________________
Changes
Changes
* Revert erroneous changes in rule permissions checking
A patch applied in 7.3.3 to fix a corner case in rule permissions
@ -897,12 +938,12 @@ Contrib Changes
This has a variety of fixes from 7.3.4.
_________________________________________________________________
Migration to version 7.3.5
Migration to version 7.3.5
A dump/restore is *not* required for those running 7.3.*.
_________________________________________________________________
Changes
Changes
* Force zero_damaged_pages to be on during recovery from WAL
* Prevent some obscure cases of "variable not in subplan target
@ -944,12 +985,12 @@ Contrib Changes
This has a variety of fixes from 7.3.3.
_________________________________________________________________
Migration to version 7.3.4
Migration to version 7.3.4
A dump/restore is *not* required for those running 7.3.*.
_________________________________________________________________
Changes
Changes
* Repair breakage in timestamp-to-date conversion for dates before
2000
@ -971,12 +1012,12 @@ Contrib Changes
This release contains a variety of fixes for version 7.3.2.
_________________________________________________________________
Migration to version 7.3.3
Migration to version 7.3.3
A dump/restore is *not* required for those running version 7.3.*.
_________________________________________________________________
Changes
Changes
* Repair sometimes-incorrect computation of StartUpID after a crash
* Avoid slowness with lots of deferred triggers in one transaction
@ -1094,12 +1135,12 @@ Contrib Changes
This release contains a variety of fixes for version 7.3.1.
_________________________________________________________________
Migration to version 7.3.2
Migration to version 7.3.2
A dump/restore is *not* required for those running version 7.3.*.
_________________________________________________________________
Changes
Changes
* Restore creation of OID column in CREATE TABLE AS / SELECT INTO
* Fix pg_dump core dump when dumping views having comments
@ -1150,7 +1191,7 @@ Contrib Changes
This release contains a variety of fixes for version 7.3.
_________________________________________________________________
Migration to version 7.3.1
Migration to version 7.3.1
A dump/restore is *not* required for those running version 7.3.
However, it should be noted that the main PostgreSQL interface
@ -1158,7 +1199,7 @@ Contrib Changes
may require recompilation of client code in certain cases.
_________________________________________________________________
Changes
Changes
* Fix a core dump of COPY TO when client/server encodings don't
match (Tom)
@ -1186,7 +1227,7 @@ Contrib Changes
Release date: 2002-11-27
_________________________________________________________________
Overview
Overview
Major changes in this release:
@ -1241,7 +1282,7 @@ Contrib Changes
result types.
_________________________________________________________________
Migration to version 7.3
Migration to version 7.3
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release. If your application examines the
@ -1276,7 +1317,7 @@ Contrib Changes
integer field. Formerly, it was silently interpreted as 0.
_________________________________________________________________
Changes
Changes
Server Operation
@ -1734,12 +1775,12 @@ Contrib
fixes to prevent possible data loss.
_________________________________________________________________
Migration to version 7.2.4
Migration to version 7.2.4
A dump/restore is *not* required for those running version 7.2.*.
_________________________________________________________________
Changes
Changes
* Fix some additional cases of VACUUM "No one parent tuple was
found" error
@ -1765,12 +1806,12 @@ Contrib
fixes to prevent possible data loss.
_________________________________________________________________
Migration to version 7.2.3
Migration to version 7.2.3
A dump/restore is *not* required for those running version 7.2.*.
_________________________________________________________________
Changes
Changes
* Prevent possible compressed transaction log loss (Tom)
* Prevent non-superuser from increasing most recent vacuum info
@ -1788,12 +1829,12 @@ Contrib
This release contains a variety of fixes for version 7.2.1.
_________________________________________________________________
Migration to version 7.2.2
Migration to version 7.2.2
A dump/restore is *not* required for those running version 7.2.*.
_________________________________________________________________
Changes
Changes
* Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)
* Fix for compressed transaction log id wraparound (Tom)
@ -1819,12 +1860,12 @@ Contrib
This release contains a variety of fixes for version 7.2.
_________________________________________________________________
Migration to version 7.2.1
Migration to version 7.2.1
A dump/restore is *not* required for those running version 7.2.
_________________________________________________________________
Changes
Changes
* Ensure that sequence counters do not go backwards after a crash
(Tom)
@ -1854,7 +1895,7 @@ Contrib
Release date: 2002-02-04
_________________________________________________________________
Overview
Overview
This release improves PostgreSQL for use in high-volume applications.
@ -1892,7 +1933,7 @@ Contrib
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.
@ -1921,7 +1962,7 @@ Contrib
clauses, e.g. LIMIT 10 OFFSET 20.
_________________________________________________________________
Changes
Changes
Server Operation
@ -2320,12 +2361,12 @@ Contrib
Release date: 2001-08-15
_________________________________________________________________
Migration to version 7.1.3
Migration to version 7.1.3
A dump/restore is *not* required for those running 7.1.X.
_________________________________________________________________
Changes
Changes
Remove unused WAL segements of large transactions (Tom)
Multiaction rule fix (Tom)
@ -2347,12 +2388,12 @@ Cygwin build (Jason Tishler)
This has one fix from 7.1.1.
_________________________________________________________________
Migration to version 7.1.2
Migration to version 7.1.2
A dump/restore is *not* required for those running 7.1.X.
_________________________________________________________________
Changes
Changes
Fix PL/pgSQL SELECTs when returning no rows
Fix for psql backslash core dump
@ -2369,12 +2410,12 @@ pg_dump cleanups
This has a variety of fixes from 7.1.
_________________________________________________________________
Migration to version 7.1.1
Migration to version 7.1.1
A dump/restore is *not* required for those running 7.1.
_________________________________________________________________
Changes
Changes
Fix for numeric MODULO operator (Tom)
pg_dump fixes (Philip)
@ -2437,13 +2478,13 @@ Python fixes (Darcy)
default. Subqueries in FROM are now supported.
_________________________________________________________________
Migration to version 7.1
Migration to version 7.1
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -2640,12 +2681,12 @@ New FreeBSD tools ipc_check, start-scripts/freebsd
This has a variety of fixes from 7.0.2.
_________________________________________________________________
Migration to version 7.0.3
Migration to version 7.0.3
A dump/restore is *not* required for those running 7.0.*.
_________________________________________________________________
Changes
Changes
Jdbc fixes (Peter)
Large object fix (Tom)
@ -2696,12 +2737,12 @@ Fix for crash of backend, on abort (Tom)
This is a repackaging of 7.0.1 with added documentation.
_________________________________________________________________
Migration to version 7.0.2
Migration to version 7.0.2
A dump/restore is *not* required for those running 7.*.
_________________________________________________________________
Changes
Changes
Added documentation to tarball.
@ -2714,12 +2755,12 @@ Added documentation to tarball.
This is a cleanup release for 7.0.
_________________________________________________________________
Migration to version 7.0.1
Migration to version 7.0.1
A dump/restore is *not* required for those running 7.0.
_________________________________________________________________
Changes
Changes
Fix many CLUSTER failures (Tom)
Allow ALTER TABLE RENAME works on indexes (Tom)
@ -2780,7 +2821,7 @@ ecpg changes (Michael)
are available, as are column correlation names.
_________________________________________________________________
Migration to version 7.0
Migration to version 7.0
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release of PostgreSQL. For those upgrading from
@ -2811,7 +2852,7 @@ ecpg changes (Michael)
geometric types.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -3144,12 +3185,12 @@ New multibyte encodings
PgAccess that was missing in 6.5.2, and installed an NT-specific fix.
_________________________________________________________________
Migration to version 6.5.3
Migration to version 6.5.3
A dump/restore is *not* required for those running 6.5.*.
_________________________________________________________________
Changes
Changes
Updated version of pgaccess 0.98
NT-specific patch
@ -3165,12 +3206,12 @@ Fix dumping rules on inherited tables
of problems reported by 6.5.1 users.
_________________________________________________________________
Migration to version 6.5.2
Migration to version 6.5.2
A dump/restore is *not* required for those running 6.5.*.
_________________________________________________________________
Changes
Changes
subselect+CASE fixes(Tom)
Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik)
@ -3209,12 +3250,12 @@ Updated version of pgaccess 0.98
of problems reported by 6.5 users.
_________________________________________________________________
Migration to version 6.5.1
Migration to version 6.5.1
A dump/restore is *not* required for those running 6.5.
_________________________________________________________________
Changes
Changes
Add NT README file
Portability fixes for linux_ppc, IRIX, linux_alpha, OpenBSD, alpha
@ -3312,7 +3353,7 @@ Add Win1250 (Czech) support (Pavel Behal)
CVSup.
_________________________________________________________________
Migration to version 6.5
Migration to version 6.5
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release of PostgreSQL. pg_upgrade can *not* be
@ -3358,7 +3399,7 @@ Multiversion Concurrency Control
referential integrity will be implemented.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -3535,12 +3576,12 @@ New install commands for plpgsql(Jan)
additional bug fix.
_________________________________________________________________
Migration to version 6.4.2
Migration to version 6.4.2
A dump/restore is *not* required for those running 6.4.*.
_________________________________________________________________
Changes
Changes
Fix for datetime constant problem on some platforms(Thomas)
_________________________________________________________________
@ -3553,12 +3594,12 @@ Fix for datetime constant problem on some platforms(Thomas)
of problems reported by 6.4 users.
_________________________________________________________________
Migration to version 6.4.1
Migration to version 6.4.1
A dump/restore is *not* required for those running 6.4.
_________________________________________________________________
Changes
Changes
Add pg_dump -N flag to force double quotes around identifiers. This is
the default(Thomas)
@ -3631,13 +3672,13 @@ Upgrade to PyGreSQL 2.2(D'Arcy)
it has ever been.
_________________________________________________________________
Migration to version 6.4
Migration to version 6.4
A dump/restore using pg_dump or pg_dumpall is required for those
wishing to migrate data from any previous release of PostgreSQL.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -3860,7 +3901,7 @@ new Makefile.shlib for shared library configuration(Tom)
migration instructions for version 6.3.
_________________________________________________________________
Changes
Changes
Configure detection improvements for tcl/tk(Brook Milligan, Alvin)
Manual page improvements(Bruce)
@ -3903,7 +3944,7 @@ ASSERT fixes(Bruce)
migration instructions for version 6.3.
_________________________________________________________________
Changes
Changes
ecpg cleanup/fixes, now version 1.1(Michael Meskes)
pg_user cleanup(Bruce)
@ -4016,13 +4057,13 @@ Better identify tcl and tk libs and includes(Bruce)
using are no longer needed.
_________________________________________________________________
Migration to version 6.3
Migration to version 6.3
A dump/restore using pg_dump or pg_dumpall is required for those
wishing to migrate data from any previous release of PostgreSQL.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -4210,7 +4251,7 @@ Remove un-needed malloc() calls and replace with palloc()(Bruce)
notes for instructions.
_________________________________________________________________
Migration from version 6.2 to version 6.2.1
Migration from version 6.2 to version 6.2.1
This is a minor bug-fix release. A dump/reload is not required from
version 6.2, but is required from any release prior to 6.2.
@ -4228,7 +4269,7 @@ Remove un-needed malloc() calls and replace with palloc()(Bruce)
template1.
_________________________________________________________________
Changes
Changes
Allow TIME and TYPE column names(Thomas)
Allow larger range of true/false as boolean values(Thomas)
@ -4252,7 +4293,7 @@ Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
previous releases of PostgreSQL.
_________________________________________________________________
Migration from version 6.1 to version 6.2
Migration from version 6.1 to version 6.2
This migration requires a complete dump of the 6.1 database and a
restore of the database in 6.2.
@ -4261,13 +4302,13 @@ Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
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
---------
@ -4388,14 +4429,14 @@ SPI and Trigger programming guides (Vadim & D'Arcy)
Release date: 1997-07-22
_________________________________________________________________
Migration from version 6.1 to version 6.1.1
Migration from version 6.1 to version 6.1.1
This is a minor bug-fix release. A dump/reload is not required from
version 6.1, but is required from any release prior to 6.1. Refer to
the release notes for 6.1 for more details.
_________________________________________________________________
Changes
Changes
fix for SET with options (Thomas)
allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce)
@ -4456,7 +4497,7 @@ pg_dumpall now returns proper status, portability fix(Bruce)
on my test machine (Linux/gcc/i686).
_________________________________________________________________
Migration to version 6.1
Migration to version 6.1
This migration requires a complete dump of the 6.0 database and a
restore of the database in 6.1.
@ -4465,7 +4506,7 @@ pg_dumpall now returns proper status, portability fix(Bruce)
because the COPY output format was improved from the 1.02 release.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -4571,19 +4612,19 @@ DG/UX, Ultrix, IRIX, AIX portability fixes
previous releases of PostgreSQL.
_________________________________________________________________
Migration from version 1.09 to version 6.0
Migration from version 1.09 to version 6.0
This migration requires a complete dump of the 1.09 database and a
restore of the database in 6.0.
_________________________________________________________________
Migration from pre-1.09 to version 6.0
Migration from pre-1.09 to version 6.0
Those migrating from earlier 1.* releases should first upgrade to 1.09
because the COPY output format was improved from the 1.02 release.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
@ -4706,7 +4747,7 @@ Unused/uninialized variables corrected
Release date: 1996-08-01
_________________________________________________________________
Migration from version 1.02 to version 1.02.1
Migration from version 1.02 to version 1.02.1
Here is a new migration file for 1.02.1. It includes the 'copy' change
and a script to convert old ASCII files.
@ -4734,7 +4775,7 @@ Unused/uninialized variables corrected
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
@ -4758,7 +4799,7 @@ create operator !~* (leftarg = varchar, rightarg = text, procedure = texticrege
xne);
_________________________________________________________________
Changes
Changes
Source code maintenance and development
* worldwide team of volunteers
@ -4792,7 +4833,7 @@ New Ports
Release date: 1996-02-23
_________________________________________________________________
Migration from version 1.0 to version 1.01
Migration from version 1.0 to version 1.01
The following notes are for the benefit of users who want to migrate
databases from Postgres95 1.0 to Postgres95 1.01.
@ -4882,7 +4923,7 @@ create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne
);
_________________________________________________________________
Changes
Changes
Incompatibilities:
* 1.01 is backwards compatible with 1.0 database provided the user
@ -4923,7 +4964,7 @@ Bug fixes:
Release date: 1995-09-05
_________________________________________________________________
Changes
Changes
Copyright change:
* The copyright of Postgres 1.0 has been loosened to be freely modifiable
@ -4971,7 +5012,7 @@ Bug fixes:
Release date: 1995-07-21
_________________________________________________________________
Changes
Changes
Incompatible changes:
* BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS VERSIONS
@ -5085,7 +5126,7 @@ New documentation:
Release date: 1995-05-25
_________________________________________________________________
Changes
Changes
Incompatible changes:
* The SQL statement for creating a database is 'CREATE DATABASE' instead

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

@ -1,10 +1,63 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.235.2.19 2004/03/02 00:38:56 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.235.2.20 2004/03/05 19:52:39 momjian Exp $
-->
<appendix id="release">
<title>Release Notes</title>
<sect1 id="release-7-4-2">
<title>Release 7.4.2</title>
<note>
<title>Release date</title>
<simpara>2004-03-??</simpara>
</note>
<para>
This release contains a variety of fixes from 7.4.1.
</para>
<sect2>
<title>Migration to version 7.4.2</title>
<para>
A dump/restore is <emphasis>not</emphasis> required for those
running 7.4.X.
</para>
</sect2>
<sect2>
<title>Changes</title>
<para>As of 2004-03-02</para>
<itemizedlist>
<listitem><para>Fix problems with ALTER TABLE during concurrent access (Tom)</para></listitem>
<listitem><para>Improve hash build reliability (Tom)</para></listitem>
<listitem><para>Fix statistics alignment bug that could affect optimizer, initdb required (Tom)</para></listitem>
<listitem><para>Optimizer improvements (Tom)</para></listitem>
<listitem><para>Permission fix for view updates (Tom)</para></listitem>
<listitem><para>Allow non-super users to update pg_settings (Tom)</para></listitem>
<listitem><para>Fix for multibyte handling in position() (Korea PostgreSQL Users' Group)</para></listitem>
<listitem><para>Various multibyte fixes</para></listitem>
<listitem><para>Fix problem with hitting open file limit, especially on OS X (Tom)</para></listitem>
<listitem><para>Have pg_dump set client encoding on restore (Tom)</para></listitem>
<listitem><para>Allow ecpg to again use C keywords as column names (Michael)</para></listitem>
<listitem><para>Added ecpg WHENEVER NOT_FOUND to SELECT/INSERT/UPDATE/DELETE (Michael)</para></listitem>
<listitem><para>Fix ecpg crash for queries calling set-returning functions (Michael)</para></listitem>
<listitem><para>Various ecpg fixes (Michael)</para></listitem>
<listitem><para>Fixes for Borland compiler</para></listitem>
<listitem><para>Thread build improvements (Bruce)</para></listitem>
<listitem><para>Fix for configure --disable-shared support (Tom)</para></listitem>
<listitem><para>Various build fixes</para></listitem>
<listitem><para>Various jdbc fixes</para></listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-7-4-1">
<title>Release 7.4.1</title>
@ -896,7 +949,7 @@ DROP SCHEMA information_schema CASCADE;
<para>Add Mac OS X Rendezvous server support (Chris Campbell)</para>
<para>
This allows Mac OS X hosts to query the network for available
PostgreSQL servers.
<productname>PostgreSQL</productname> servers.
</para>
</listitem>
@ -954,7 +1007,7 @@ DROP SCHEMA information_schema CASCADE;
<varname>max_connections</> 100, if possible (Tom)
</para>
<para>
Prior versions defaulted to 64 shared buffers so PostgreSQL
Prior versions defaulted to 64 shared buffers so <productname>PostgreSQL</productname>
would start on even very old systems. This release tests the
amount of shared memory allowed by the platform and selects more
reasonable default values if possible. Of course, users are
@ -1019,8 +1072,9 @@ DROP SCHEMA information_schema CASCADE;
<para>
The SQL standard says that an aggregate function appearing
within a nested subquery belongs to the outer query if its
argument contains only outer-query variables. Prior PostgreSQL
releases did not handle this fine point correctly.
argument contains only outer-query variables. Prior
<productname>PostgreSQL</productname> releases did not handle
this fine point correctly.
</para>
</listitem>
@ -1029,8 +1083,9 @@ DROP SCHEMA information_schema CASCADE;
<para>
By default, tables mentioned in the query are automatically
added to the <literal>FROM</> clause if they are not already
there. This is compatible with historic POSTGRES behavior but
is contrary to the SQL standard. This option allows selecting
there. This is compatible with historic
<productname>POSTGRES</productname> behavior but is contrary to
the SQL standard. This option allows selecting
standard-compatible behavior.
</para>
</listitem>
@ -1092,7 +1147,7 @@ DROP SCHEMA information_schema CASCADE;
<listitem>
<para>Fix several zero-column table bugs (Tom)</para>
<para>
PostgreSQL supports zero-column tables. This fixes various bugs
<productname>PostgreSQL</productname> supports zero-column tables. This fixes various bugs
that occur when using such tables.
</para>
</listitem>
@ -1750,7 +1805,8 @@ DROP SCHEMA information_schema CASCADE;
<listitem>
<para>Long options for <application>pg_dump</application> are now available on all platforms</para>
<para>
PostgreSQL now includes its own long-option processing routines.
<productname>PostgreSQL</productname> now includes its own
long-option processing routines.
</para>
</listitem>
</itemizedlist>
@ -1912,7 +1968,7 @@ DROP SCHEMA information_schema CASCADE;
<listitem><para>Allow libpq to compile with Borland C++ compiler (Lester Godwin, Karl Waclawek)</para></listitem>
<listitem><para>Use our own version of <function>getopt_long()</function> if needed (Peter)</para></listitem>
<listitem><para>Convert administration scripts to C (Peter)</para></listitem>
<listitem><para>Bison >= 1.85 is now required to build the PostgreSQL grammar, if building from CVS</para></listitem>
<listitem><para> Bison >= 1.85 is now required to build the <productname>PostgreSQL</> grammar, if building from CVS</para></listitem>
<listitem><para>Merge documentation into one book (Peter)</para></listitem>
<listitem><para>Add Windows compatibility functions (Bruce)</para></listitem>
<listitem><para>Allow client interfaces to compile under MinGW (Bruce)</para></listitem>
@ -2314,9 +2370,9 @@ operations on bytea columns (Joe)</para></listitem>
<para>
A dump/restore is <emphasis>not</emphasis> required for those
running version 7.3. However, it should be noted that the main
PostgreSQL interface library, libpq, has a new major version
number for this release, which may require recompilation of client
code in certain cases.
<productname>PostgreSQL</productname> interface library, libpq,
has a new major version number for this release, which may require
recompilation of client code in certain cases.
</para>
</sect2>
@ -2377,8 +2433,8 @@ operations on bytea columns (Joe)</para></listitem>
<term>Drop Column</term>
<listitem>
<para>
PostgreSQL now supports the <literal>ALTER TABLE ... DROP
COLUMN</literal> functionality.
<productname>PostgreSQL</productname> now supports the
<literal>ALTER TABLE ... DROP COLUMN</literal> functionality.
</para>
</listitem>
</varlistentry>
@ -2401,8 +2457,8 @@ operations on bytea columns (Joe)</para></listitem>
<term>Prepared Queries</term>
<listitem>
<para>
PostgreSQL now supports prepared queries, for improved
performance.
<productname>PostgreSQL</productname> now supports prepared
queries, for improved performance.
</para>
</listitem>
</varlistentry>
@ -2411,11 +2467,11 @@ operations on bytea columns (Joe)</para></listitem>
<term>Dependency Tracking</term>
<listitem>
<para>
PostgreSQL now records object dependencies, which allows
improvements in many areas. <command>DROP</command>
statements now take either <literal>CASCADE</> or
<literal>RESTRICT</> to control whether dependent objects are
also dropped.
<productname>PostgreSQL</productname> now records object
dependencies, which allows improvements in many areas.
<command>DROP</command> statements now take either
<literal>CASCADE</> or <literal>RESTRICT</> to control whether
dependent objects are also dropped.
</para>
</listitem>
</varlistentry>
@ -2595,7 +2651,7 @@ operations on bytea columns (Joe)</para></listitem>
<itemizedlist>
<listitem><para>Add pg_locks view to show locks (Neil)</para></listitem>
<listitem><para>Security fixes for password negotiation memory allocation (Neil)</para></listitem>
<listitem><para>Remove support for version 0 FE/BE protocol (PostgreSQL 6.2 and earlier) (Tom)</para></listitem>
<listitem><para>Remove support for version 0 FE/BE protocol (<productname>PostgreSQL</productname> 6.2 and earlier) (Tom)</para></listitem>
<listitem><para>Reserve the last few backend slots for superusers, add parameter superuser_reserved_connections to control this (Nigel J. Andrews)</para></listitem>
</itemizedlist>
</sect3>
@ -3836,7 +3892,7 @@ Python fixes (Darcy)
<para>
This release focuses on removing limitations that have existed in the
PostgreSQL code for many years.
<productname>PostgreSQL</productname> code for many years.
</para>
<para>
@ -3849,12 +3905,12 @@ Python fixes (Darcy)
</term>
<listitem>
<para>
To maintain database consistency in case
of an operating system crash, previous releases of PostgreSQL have
forced all data modifications to disk before each transaction commit.
With WAL, only one log file must be flushed to disk, greatly improving
performance. If you have been using -F in previous releases to disable
disk flushes, you may want to consider discontinuing its use.
To maintain database consistency in case of an operating system crash,
previous releases of <productname>PostgreSQL</productname> have forced
all data modifications to disk before each transaction commit. With
WAL, only one log file must be flushed to disk, greatly improving
performance. If you have been using -F in previous releases to
disable disk flushes, you may want to consider discontinuing its use.
</para>
</listitem>
</varlistentry>
@ -4358,20 +4414,6 @@ ecpg changes (Michael)
</para>
</listitem>
</varlistentry>
<!--
<varlistentry>
<term>
Upcoming Features
</term>
<listitem>
<para>
In 7.1 or 7.2, we plan to have outer joins, storage for very long rows, and a
write-ahead logging system.
</para>
</listitem>
</varlistentry>
-->
</variablelist>
</para>
@ -4941,17 +4983,18 @@ Add Win1250 (Czech) support (Pavel Behal)
</term>
<listitem>
<para>
This removes our old
table-level locking, and replaces it with a locking system that is
superior to most commercial database systems. In a traditional system,
each row that is modified is locked until committed, preventing reads by
other users. MVCC uses the natural multiversion nature of PostgreSQL
to allow readers to continue reading consistent data during writer
activity. Writers continue to use the compact pg_log transaction
system. This is all performed without having to allocate a lock for
every row like traditional database systems. So, basically, we no
longer are restricted by simple table-level locking;
we have something better than row-level locking.
This removes our old table-level locking, and replaces it with
a locking system that is superior to most commercial database
systems. In a traditional system, each row that is modified
is locked until committed, preventing reads by other users.
MVCC uses the natural multiversion nature of
<productname>PostgreSQL</productname> to allow readers to
continue reading consistent data during writer activity.
Writers continue to use the compact pg_log transaction system.
This is all performed without having to allocate a lock for
every row like traditional database systems. So, basically,
we no longer are restricted by simple table-level locking; we
have something better than row-level locking.
</para>
</listitem>
</varlistentry>
@ -5012,9 +5055,10 @@ Add Win1250 (Czech) support (Pavel Behal)
</term>
<listitem>
<para>
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.
We continue to speed up <productname>PostgreSQL</productname>,
thanks to the variety of talents within our team. We have
sped up memory allocation, optimization, table joins, and row
transfer routines.
</para>
</listitem>
</varlistentry>