Skip to content

P
Postgres FD Implementation
Commit 34cb0f7b authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Update HISTORY and release notes for 7.4.1.

parent 6efdd418
Show whitespace changes
Inline Side-by-side
Showing with 370 additions and 222 deletions
HISTORY
View file @ 34cb0f7b
Release Notes
Release 7.4.1
Release date: 2003-12-15
This has a variety of fixes from 7.4.
_________________________________________________________________
Migration to version 7.4
A dump/restore is *not* required for those running 7.4.
_________________________________________________________________
Changes
Changes as of 2003-12-14
* Fixed bug in CREATE SCHEMA parsing (Michael)
* Fix --enable-thread-safety compile error when used with
--with-perl (Peter)
* Fix for subqueries that used hash joins (Tom)
Certain subqueries that used hash joins would crash because of
improperly shared structures.
* Fix free space map compaction bug (Tom)
This fixes a bug where compaction of the free space map could lead
to a database server shutdown.
* Fix for Borland compiler build of libpq (Bruce)
* Fix netmask() and hostmask() to return the maximum-length masklen
(Tom)
Fix these functions to return values consistent with pre-7.4
releases.
* Several /contrib/pg_autovacuum fixes
Fixes include improper variable initialization, missing vacuum
after TRUNCATE, and duration computation overflow for long
vacuums.
* Allow compile of /contrib/cube under Cygwin (Jason Tishler)
* Fix Solaris use of password file when no passwords are defined
(Tom)
Fix crash on Solaris caused by use of any type of password
authentication when no passwords were defined.
* JDBC fix for thread problems, other fixes
* Fix for index bytea lookups (Joe)
* Fix information schema for bit data types (Peter)
To enable this fix, an initdb is required.
* Force zero_damaged_pages to be on during recovery from WAL
* Prevent some obscure cases of "variable not in subplan target
lists"
* Make PQescapeBytea and byteaout consistent with each other (Joe)
* Escape bytea output for bytes > 0x7e(Joe)
If different client encodings are used for bytea output and input,
it is possible for bytea values to be corrupted by the differing
encodings. This fix escapes all bytes that might be affected.
* Added missing SPI_finish() calls to dblink's
get_tuple_of_interest() (Joe)
_________________________________________________________________
Release 7.4
Release date: 2003-11-17
_________________________________________________________________
Overview
Overview
Major changes in this release:
......@@ -107,7 +162,7 @@
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.
......@@ -171,7 +226,7 @@
adjacent to operators.
_________________________________________________________________
Changes
Changes
Below you will find a detailed account of the changes between release
7.4 and the previous major release.
......@@ -534,7 +589,7 @@ Data Type and Function Changes
values (Tom)
Sixty-second values are needed for leap seconds.
* Allow cidr data type to be cast to text (Tom)
* Disallow invalid time zone names (Tom)
* Disallow invalid time zone names in SET TIMEZONE
* Trim trailing spaces when char is cast to varchar or text (Tom)
* Make float(p) measure the precision "p" in binary digits, not
decimal digits (Tom)
......@@ -586,7 +641,7 @@ Server-Side Language Changes
environment, so the trusted version of PL/Python was removed. If
this situation changes, a version of PL/python that can be used by
non-superusers will be readded.
* Allow polymorphic PL/pgSQL functions (Tom, Joe)
* Allow polymorphic PL/pgSQL functions (Joe, Tom)
* Allow polymorphic SQL functions (Joe)
* Improved compiled function caching mechanism in PL/pgSQL with full
support for polymorphism (Joe)
......@@ -767,6 +822,53 @@ Contrib Changes
* Remove array module because features now included by default (Joe)
_________________________________________________________________
Release 7.3.5
Release date: 2003-12-03
This has a variety of fixes from 7.3.4.
_________________________________________________________________
Migration to version 7.3.5
A dump/restore is *not* required for those running 7.3.*.
_________________________________________________________________
Changes
* Force zero_damaged_pages to be on during recovery from WAL
* Prevent some obscure cases of "variable not in subplan target
lists"
* Force stats processes to detach from shared memory, ensuring
cleaner shutdown
* Make PQescapeBytea and byteaout consistent with each other (Joe)
* Added missing SPI_finish() calls to dblink's
get_tuple_of_interest() (Joe)
* Fix for possible foreign key violation when rule rewrites INSERT
(Jan)
* Support qualified type names in PL/Tcl's spi_prepare command (Jan)
* Make pg_dump handle a procedural language handler located in
pg_catalog
* Make pg_dump handle cases where a custom opclass is in another
schema
* Make pg_dump dump binary-compatible casts correctly (Jan)
* Fix insertion of expressions containing subqueries into rule
bodies
* Fix incorrect argument processing in clusterdb script (Anand
Ranganathan)
* Fix problems with dropped columns in plpython triggers
* Repair problems with to_char() reading past end of its input
string (Karel)
* Fix GB18030 mapping errors (Tatsuo)
* Fix several problems with SSL error handling and asynchronous SSL
I/O
* Remove ability to bind a list of values to a single parameter in
JDBC (prevents possible SQL-injection attacks)
* Fix some errors in HAVE_INT64_TIMESTAMP code paths
* Fix corner case for btree search in parallel with first root page
split
_________________________________________________________________
Release 7.3.4
Release date: 2003-07-24
......@@ -774,12 +876,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
......@@ -801,12 +903,12 @@ Contrib Changes
This release contains of 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
......@@ -924,12 +1026,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
......@@ -980,7 +1082,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
......@@ -988,7 +1090,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)
......@@ -1016,7 +1118,7 @@ Contrib Changes
Release date: 2002-11-27
_________________________________________________________________
Overview
Overview
Major changes in this release:
......@@ -1071,7 +1173,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
......@@ -1106,7 +1208,7 @@ Contrib Changes
integer field. Formerly, it was silently interpreted as 0.
_________________________________________________________________
Changes
Changes
Server Operation
......@@ -1564,12 +1666,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
......@@ -1595,12 +1697,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
......@@ -1618,12 +1720,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)
......@@ -1649,12 +1751,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)
......@@ -1684,7 +1786,7 @@ Contrib
Release date: 2002-02-04
_________________________________________________________________
Overview
Overview
This release improves PostgreSQL for use in high-volume applications.
......@@ -1722,7 +1824,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.
......@@ -1751,7 +1853,7 @@ Contrib
clauses, e.g. LIMIT 10 OFFSET 20.
_________________________________________________________________
Changes
Changes
Server Operation
......@@ -2150,12 +2252,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)
......@@ -2177,12 +2279,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
......@@ -2199,12 +2301,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)
......@@ -2267,13 +2369,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
---------
......@@ -2470,12 +2572,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)
......@@ -2526,12 +2628,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.
......@@ -2544,12 +2646,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)
......@@ -2610,7 +2712,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
......@@ -2641,7 +2743,7 @@ ecpg changes (Michael)
geometric types.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
......@@ -2974,12 +3076,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
......@@ -2995,12 +3097,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)
......@@ -3039,12 +3141,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
......@@ -3142,7 +3244,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
......@@ -3188,7 +3290,7 @@ Multiversion Concurrency Control
referential integrity will be implemented.
_________________________________________________________________
Changes
Changes
Bug Fixes
---------
......@@ -3365,12 +3467,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)
_________________________________________________________________
......@@ -3383,12 +3485,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)
......@@ -3461,13 +3563,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
---------
......@@ -3690,7 +3792,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)
......@@ -3733,7 +3835,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)
......@@ -3846,13 +3948,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
---------
......@@ -4040,7 +4142,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.
......@@ -4058,7 +4160,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)
......@@ -4082,7 +4184,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.
......@@ -4091,13 +4193,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
---------
......@@ -4218,14 +4320,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)
......@@ -4286,7 +4388,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.
......@@ -4295,7 +4397,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
---------
......@@ -4401,19 +4503,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
---------
......@@ -4536,7 +4638,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.
......@@ -4564,7 +4666,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
......@@ -4588,7 +4690,7 @@ create operator !~* (leftarg = varchar, rightarg = text, procedure = texticrege
xne);
_________________________________________________________________
Changes
Changes
Source code maintenance and development
* worldwide team of volunteers
......@@ -4622,7 +4724,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.
......@@ -4712,7 +4814,7 @@ create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne
);
_________________________________________________________________
Changes
Changes
Incompatibilities:
* 1.01 is backwards compatible with 1.0 database provided the user
......@@ -4753,7 +4855,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
......@@ -4801,7 +4903,7 @@ Bug fixes:
Release date: 1995-07-21
_________________________________________________________________
Changes
Changes
Incompatible changes:
* BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS VERSIONS
......@@ -4915,7 +5017,7 @@ New documentation:
Release date: 1995-05-25
_________________________________________________________________
Changes
Changes
Incompatible changes:
* The SQL statement for creating a database is 'CREATE DATABASE' instead
......
doc/src/sgml/Makefile
View file @ 34cb0f7b
......@@ -2,7 +2,7 @@
#
# PostgreSQL documentation makefile
#
# $PostgreSQL: pgsql/doc/src/sgml/Makefile,v 1.61 2003/12/11 22:10:51 petere Exp $
# $PostgreSQL: pgsql/doc/src/sgml/Makefile,v 1.62 2003/12/15 22:24:59 momjian Exp $
#
#----------------------------------------------------------------------------
......@@ -184,13 +184,13 @@ INSTALL.html: standalone-install.sgml installation.sgml version.sgml
$(JADE.text) -V nochunks standalone-install.sgml installation.sgml >$@
HISTORY.html: release.sgml
( echo '<!doctype appendix PUBLIC "-//OASIS//DTD DocBook V3.1//EN">'; \
( echo '<!doctype appendix PUBLIC "-//OASIS//DTD DocBook V4.2//EN">'; \
cat $< ) >tempfile_HISTORY.sgml
$(JADE.text) -V nochunks tempfile_HISTORY.sgml >$@
rm tempfile_HISTORY.sgml
regress_README.html: regress.sgml
( echo '<!doctype chapter PUBLIC "-//OASIS//DTD DocBook V3.1//EN" ['; \
( echo '<!doctype chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN" ['; \
echo '<!entity % standalone-ignore "IGNORE"> ]>'; \
cat $< ) >tempfile_regress_README.sgml
$(JADE.text) -V nochunks tempfile_regress_README.sgml >$@
......
doc/src/sgml/release.sgml
View file @ 34cb0f7b
<!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.246 2003/12/02 16:14:12 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.247 2003/12/15 22:24:59 momjian Exp $
-->
<appendix id="release">
<title>Release Notes</title>
<sect1 id="release-7-4-1">
<title>Release 7.4.1</title>
<note>
<title>Release date</title>
<simpara>2003-12-15</simpara>
</note>
<para>
This has a variety of fixes from 7.4.
</para>
<sect2>
<title>Migration to version 7.4</title>
<para>
A dump/restore is <emphasis>not</emphasis> required for those
running 7.4.
</para>
</sect2>
<sect2>
<title>Changes</title>
<para>Changes as of 2003-12-14</para>
<itemizedlist>
<listitem><para>Fixed bug in CREATE SCHEMA parsing (Michael)</para></listitem>
<listitem><para>Fix --enable-thread-safety compile error when used with --with-perl (Peter)</para></listitem>
<listitem><para>Fix for subqueries that used hash joins (Tom)</para>
<para>
Certain subqueries that used hash joins would crash because of
improperly shared structures.
</para></listitem>
<listitem><para>Fix free space map compaction bug (Tom)</para>
<para>
This fixes a bug where compaction of the free space map could lead
to a database server shutdown.
</para>
</listitem>
<listitem><para>Fix for Borland compiler build of libpq (Bruce)</para></listitem>
<listitem><para>Fix netmask() and hostmask() to return the maximum-length masklen (Tom)</para>
<para>
Fix these functions to return values consistent with pre-7.4
releases.
</para>
</listitem>
<listitem><para>Several /contrib/pg_autovacuum fixes</para>
<para>
Fixes include improper variable initialization, missing vacuum after
TRUNCATE, and duration computation overflow for long vacuums.
</para>
</listitem>
<listitem><para>Allow compile of /contrib/cube under Cygwin (Jason Tishler)</para></listitem>
<listitem><para>Fix Solaris use of password file when no passwords are defined (Tom)</para>
<para>
Fix crash on Solaris caused by use of any type of password
authentication when no passwords were defined.
</para>
</listitem>
<listitem><para>JDBC fix for thread problems, other fixes</para></listitem>
<listitem><para>Fix for index bytea lookups (Joe)</para></listitem>
<listitem><para>Fix information schema for bit data types (Peter)</para>
<para>
To enable this fix, an initdb is required.
</para>
</listitem>
<listitem><para>Force zero_damaged_pages to be on during recovery from WAL</para></listitem>
<listitem><para>Prevent some obscure cases of <quote>variable not in subplan target lists</para></listitem>
<listitem><para>Make PQescapeBytea and byteaout consistent with each other (Joe)</para>
<listitem><para>Escape bytea output for bytes > 0x7e(Joe)</para>
<para>
If different client encodings are used for bytea output and input, it
is possible for bytea values to be corrupted by the differing
encodings. This fix escapes all bytes that might be affected.
</para>
</listitem>
<listitem><para>Added missing SPI_finish() calls to dblink's get_tuple_of_interest() (Joe)</para></listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-7-4">
<title>Release 7.4</title>
......@@ -1882,64 +1965,26 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.246 2003/12/02 16:14:12 tgl Exp
<title>Changes</title>
<itemizedlist>
<listitem><para>
Force zero_damaged_pages to be on during recovery from WAL
</para></listitem>
<listitem><para>
Prevent some obscure cases of <quote>variable not in subplan target lists</>
</para></listitem>
<listitem><para>
Force stats processes to detach from shared memory, ensuring cleaner shutdown
</para></listitem>
<listitem><para>
Make PQescapeBytea and byteaout consistent with each other (Joe)
</para></listitem>
<listitem><para>
Added missing SPI_finish() calls to get_tuple_of_interest() (Joe)
</para></listitem>
<listitem><para>
Fix for possible foreign key violation when rule rewrites INSERT (Jan)
</para></listitem>
<listitem><para>
Support qualified type names in PL/Tcl's spi_prepare command (Jan)
</para></listitem>
<listitem><para>
Make pg_dump handle a procedural language handler located in pg_catalog
</para></listitem>
<listitem><para>
Make pg_dump handle cases where a custom opclass is in another schema
</para></listitem>
<listitem><para>
Make pg_dump dump binary-compatible casts correctly (Jan)
</para></listitem>
<listitem><para>
Fix insertion of expressions containing subqueries into rule bodies
</para></listitem>
<listitem><para>
Fix incorrect argument processing in clusterdb script (Anand Ranganathan)
</para></listitem>
<listitem><para>
Fix problems with dropped columns in plpython triggers
</para></listitem>
<listitem><para>
Repair problems with to_char() reading past end of its input string (Karel)
</para></listitem>
<listitem><para>
Fix GB18030 mapping errors (Tatsuo)
</para></listitem>
<listitem><para>
Fix several problems with SSL error handling and asynchronous SSL I/O
</para></listitem>
<listitem><para>
Remove ability to bind a list of values to a single parameter in JDBC
(prevents possible SQL-injection attacks)
</para></listitem>
<listitem><para>
Fix some errors in HAVE_INT64_TIMESTAMP code paths
</para></listitem>
<listitem><para>
Fix corner case for btree search in parallel with first root page split
</para></listitem>
<listitem><para>Force zero_damaged_pages to be on during recovery from WAL</para></listitem>
<listitem><para>Prevent some obscure cases of <quote>variable not in subplan target lists</para></listitem>
<listitem><para>Force stats processes to detach from shared memory, ensuring cleaner shutdown</para></listitem>
<listitem><para>Make PQescapeBytea and byteaout consistent with each other (Joe)</para></listitem>
<listitem><para>Added missing SPI_finish() calls to dblink's get_tuple_of_interest() (Joe)</para></listitem>
<listitem><para>Fix for possible foreign key violation when rule rewrites INSERT (Jan)</para></listitem>
<listitem><para>Support qualified type names in PL/Tcl's spi_prepare command (Jan)</para></listitem>
<listitem><para>Make pg_dump handle a procedural language handler located in pg_catalog</para></listitem>
<listitem><para>Make pg_dump handle cases where a custom opclass is in another schema</para></listitem>
<listitem><para>Make pg_dump dump binary-compatible casts correctly (Jan)</para></listitem>
<listitem><para>Fix insertion of expressions containing subqueries into rule bodies</para></listitem>
<listitem><para>Fix incorrect argument processing in clusterdb script (Anand Ranganathan)</para></listitem>
<listitem><para>Fix problems with dropped columns in plpython triggers</para></listitem>
<listitem><para>Repair problems with to_char() reading past end of its input string (Karel)</para></listitem>
<listitem><para>Fix GB18030 mapping errors (Tatsuo)</para></listitem>
<listitem><para>Fix several problems with SSL error handling and asynchronous SSL I/O</para></listitem>
<listitem><para>Remove ability to bind a list of values to a single parameter in JDBC
(prevents possible SQL-injection attacks)</para></listitem>
<listitem><para>Fix some errors in HAVE_INT64_TIMESTAMP code paths</para></listitem>
<listitem><para>Fix corner case for btree search in parallel with first root page split</para></listitem>
</itemizedlist>
</sect2>
......@@ -7351,3 +7396,4 @@ sgml-local-catalogs:("/usr/lib/sgml/catalog")
sgml-local-ecat-files:nil
End:
-->
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