From a5645972affed43ecf3cc640baeb48de5327e75d Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 15 Jan 2005 21:11:46 +0000 Subject: [PATCH] Some minor editing work on the release notes. --- doc/src/sgml/release.sgml | 266 +++++++++++++++++++------------------- 1 file changed, 133 insertions(+), 133 deletions(-) diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 7d191056a7..deba319525 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,5 +1,5 @@ @@ -28,8 +28,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp This is the first PostgreSQL release - to natively run on Microsoft Windows as a - server. It can run as a Windows service. This + to run natively on Microsoft Windows as + a server. It can run as a Windows service. This release supports NT-based Windows releases like Windows 2000, Windows XP, and Windows 2003. Older releases like @@ -38,7 +38,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp systems do not have the infrastructure to support PostgreSQL. A separate installer project has been created to ease installation on - Windows: Windows — see http://pgfoundry.org/projects/pginstaller. @@ -47,7 +47,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp Although tested throughout our release cycle, the Windows port does not have the benefit of years of use in production environments that PostgreSQL has on - Unix platforms and therefore should be treated with the same + Unix platforms. Therefore it should be treated with the same level of caution as you would a new product. @@ -85,8 +85,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Though PostgreSQL is very reliable, - in previous releases there was no way to recover from disk + In previous releases there was no way to recover from disk drive failure except to restore from a previous backup or use a standby replication server. Point-in-time recovery allows continuous backup of the server. You can recover either to @@ -102,8 +101,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Tablespaces allow administrators to select the file systems - used for storage of tables, indexes, and entire databases. + Tablespaces allow administrators to select different file systems + for storage of individual tables, indexes, and databases. This improves performance and control over disk space usage. Prior releases used initlocation and manual symlink management for such tasks. @@ -186,6 +185,37 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp + + + In + + + + + Functions declared + + + + + Non-deferred + + Server configuration parameters virtual_host and @@ -210,14 +240,13 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp Server configuration parameters log_pid, log_timestamp, and log_source_port have been - removed now that a more flexible log_line_prefix has been - added. + replaced with a more general parameter log_line_prefix. - Server configuration parameter syslog has been removed and + Server configuration parameter syslog has been replaced with a more logical log_destination variable to control the log output destination. @@ -227,8 +256,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp Server configuration parameter log_statement has been changed so it can selectively log just database modification or - data definition statements. Server configuration parameter - log_duration now prints only when log_statement + data definition statements. Server configuration parameter + log_duration now prints only when log_statement prints the query. @@ -267,24 +296,27 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Overflow in integer arithmetic operations is now detected and - reported as an error. + Syntax checking of array input values has been tightened up + considerably. Junk that was previously allowed in odd places with + odd results now causes an error. Empty-string element values + must now be written as "", rather than writing nothing. + Also changed behavior with respect to whitespace surrounding + array elements: trailing whitespace is now ignored, for symmetry + with leading whitespace (which has always been ignored). - The arithmetic operators associated with the single-byte - "char" data type have been removed. + Overflow in integer arithmetic operations is now detected and + reported as an error. - The server now warns of empty strings passed to - oid/float4/float8 data - types. In the next major release, doing this will generate an - error. + The arithmetic operators associated with the single-byte + "char" data type have been removed. @@ -298,6 +330,23 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp + + + CIDR values now must have their non-masked bits be zero. + For example, we no longer allow + 204.248.199.1/31 as a CIDR value. Such + values should never have been accepted by + PostgreSQL and will now be rejected. + + + + + + EXECUTE now returns a completion tag that + matches the executed statement. + + + psql's \copy command now reads or @@ -309,9 +358,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - The JDBC client interface has been removed from the core + + The JDBC client interface has been removed from the core distribution, and is now hosted at http://jdbc.postgresql.org. + + + + + The Tcl client interface has also been removed. There are several Tcl interfaces now hosted at http://gborg.postgresql.org. @@ -324,18 +379,12 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp one supplied by the operating system. This will provide consistent behavior across all platforms. In most cases, there should be little noticeable difference in time zone behavior, except that - the time zone names used by SET/SHOW TimeZone may + the time zone names used by SET/SHOW + TimeZone may be different from what your platform provides. - - - EXECUTE now returns a completion tag that - matches the executed statement. - - - Configure's threading option no longer requires @@ -351,60 +400,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - - - Syntax checking of array input values has been tightened up - considerably. Junk that was previously allowed in odd places with - odd results now causes an error. Empty-string element values - must now be written as "", rather than writing nothing. - Also changed behavior with respect to whitespace surrounding - array elements: trailing whitespace is now ignored, for symmetry - with leading whitespace (which has always been ignored). - - - - - - In - - - - - Functions declared - - - - - Non-deferred - - - - - CIDR values now must have their non-masked bits be zero. - For example, we no longer allow - 204.248.199.1/31 as a CIDR value. Such - values should never have been accepted by - PostgreSQL and will now be rejected. - - - - @@ -424,10 +419,20 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp The 8.1 release will remove the function - to_char(interval). + to_char(interval, text). + + + The server now warns of empty strings passed to + oid/float4/float8 data + types, but continues to interpret them as zeroes as before. + In the next major release, empty strings will be considered + invalid input for these data types. + + + By default, tables in PostgreSQL 8.0 @@ -435,7 +440,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp this will not be the case: to create a table that contains OIDs, the - The optimizer now uses a table's current actual size on disk as its - estimate of the number of blocks in the table, and it makes an estimate - of the number of rows in the table based on the current size on disk. - Formerly, the - pg_class.relpages - and - pg_class.reltuples - fields were used as-is, but these values might be quite out-of-date, - leading to poor choices of plans. They are now treated only as an - indication of the table's density (rows per page). + Formerly the planner estimated table sizes using the values seen + by the last VACUUM or ANALYZE, + both as to physical table size (number of pages) and number of rows. + Now, the current physical table size is obtained from the kernel, + and the number of rows is estimated by multiplying the table size + by the row density (rows per page) seen by the last + VACUUM or ANALYZE. This should + produce more reliable estimates in cases where the table size has + changed significantly since the last housekeeping command. @@ -612,7 +616,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Allow collection of ANALYZE statistics for + ANALYZE now collects statistics for expression indexes (Tom) @@ -646,23 +650,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - - - Improve optimizer rowcount estimates (Tom) - - - Formerly the planner estimated table sizes using the values seen - by the last VACUUM or ANALYZE, - both as to physical table size (number of pages) and number of rows. - Now, the physical table size is obtained directly from the kernel, - and the number of rows is estimated by multiplying the table size - by the row density (rows per page) seen by the last - VACUUM or ANALYZE. This should - produce more reliable estimates in cases where the table size has - changed significantly since the last housekeeping command. - - - @@ -696,7 +683,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Add new read-only server configuration parameters to query server + Add new read-only server configuration parameters to show server compile-time settings: block_size, integer_datetimes, max_function_args, max_identifier_length, max_index_keys (Joe) @@ -769,6 +756,11 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp parameters with a unified listen_addresses parameter (Andrew, Tom) + + virtual_host could only specify a single IP address to + listen on. listen_addresses allows multiple addresses + to be specified. + @@ -839,7 +831,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp parameters to be used in the query. In this release, planning of unnamed prepared statements is delayed until the first execution, and the actual parameter values of that execution are used as - optimization hints. + optimization hints. This allows use of out-of-line parameter passing + without incurring a performance penalty. @@ -1052,9 +1045,11 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp control whether tables are created with OIDs by default (Neil) - This allows administrators to default all CREATE - TABLE commands to create tables without OID - columns. + This allows administrators to control whether CREATE + TABLE commands create tables with or without OID + columns by default. (Note: the current factory default setting for + default_with_oids is TRUE, but the default + will become FALSE in future releases.) @@ -1156,7 +1151,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Constraint/Index/SERIAL names are now table_column_type + Constraint/Index/SERIAL names are now + table_column_type with numbers appended to guarantee uniqueness within the schema (Tom) @@ -1300,11 +1296,11 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp PostgreSQL uses the user name as salt - when encrypting passwords via MD5. When a user name is changed, - their salt no longer matches the stored MD5 password, so the + when encrypting passwords via MD5. When a user's name is changed, + the salt will no longer match the stored MD5 password, so the stored password becomes useless. In this release a notice is generated and the password is cleared. A new password must then - be assigned. + be assigned if the user is to be able to log in with a password. @@ -1389,7 +1385,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp Formerly, the parser would select these operators in many situations where an unable to select an operator error would be more appropriate, such as null * null. If you actually want - to do arithmetic on a "char" column, you can cast it to integer. + to do arithmetic on a "char" column, you can cast it to + integer explicitly. @@ -1479,7 +1476,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Warn of empty string being passed to + Warn about empty string being passed to OID/float4/float8 data types (Neil) @@ -1489,9 +1486,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Allow - int2/int4/int8/float4/float8 - input routines to have leading or trailing whitespace + Allow leading or trailing whitespace in + int2/int4/int8/float4/float8 + input routines (Neil) @@ -1656,7 +1653,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp effects of actions taken after the calling query starts, whether in their own transaction or other transactions. Such a function must be read-only, too, meaning that it cannot use any SQL commands other than - SELECT. + SELECT. There is a considerable performance gain from + declaring a function STABLE or IMMUTABLE + rather than VOLATILE. @@ -1967,7 +1966,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Make libpq @@ -2326,7 +2325,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp - Removed contrib/pg_logger + Removed contrib/pg_logger: obsoleted by integrated logging + subprocess -- 2.40.0