From 465ae004ce61044e233c272b1e83d60f3fa087d9 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 11 Sep 2007 17:19:15 +0000 Subject: [PATCH] Stamp --- doc/src/sgml/release.sgml | 453 ++++++++++++++++++++++++-------------- 1 file changed, 284 insertions(+), 169 deletions(-) diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 74e5b3db7df..c6d86757492 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,10 +1,92 @@ + Release Notes + + Release 7.4.18 + + + Release date + 2007-09-17 + + + + This release contains fixes from 7.4.17. + + + + Migration to version 7.4.18 + + + A dump/restore is not required for those running 7.4.X. However, + if you are upgrading from a version earlier than 7.4.11, see the release + notes for 7.4.11. + + + + + + Changes + + + + + + Fix excessively SSL log error messages (Tom) + + + + + + Allow CREATE DOMAIN ... DEFAULT NULL (Tom) + + + + + + Require non-superusers who use /contrib/dblink to use only password + authentication, as a security measure (Joe) + + + + + + + + Release 7.4.17 @@ -142,7 +224,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.235.2.54 2007/04/20 03:28: - + Release 7.4.15 @@ -206,11 +288,13 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.235.2.54 2007/04/20 03:28: to_number() and to_char(numeric) are now STABLE, not IMMUTABLE, for - new initdb installs (Tom) + new initdb + installs (Tom) - This is because lc_numeric can potentially + This is because lc_numeric can potentially change the output of these functions. @@ -229,7 +313,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.235.2.54 2007/04/20 03:28: - + Release 7.4.14 @@ -274,7 +358,7 @@ ANYARRAY - + Release 7.4.13 @@ -299,7 +383,7 @@ ANYARRAY Full security against the SQL-injection attacks described in - CVE-2006-2313 and CVE-2006-2314 may require changes in application + CVE-2006-2313 and CVE-2006-2314 might require changes in application code. If you have applications that embed untrustworthy strings into SQL commands, you should examine them as soon as possible to ensure that they are using recommended escaping techniques. In @@ -331,7 +415,7 @@ literals. By default, \' is rejected only when GB18030, or UHC), which is the scenario in which SQL injection is possible. A new configuration parameter backslash_quote is available to adjust this behavior when needed. Note that full security against -CVE-2006-2314 may require client-side changes; the purpose of +CVE-2006-2314 might require client-side changes; the purpose of backslash_quote is in part to make it obvious that insecure clients are insecure. @@ -379,7 +463,7 @@ Fuhr) - + Release 7.4.12 @@ -404,7 +488,7 @@ Fuhr) Changes - + Fix potential crash in SET @@ -440,7 +524,7 @@ and isinf during configure (Tom) - + Release 7.4.11 @@ -468,7 +552,7 @@ and isinf during configure (Tom) Changes - + Fix for protocol-level Describe messages issued @@ -484,7 +568,7 @@ to ensure that plperl won't change the locale later This fixes a problem that occurred if the postmaster was started with environment variables specifying a different locale than what initdb had been told. Under these conditions, any use of -plperl was likely to lead to corrupt indexes. You may need +plperl was likely to lead to corrupt indexes. You might need REINDEX to fix existing indexes on textual columns if this has happened to you. @@ -505,7 +589,7 @@ what's actually returned by the query (Joe) - + Release 7.4.10 @@ -530,7 +614,7 @@ what's actually returned by the query (Joe) Changes - + Fix race condition in transaction log management @@ -556,7 +640,7 @@ table has been dropped - + Release 7.4.9 @@ -623,7 +707,7 @@ code - + Release 7.4.8 @@ -670,7 +754,7 @@ code It is strongly recommended that all installations repair these errors, either by initdb or by following the manual repair procedures given below. The errors at least allow unprivileged database users to crash - their server process, and may allow unprivileged users to gain the + their server process, and might allow unprivileged users to gain the privileges of a database superuser. @@ -688,7 +772,7 @@ WHERE pronamespace = 11 AND pronargs = 5 COMMIT; - Next, if you have installed contrib/tsearch2, do + Next, if you have installed contrib/tsearch2, do: BEGIN; @@ -717,12 +801,12 @@ COMMIT; template databases then any subsequently created databases will contain the same errors. template1 can be fixed in the same way as any other database, but fixing template0 requires - additional steps. First, from any database issue + additional steps. First, from any database issue: UPDATE pg_database SET datallowconn = true WHERE datname = 'template0'; Next connect to template0 and perform the above repair - procedures. Finally, do + procedures. Finally, do: -- re-freeze template0: VACUUM FREEZE; @@ -891,7 +975,7 @@ GMT Repair possible failure to update hint bits on disk -Under rare circumstances this oversight could lead to +Under rare circumstances this oversight could lead to could not access transaction status failures, which qualifies it as a potential-data-loss bug. @@ -1051,7 +1135,7 @@ aggregate plan Fix error in COPY IN termination when using the old network protocol (ljb) Several important fixes in pg_autovacuum, including fixes for large tables, unsigned oids, stability, temp tables, and debug mode -(Matthew T. O'Connor) +(Matthew T. O'Connor) Fix problem with reading tar-format dumps on NetBSD and BSD/OS (Bruce) Several JDBC fixes Fix ALTER SEQUENCE RESTART where last_value equals the restart value (Tom) @@ -1094,7 +1178,7 @@ names from outer query levels. A dump/restore is not required for those running 7.4.X. However, - it may be advisable as the easiest method of incorporating fixes for + it might be advisable as the easiest method of incorporating fixes for two errors that have been found in the initial contents of 7.4.X system catalogs. A dump/initdb/reload sequence using 7.4.2's initdb will automatically correct these problems. @@ -1134,7 +1218,7 @@ VACUUM pg_statistic; UPDATE pg_type SET typalign = 'd' WHERE oid = 2277; -- this should update 6 rows: UPDATE pg_attribute SET attalign = 'd' WHERE atttypid = 2277; --- +-- -- At this point you MUST start a fresh backend to avoid a crash! -- -- repopulate pg_statistic: @@ -1160,12 +1244,12 @@ GRANT SELECT, UPDATE ON pg_settings TO PUBLIC; template databases then any subsequently created databases will contain the same errors. template1 can be fixed in the same way as any other database, but fixing template0 requires - additional steps. First, from any database issue + additional steps. First, from any database issue: UPDATE pg_database SET datallowconn = true WHERE datname = 'template0'; Next connect to template0 and perform the above repair - procedures. Finally, do + procedures. Finally, do: -- re-freeze template0: VACUUM FREEZE; @@ -1205,7 +1289,7 @@ inconveniences associated with the i/I problem. Other minor pg_dump fixes Allow ecpg to again use C keywords as column names (Michael) Added ecpg WHENEVER NOT_FOUND to -SELECT/INSERT/UPDATE/DELETE (Michael) +SELECT/INSERT/UPDATE/DELETE (Michael) Fix ecpg crash for queries calling set-returning functions (Michael) Various other ecpg fixes (Michael) Fixes for Borland compiler @@ -1612,13 +1696,13 @@ DROP SCHEMA information_schema CASCADE; Migration to version 7.4 - + A dump/restore using pg_dump is required for those wishing to migrate data from any previous release. - + Observe the following incompatibilities: @@ -1648,7 +1732,7 @@ DROP SCHEMA information_schema CASCADE; Inner joins using the explicit JOIN syntax - may behave differently because they are now better + might behave differently because they are now better optimized. @@ -2615,7 +2699,7 @@ DROP SCHEMA information_schema CASCADE; - Arrays may now be specified as ARRAY[1,2,3], + Arrays can now be specified as ARRAY[1,2,3], ARRAY[['a','b'],['c','d']], or ARRAY[ARRAY[ARRAY[2]]] (Joe) @@ -2941,7 +3025,7 @@ DROP SCHEMA information_schema CASCADE; - Have pg_dumpall use GRANT/REVOKE to dump database-level privleges (Tom) + Have pg_dumpall use GRANT/REVOKE to dump database-level privileges (Tom) @@ -3189,6 +3273,52 @@ DROP SCHEMA information_schema CASCADE; + + Release 7.3.20 + + + Release date + 2007-09-17 + + + + This release contains fixes from 7.3.19. + + + + Migration to version 7.3.20 + + + A dump/restore is not required for those running 7.3.X. However, + if you are upgrading from a version earlier than 7.3.13, see the release + notes for 7.3.13. + + + + + + Changes + + + + + + Allow CREATE DOMAIN ... DEFAULT NULL (Tom) + + + + + + Require non-superusers who use /contrib/dblink to use only password + authentication, as a security measure (Joe) + + + + + + + + Release 7.3.19 @@ -3339,11 +3469,13 @@ DROP SCHEMA information_schema CASCADE; to_number() and to_char(numeric) are now STABLE, not IMMUTABLE, for - new initdb installs (Tom) + new initdb + installs (Tom) - This is because lc_numeric can potentially + This is because lc_numeric can potentially change the output of these functions. @@ -3362,7 +3494,7 @@ DROP SCHEMA information_schema CASCADE; - + Release 7.3.16 @@ -3389,7 +3521,7 @@ DROP SCHEMA information_schema CASCADE; Changes - + Fix corner cases in pattern matching for psql's \d commands Fix index-corrupting bugs in /contrib/ltree @@ -3404,7 +3536,7 @@ DROP SCHEMA information_schema CASCADE; - + Release 7.3.15 @@ -3429,7 +3561,7 @@ DROP SCHEMA information_schema CASCADE; Full security against the SQL-injection attacks described in - CVE-2006-2313 and CVE-2006-2314 may require changes in application + CVE-2006-2313 and CVE-2006-2314 might require changes in application code. If you have applications that embed untrustworthy strings into SQL commands, you should examine them as soon as possible to ensure that they are using recommended escaping techniques. In @@ -3461,7 +3593,7 @@ literals. By default, \' is rejected only when GB18030, or UHC), which is the scenario in which SQL injection is possible. A new configuration parameter backslash_quote is available to adjust this behavior when needed. Note that full security against -CVE-2006-2314 may require client-side changes; the purpose of +CVE-2006-2314 might require client-side changes; the purpose of backslash_quote is in part to make it obvious that insecure clients are insecure. @@ -3496,7 +3628,7 @@ Fuhr) - + Release 7.3.14 @@ -3521,7 +3653,7 @@ Fuhr) Changes - + Fix potential crash in SET @@ -3553,7 +3685,7 @@ and isinf during configure (Tom) - + Release 7.3.13 @@ -3581,7 +3713,7 @@ and isinf during configure (Tom) Changes - + Fix character string comparison for locales that consider @@ -3594,7 +3726,7 @@ to ensure that plperl won't change the locale later This fixes a problem that occurred if the postmaster was started with environment variables specifying a different locale than what initdb had been told. Under these conditions, any use of -plperl was likely to lead to corrupt indexes. You may need +plperl was likely to lead to corrupt indexes. You might need REINDEX to fix existing indexes on textual columns if this has happened to you. @@ -3615,7 +3747,7 @@ what's actually returned by the query (Joe) - + Release 7.3.12 @@ -3640,7 +3772,7 @@ what's actually returned by the query (Joe) Changes - + Fix race condition in transaction log management @@ -3662,7 +3794,7 @@ table has been dropped - + Release 7.3.11 @@ -3749,7 +3881,7 @@ the variable is of pass-by-reference type It is strongly recommended that all installations repair this error, either by initdb or by following the manual repair procedure given below. The error at least allows unprivileged database users to crash - their server process, and may allow unprivileged users to gain the + their server process, and might allow unprivileged users to gain the privileges of a database superuser. @@ -3775,12 +3907,12 @@ COMMIT; template databases then any subsequently created databases will contain the same error. template1 can be fixed in the same way as any other database, but fixing template0 requires - additional steps. First, from any database issue + additional steps. First, from any database issue: UPDATE pg_database SET datallowconn = true WHERE datname = 'template0'; Next connect to template0 and perform the above repair - procedure. Finally, do + procedure. Finally, do: -- re-freeze template0: VACUUM FREEZE; @@ -3923,7 +4055,7 @@ datestyles Repair possible failure to update hint bits on disk -Under rare circumstances this oversight could lead to +Under rare circumstances this oversight could lead to could not access transaction status failures, which qualifies it as a potential-data-loss bug. @@ -4033,7 +4165,7 @@ On some platforms, building with -fstrict-aliasing causes bugs. Make pg_restore handle 64-bit off_t correctly -This bug prevented proper restoration from archive files exceeding 4Gb. +This bug prevented proper restoration from archive files exceeding 4 GB. Make contrib/dblink not assume that local and remote type OIDs match (Joe) @@ -4333,7 +4465,7 @@ operations on bytea columns (Joe) A dump/restore is not 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 + has a new major version number for this release, which might require recompilation of client code in certain cases. @@ -4361,8 +4493,8 @@ operations on bytea columns (Joe) - - + + Release 7.3 @@ -4569,7 +4701,7 @@ operations on bytea columns (Joe) COPY no longer considers missing trailing columns to be null. All columns need to be specified. - (However, one may achieve a similar effect by specifying a + (However, one can achieve a similar effect by specifying a column list in the COPY command.) @@ -5125,7 +5257,7 @@ datestyles Repair possible failure to update hint bits on disk -Under rare circumstances this oversight could lead to +Under rare circumstances this oversight could lead to could not access transaction status failures, which qualifies it as a potential-data-loss bug. @@ -5266,8 +5398,8 @@ since PostgreSQL 7.1. - - + + Release 7.2.2 @@ -5309,8 +5441,8 @@ since PostgreSQL 7.1. - - + + Release 7.2.1 @@ -5470,7 +5602,7 @@ since PostgreSQL 7.1. The semantics of the VACUUM command have - changed in this release. You may wish to update your + changed in this release. You might wish to update your maintenance procedures accordingly. @@ -5510,7 +5642,7 @@ since PostgreSQL 7.1. The timestamp(), time(), and interval() functions are no longer - available. Instead of timestamp(), use + available. Instead of timestamp(), use timestamp 'string' or CAST. @@ -5935,7 +6067,7 @@ since PostgreSQL 7.1. -Remove unused WAL segements of large transactions (Tom) +Remove unused WAL segments of large transactions (Tom) Multiaction rule fix (Tom) PL/pgSQL memory allocation fix (Jan) VACUUM buffer fix (Tom) @@ -5982,7 +6114,7 @@ Fix PL/pgSQL SELECTs when returning no rows Fix for psql backslash core dump Referential integrity privilege fix Optimizer fixes -pg_dump cleanups +pg_dump cleanups @@ -6065,7 +6197,7 @@ 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. +disable disk flushes, you might want to consider discontinuing its use. @@ -6106,7 +6238,7 @@ outer join syntax. 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 +functions, but you might want to rewrite them in the future to use the new function manager call interface. @@ -6121,7 +6253,7 @@ function manager call interface. A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables -now work properly. Inherited tables are now accessed by default. +now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. @@ -6151,7 +6283,7 @@ Kerberos V fixes (David Wragg) Fix for INSERT INTO...SELECT where targetlist has subqueries (Tom) Prompt username/password on standard error (Bruce) Large objects inv_read/inv_write fixes (Tom) -Fixes for to_char(), to_date(), to_ascii(), and to_timestamp() (Karel, +Fixes for to_char(), to_date(), to_ascii(), and to_timestamp() (Karel, Daniel Baldoni) Prevent query expressions from leaking memory (Tom) Allow UPDATE of arrays elements (Tom) @@ -6167,7 +6299,7 @@ Disallow DROP RULE, CREATE INDEX, TRUNCATE on views (Mark Hollomon) Allow PL/pgSQL accept non-ASCII identifiers (Tatsuo) Allow views to proper handle GROUP BY, aggregates, DISTINCT (Tom) Fix rare failure with TRUNCATE command (Tom) -Allow UNION/INTERSECT/EXCEPT to be used with ALL, subqueries, views, +Allow UNION/INTERSECT/EXCEPT to be used with ALL, subqueries, views, DISTINCT, ORDER BY, SELECT...INTO (Tom) Fix parser failures during aborted transactions (Tom) Allow temporary relations to properly clean up indexes (Bruce) @@ -6203,14 +6335,14 @@ Improve ps status display for more platforms (Peter E, Marc) Improve CREATE FUNCTION failure message (Ross) JDBC improvements (Peter, Travis Bauer, Christopher Cain, William Webber, Gunnar) -Grand Unified Configuration scheme/GUC. Many options can now be set in +Grand Unified Configuration scheme/GUC. Many options can now be set in data/postgresql.conf, postmaster/postgres flags, or SET commands (Peter E) Improved handling of file descriptor cache (Tom) New warning code about auto-created table alias entries (Bruce) Overhaul initdb process (Tom, Peter E) Overhaul of inherited tables; inherited tables now accessed by default; new ONLY key word prevents it (Chris Bitmead, Tom) -ODBC cleanups/improvements (Nick Gorham, Stephan Szabo, Zoltan Kovacs, +ODBC cleanups/improvements (Nick Gorham, Stephan Szabo, Zoltan Kovacs, Michael Fork) Allow renaming of temp tables (Tom) Overhaul memory manager contexts (Tom) @@ -6281,7 +6413,7 @@ New CIDR abbrev() function (Tom) Performance ----------- -Write-Ahead Log (WAL) to provide crash recovery with less performance +Write-Ahead Log (WAL) to provide crash recovery with less performance overhead (Vadim) ANALYZE stage of VACUUM no longer exclusively locks table (Bruce) Reduced file seeks (Denis Perchine) @@ -6372,7 +6504,7 @@ Fix for psql \l+ when multibyte enabled (Tatsuo) Allow PL/pgSQL to accept non ascii identifiers (Tatsuo) Make vacuum always flush buffers (Tom) Fix to allow cancel while waiting for a lock (Hiroshi) -Fix for memory aloocation problem in user authentication code (Tom) +Fix for memory allocation problem in user authentication code (Tom) Remove bogus use of int4out() (Tom) Fixes for multiple subqueries in COALESCE or BETWEEN (Tom) Fix for failure of triggers on heap open in certain cases (Jeroen van @@ -6503,7 +6635,7 @@ ecpg changes (Michael) 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 @@ -6579,7 +6711,7 @@ ecpg changes (Michael) 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 + For those upgrading from 6.5.*, you can instead use pg_upgrade to upgrade to this release; however, a full dump/reload installation is always the most robust method for upgrades. @@ -6600,7 +6732,7 @@ ecpg changes (Michael) ease the transition by allowing PostgreSQL to recognize the deprecated type names and translate them to the new type - names, this mechanism may not be completely transparent to + names, this mechanism cannot be completely transparent to your existing application. @@ -6612,8 +6744,8 @@ ecpg changes (Michael) decreased query times as the optimizer makes a better choice for the preferred plan. However, in a small number of cases, usually involving pathological distributions of data, your - query times may go up. If you are dealing with large amounts - of data, you may want to check your queries to verify + query times might go up. If you are dealing with large amounts + of data, you might want to check your queries to verify performance. @@ -6756,8 +6888,8 @@ Force permissions on PGDATA directory to be secure, even if it exists (Tom) Added psql LASTOID variable to return last inserted oid (Peter E) Allow concurrent vacuum and remove pg_vlock vacuum lock file (Tom) Add privilege check for vacuum (Peter E) -New libpq functions to allow asynchronous connections: PQconnectStart(), - PQconnectPoll(), PQresetStart(), PQresetPoll(), PQsetenvStart(), +New libpq functions to allow asynchronous connections: PQconnectStart(), + PQconnectPoll(), PQresetStart(), PQresetPoll(), PQsetenvStart(), PQsetenvPoll(), PQsetenvAbort (Ewan Mellor) New libpq PQsetenv() function (Ewan Mellor) create/alter user extension (Peter E) @@ -6775,7 +6907,7 @@ Add CREATE/ALTER/DROP GROUP (Peter E) All administration scripts now support --long options (Peter E, Karel) Vacuumdb script now supports --all option (Peter E) ecpg new portable FETCH syntax -Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF +Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF and EXEC SQL ENDIF directives Add pg_ctl script to control backend start-up (Tatsuo) Add postmaster.opts.default file to store start-up flags (Tatsuo) @@ -6850,8 +6982,8 @@ Cleanups for int8 inputs, range checking, and type conversion (Tom) Fix for SELECT timespan('21:11:26'::time) (Tom) netmask('x.x.x.x/0') is 255.255.255.255 instead of 0.0.0.0 (Oleg Sharoiko) Add btree index on NUMERIC (Jan) -Perl fix for large objects containing NUL characters (Douglas Thomson) -ODBC fix for for large objects (free) +Perl fix for large objects containing NUL characters (Douglas Thomson) +ODBC fix for large objects (free) Fix indexing of cidr data type Fix for Ethernet MAC addresses (macaddr type) comparisons Fix for date/time types when overflows happened in computations (Tom) @@ -7091,13 +7223,13 @@ Fix for EXPLAIN on inheritance(Tom) Patch to allow vacuum on multisegment tables(Hiroshi) R-Tree optimizer selectivity fix(Tom) ACL file descriptor leak fix(Atsushi Ogawa) -New expresssion subtree code(Tom) +New expression subtree code(Tom) Avoid disk writes for read-only transactions(Vadim) Fix for removal of temp tables if last transaction was aborted(Bruce) Fix to prevent too large row from being created(Bruce) plpgsql fixes Allow port numbers 32k - 64k(Bruce) -Add ^ precidence(Bruce) +Add ^ precedence(Bruce) Rename sort files called pg_temp to pg_sorttemp(Bruce) Fix for microseconds in time values(Tom) Tutorial source cleanup @@ -7259,10 +7391,10 @@ Add Win1250 (Czech) support (Pavel Behal) The Administrator's Guide has a new chapter on troubleshooting from Tom Lane. And the Programmer's Guide has a - description of query processing, also from Stefan, and details + description of query processing, also from Stefan, and details on obtaining the PostgreSQL source tree via anonymous CVS and - CVSup. + CVSup. @@ -7284,7 +7416,7 @@ Add Win1250 (Czech) support (Pavel Behal) The new Multiversion Concurrency Control (MVCC) features can give somewhat different behaviors in multiuser - environments. Read and understand the following section + environments. Read and understand the following section to ensure that your existing applications will give you the behavior you need. @@ -7464,7 +7596,7 @@ JDBC fixes/features, see src/interfaces/jdbc/CHANGELOG(Peter) Make % operator have precedence like /(Bruce) Add new postgres -O option to allow system table structure changes(Bruce) Update contrib/pginterface/findoidjoins script(Tom) -Major speedup in vacuum of deleted rows with indexes(Vadim) +Major speedup in vacuum of deleted rows with indexes(Vadim) Allow non-SQL functions to run different versions based on arguments(Tom) Add -E option that shows actual queries sent by \dt and friends(Masaaki Sakaida) Add version number in start-up banners for psql(Masaaki Sakaida) @@ -7479,7 +7611,7 @@ New pg_options: pretty_plan, pretty_parse, pretty_rewritten(Jan) Better optimization statistics for system table access(Tom) Better handling of non-default block sizes(Massimo) Improve GEQO optimizer memory consumption(Tom) -UNION now suppports ORDER BY of columns not in target list(Jan) +UNION now supports ORDER BY of columns not in target list(Jan) Major libpq++ improvements(Vince Vielhaber) pg_dump now uses -z(ACL's) as default(Bruce) backend cache, memory speedups(Tom) @@ -7628,7 +7760,7 @@ Here is a brief, incomplete summary: -Views and rules are now functional thanks to extensive new code in the +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. @@ -7667,7 +7799,7 @@ which covers this topic. -Three new data types have been added. +Three new data types have been added. Two types, inet and cidr, support various forms of IP network, subnet, and machine addressing. There is now an 8-byte integer type available on some platforms. See the chapter on data types @@ -7699,7 +7831,7 @@ been. Migration to version 6.4 -A dump/restore using pg_dump +A dump/restore using pg_dump or pg_dumpall is required for those wishing to migrate data from any previous release of PostgreSQL. @@ -7769,7 +7901,7 @@ Readline cleanups(Tom) Allow psql \f \ to make spaces as delimiter(Bruce) Pass pg_attribute.atttypmod to the frontend for column field lengths(Tom,Bruce) Msql compatibility library in /contrib(Aldrin) -Remove the requirement that ORDER/GROUP BY clause identifiers be +Remove the requirement that ORDER/GROUP BY clause identifiers be included in the target list(David) Convert columns to match columns in UNION clauses(Thomas) Remove fork()/exec() and only do fork()(Bruce) @@ -7777,7 +7909,7 @@ Jdbc cleanups(Peter) Show backend status on ps command line(only works on some platforms)(Bruce) Pg_hba.conf now has a sameuser option in the database field Make lo_unlink take oid param, not int4 -New DISABLE_COMPLEX_MACRO for compilers that can't handle our macros(Bruce) +New DISABLE_COMPLEX_MACRO for compilers that cannot handle our macros(Bruce) Libpgtcl now handles NOTIFY as a Tcl event, need not send dummy queries(Tom) libpgtcl cleanups(Tom) Add -error option to libpgtcl's pg_result command(Tom) @@ -7853,7 +7985,7 @@ New UNLISTEN command(Massimo) psql and libpq now compile under Windows using win32.mak(Magnus) Lo_read no longer stores trailing NULL(Bruce) Identifiers are now truncated to 31 characters internally(Bruce) -Createuser options now availble on the command line +Createuser options now available on the command line Code for 64-bit integer supported added, configure tested, int8 type(Thomas) Prevent file descriptor leaf from failed COPY(Bruce) New pg_upgrade command(Bruce) @@ -7864,7 +7996,7 @@ New DECLARE and FETCH feature(Thomas) libpq's internal structures now not exported(Tom) Allow up to 8 key indexes(Bruce) Remove ARCHIVE key word, that is no longer used(Thomas) -pg_dump -n flag to supress quotes around indentifiers +pg_dump -n flag to suppress quotes around indentifiers disable system columns for views(Jan) new INET and CIDR types for network addresses(TomH, Paul) no more double quotes in psql output @@ -7893,7 +8025,7 @@ NS32K platform fixes(Phil Nelson, John Buller) SCO 7/UnixWare 2.x fixes(Billy,others) Sparc/Solaris 2.5 fixes(Ryan) Pgbuiltin.3 is obsolete, move to doc files(Thomas) -Even more documention(Thomas) +Even more documentation(Thomas) Nextstep support(Jacek) Aix support(David) pginterface manual page(Bruce) @@ -7940,7 +8072,7 @@ 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 +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. @@ -8017,7 +8149,7 @@ Improvements to the configuration autodetection for installation. -A dump/restore is NOT required for those running 6.3. A +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. @@ -8094,7 +8226,7 @@ Better identify tcl and tk libs and includes(Bruce) Socket interface for client/server connection. This is the default now - so you may need to start postmaster with the + so you might need to start postmaster with the flag. @@ -8130,9 +8262,9 @@ Better identify tcl and tk libs and includes(Bruce) mention that without subselects, SQL is a very limited language. Subselects are a major feature, and you should review your code for places where subselects provide a better solution for your queries. I - think you will find that there are more uses for subselects than you may + think you will find that there are more uses for subselects than you might 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 + functional ones too. The only thing you cannot do with subselects is to use them in the target list. @@ -8145,7 +8277,7 @@ Better identify tcl and tk libs and includes(Bruce) 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 also - have this access penalty, but it no longer does. This may suggest that + have this access penalty, but it no longer does. This might suggest 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. @@ -8163,7 +8295,7 @@ Better identify tcl and tk libs and includes(Bruce) User-created tables now no longer have SELECT privilege to PUBLIC by default. This was done because the ANSI standard requires it. You can - of course GRANT any privileges you want after the table is created. + of course GRANT any privileges you want after the table is created. System tables continue to be SELECT-able by PUBLIC. @@ -8195,7 +8327,7 @@ Better identify tcl and tk libs and includes(Bruce) Migration to version 6.3 - A dump/restore using pg_dump + A dump/restore using pg_dump or pg_dumpall is required for those wishing to migrate data from any previous release of PostgreSQL. @@ -8241,7 +8373,7 @@ Check boolean input literals for 'true','false','yes','no','1','0' and throw elog(ERROR) if unrecognized(Thomas) Major large objects fix Fix for GROUP BY showing duplicates(Vadim) -Fix for index scans in MergeJion(Vadim) +Fix for index scans in MergeJoin(Vadim) Enhancements ------------ @@ -8249,7 +8381,7 @@ Subselects with EXISTS, IN, ALL, ANY key words (Vadim, Bruce, Thomas) New User Manual(Thomas, others) Speedup by inlining some frequently-called functions Real deadlock detection, no more timeouts(Bruce) -Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, +Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, CURRENT_USER(Thomas) Modify constraint syntax to be SQL92-compliant(Thomas) Implement SQL92 PRIMARY KEY and UNIQUE clauses using indexes(Thomas) @@ -8329,7 +8461,7 @@ Reduce system column overhead(Vadmin) Remove pg_time table(Vadim) Add pg_type attribute to identify types that need length (bpchar, varchar) Add report of offending line when COPY command fails -Allow VIEW privileges to be set separately from the underlying tables. +Allow VIEW privileges to be set separately from the underlying tables. For security, use GRANT/REVOKE on views as appropriate(Jan) Tables now have no default GRANT SELECT TO PUBLIC. You must explicitly grant such privileges. @@ -8406,8 +8538,8 @@ 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. +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. @@ -8509,14 +8641,14 @@ Catch non-functional delete attempts(Vadim) Change time function names to be more consistent(Michael Reifenberg) Check for zero divides(Michael Reifenberg) Fix very old bug which made rows changed/inserted by a command - visible to the command itself (so we had multiple update of + visible to the command itself (so we had multiple update of updated rows, etc.)(Vadim) Fix for SELECT null, 'fail' FROM pg_am (Patrick) SELECT NULL as EMPTY_FIELD now allowed(Patrick) Remove un-needed signal stuff from contrib/pginterface Fix OR (where x != 1 or x isnull didn't return rows with x NULL) (Vadim) Fix time_cmp function (Vadim) -Fix handling of functions with non-attribute first argument in +Fix handling of functions with non-attribute first argument in WHERE clauses (Vadim) Fix GROUP BY when order of entries is different from order in target list (Vadim) @@ -8530,7 +8662,7 @@ Added JDBC driver as an interface(Adrian & Peter) pg_password utility Return number of rows inserted/affected by INSERT/UPDATE/DELETE etc.(Vadim) Triggers implemented with CREATE TRIGGER (SQL3)(Vadim) -SPI (Server Programming Interface) allows execution of queries inside +SPI (Server Programming Interface) allows execution of queries inside C-functions (Vadim) NOT NULL implemented (SQL92)(Robson Paniago de Miranda) Include reserved words for string handling, outer joins, and unions(Thomas) @@ -8694,7 +8826,7 @@ optimizer which uses genetic 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! + new interpretation, which might not be correct! @@ -8763,7 +8895,7 @@ Enhancements ------------ attribute optimization statistics(Bruce) much faster new btree bulk load code(Paul) -BTREE UNIQUE added to bulk load code(Vadim) +BTREE UNIQUE added to bulk load code(Vadim) new lock debug code(Massimo) massive changes to libpg++(Leo) new GEQO optimizer speeds table multitable optimization(Martin) @@ -8866,7 +8998,7 @@ because the COPY output format was improved from the 1.02 release. Bug Fixes --------- -ALTER TABLE bug - running postgress process needs to re-read table definition +ALTER TABLE bug - running postgres process needs to re-read table definition Allow vacuum to be run on one table or entire database(Bruce) Array fixes Fix array over-runs of memory writes(Kurt) @@ -8874,7 +9006,7 @@ Fix elusive btree range/non-range bug(Dan) Fix for hash indexes on some types like time and date Fix for pg_log size explosion Fix permissions on lo_export()(Bruce) -Fix unitialized reads of memory(Kurt) +Fix uninitialized reads of memory(Kurt) Fixed ALTER TABLE ... char(3) bug(Bruce) Fixed a few small memory leaks Fixed EXPLAIN handling of options and changed full_path option name @@ -8918,7 +9050,7 @@ Change default decimal constant representation from float4 to float8(Bruce) European date format now set when postmaster is started Execute lowercase function names if not found with exact case Fixes for aggregate/GROUP processing, allow 'select sum(func(x),sum(x+y) from z' -Gist now included in the distrubution(Marc) +Gist now included in the distribution(Marc) Idend authentication of local users(Bryan) Implement BETWEEN qualifier(Bruce) Implement IN qualifier(Bruce) @@ -8947,7 +9079,7 @@ Vacuum now had VERBOSE option(Bruce) Source tree changes ------------------- All functions now have prototypes that are compared against the calls -Allow asserts to be disabled easly from Makefile.global(Bruce) +Allow asserts to be disabled easily from Makefile.global(Bruce) Change oid constants used in code to #define names Decoupled sparc and solaris defines(Kurt) Gcc -Wall compiles cleanly with warnings only from unfixable constructs @@ -8960,13 +9092,13 @@ Name change from Postgres95 to PostgreSQL New config.h file(Marc, Bryan) PG_VERSION now set to 6.0 and used by postmaster Portability additions, including Ultrix, DG/UX, AIX, and Solaris -Reduced the number of #define's, centeralized #define's +Reduced the number of #define's, centralized #define's Remove duplicate OIDS in system tables(Dan) Remove duplicate system catalog info or report mismatches(Dan) Removed many os-specific #define's Restructured object file generation/location(Bryan, Marc) Restructured port-specific file locations(Bryan, Marc) -Unused/uninialized variables corrected +Unused/uninitialized variables corrected @@ -9106,8 +9238,8 @@ New Ports