From: Neil Conway Date: Sun, 11 Sep 2005 23:40:33 +0000 (+0000) Subject: Many small improvements and copy edits to the release notes. Use "—" X-Git-Tag: REL9_0_0~9302 X-Git-Url: http://git.osdn.net/view?a=commitdiff_plain;h=f7a5f90c464cc68d70255923a8bd5046e0baba37;p=pg-rex%2Fsyncrep.git Many small improvements and copy edits to the release notes. Use "—" rather than "-" for the "dash" character. Correct SGML markup. Make references to the names of contributors more consistent. Rewrite a bit of prose, and make some other similar cleanups. --- diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index b749621895..f392cab717 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,5 +1,5 @@ @@ -40,10 +39,14 @@ pg_[A-Za-z0-9_] - This was accomplished by eliminating global locks and using a - clock sweep algorithm to find free buffers. This increases - scalability on multi-CPU systems. - + Access to the shared buffer cache was identified as a + significant scalability problem, particularly on multi-CPU + systems. In this release, the way that locking is done in the + buffer manager has been overhauled to reduce lock contention + and improve scalability. The buffer manager has also been + changed to use a clock sweep replacement + policy. + @@ -56,18 +59,19 @@ pg_[A-Za-z0-9_] In previous releases, only a single index could be used to do lookups on a table. With this feature, if a query has - WHERE tab.col1 = 4 and tab.col2 = 9, and there is no - multicolumn index on col1 and col2, but there is an index on - col1 and another on col2, it is possible to search both indexes - and combine the results in memory, then do heap fetches for only - the rows matching both the col1 and col2 - restrictions. This is very useful in environments that have a - lot of unstructured queries where it is impossible to create - indexes that match all possible access conditions. Bitmap scans - are useful even with a single index, as they reduce the amount - of random access needed; a bitmap index scan is efficient for - retrieving fairly large fractions of the complete table, whereas - plain index scans are not. + WHERE tab.col1 = 4 and tab.col2 = 9, and there is + no multicolumn index on col1 and col2, + but there is an index on col1 and another on + col2, it is possible to search both indexes and + combine the results in memory, then do heap fetches for only + the rows matching both the col1 and + col2 restrictions. This is very useful in + environments that have a lot of unstructured queries where it + is impossible to create indexes that match all possible access + conditions. Bitmap scans are useful even with a single index, + as they reduce the amount of random access needed; a bitmap + index scan is efficient for retrieving fairly large fractions + of the complete table, whereas plain index scans are not. @@ -165,7 +169,7 @@ pg_[A-Za-z0-9_] Move /contrib/pg_autovacuum into the main server - (Alvaro Herrera) + (Alvaro) @@ -217,7 +221,7 @@ pg_[A-Za-z0-9_] - Migration to version 8.1 + Migration to 8.1 A dump/restore using pg_dump is required @@ -265,16 +269,14 @@ pg_[A-Za-z0-9_] default_with_oids is now false by default (Neil) - With this option set to false, user-created tables no longer have - the usually-invisible OID column unless WITH OIDS - is specified in CREATE TABLE. Though OIDs have - existed in all releases of - PostgreSQL, their use is limited + With this option set to false, user-created tables no longer + have an OID column unless WITH OIDS is specified in + CREATE TABLE. Though OIDs have existed in all + releases of PostgreSQL, their use is limited because they are only four bytes long and the counter is shared across all installed databases. The preferred way of uniquely - identifying rows is via sequences and SERIAL, which - have been supported since PostgreSQL - 6.4. + identifying rows is via sequences and the SERIAL type, + which have been supported since PostgreSQL 6.4. @@ -297,21 +299,21 @@ pg_[A-Za-z0-9_] syntax is formed by writing an E immediately preceding the single quote that starts the string, e.g. E'hi\n'. While this release does not change the handling of backslashes in strings, it - does add new GUC variables to help users migrate applications + does add new configuration parameters to help users migrate applications for future releases: - standard_conforming_strings - does this release + standard_conforming_strings — does this release treat backslashes literally in ordinary strings? - escape_string_warning - warn about backslashes in + escape_string_warning — warn about backslashes in ordinary (non-E) strings @@ -322,18 +324,20 @@ pg_[A-Za-z0-9_] The standard_conforming_strings value is read-only. Applications can retrieve the value to know how backslashes are processed. (Presence of the parameter can also be taken as an - indication that E'' string syntax is supported.) In a - future release, standard_conforming_strings will be true, - meaning backslashes will be treated literally in non-E strings. To - prepare for this change, use E'' strings in places that - need special backslash processing, and turn on - escape_string_warning to find additional strings that need - to be converted to use E''. Also, use two single-quotes - ('') to embed a literal single-quote in a string, rather - than the PostgreSQL-supported syntax of backslash single-quote - (\'). The former is standards-conforming and does not - require the use of the E'' string syntax. You can also use - the $$ string syntax, which does not treat backslashes + indication that E'' string syntax is supported.) + In a future release, standard_conforming_strings + will be true, meaning backslashes will be treated literally in + non-E strings. To prepare for this change, use E'' + strings in places that need special backslash processing, and + turn on escape_string_warning to find additional + strings that need to be converted to use E''. + Also, use two single-quotes ('') to embed a literal + single-quote in a string, rather than the + PostgreSQL-supported syntax of + backslash single-quote (\'). The former is + standards-conforming and does not require the use of the + E'' string syntax. You can also use the + $$ string syntax, which does not treat backslashes specially. @@ -353,8 +357,8 @@ pg_[A-Za-z0-9_] - In psql, treat unquoted \{digit}+ sequences as octal - (Bruce) + In psql, treat unquoted + \{digit}+ sequences as octal (Bruce) In previous releases, \{digit}+ sequences were @@ -389,8 +393,9 @@ pg_[A-Za-z0-9_] Additional Changes - Below you will find a detailed account of the additional changes - between release 8.1 and the previous major release. + Below you will find a detailed account of the additional changes + between PostgreSQL 8.1 and the + previous major release. @@ -399,7 +404,7 @@ pg_[A-Za-z0-9_] - Improve rtree index capabilities and performance (Neil) + Improve GiST and rtree index performance (Neil) @@ -435,8 +440,7 @@ pg_[A-Za-z0-9_] Allow non-consecutive index columns to be used in a multi-column - index - (Tom) + index (Tom) For example, this allows an index on columns a,b,c to be used in @@ -465,9 +469,8 @@ pg_[A-Za-z0-9_] - Add GUC full_page_writes to control writing full - pages to WAL - (Bruce) + Add configuration parameter full_page_writes to + control writing full pages to WAL (Bruce) To prevent partial disk writes from corrupting the database, @@ -481,8 +484,9 @@ pg_[A-Za-z0-9_] - Add constraint_exclusion to restrict child table lookups based - on table constraints (Simon) + Add constraint_exclusion configuration + parameter to restrict child table lookups based on table + constraints (Simon) This allows for a type of table partitioning. If child tables @@ -496,7 +500,8 @@ pg_[A-Za-z0-9_] Use O_DIRECT if available when using - O_SYNC for wal_sync_method (Itagaki Takahiro) + O_SYNC for wal_sync_method + (Itagaki Takahiro) O_DIRECT causes disk writes to bypass the kernel @@ -516,12 +521,11 @@ pg_[A-Za-z0-9_] - - + Server Changes - + Prevent problems due to transaction ID (XID) wraparound (Tom) @@ -551,9 +555,9 @@ pg_[A-Za-z0-9_] - Add temp_buffers GUC variable to allow users to - determine the size of the local buffer area for temporary table - access (Tom) + Add temp_buffers configuration parameter to allow + users to determine the size of the local buffer area for + temporary table access (Tom) @@ -586,8 +590,9 @@ pg_[A-Za-z0-9_] - Add GUC krb_server_hostname so the server hostname - can be specified as part of service principal (Todd Kover) + Add configuration parameter krb_server_hostname so + that the server hostname can be specified as part of service + principal (Todd Kover) If not set, any service principal matching an entry in the @@ -609,7 +614,7 @@ pg_[A-Za-z0-9_] Add WAL logging for GIST indexes (Teodor, Oleg) - GIST indexes are now safe for crash and point-in-time recovery + GIST indexes are now safe for crash and point-in-time recovery. @@ -626,8 +631,8 @@ pg_[A-Za-z0-9_] - Add GUC variables to control TCP/IP keep-alive times for idle, - interval, and count (Oliver Jowett) + Add configuration parameters to control TCP/IP keep-alive + times for idle, interval, and count (Oliver Jowett) @@ -650,7 +655,7 @@ pg_[A-Za-z0-9_] - Allow more than two gigabyes of shared memory and per-backend + Allow more than two gigabytes of shared memory and per-backend work memory on 64-bit machines (Koichi Suzuki) @@ -665,7 +670,7 @@ pg_[A-Za-z0-9_] - Add temporary views (Koju Iijima) + Add temporary views (Koju Iijima, Neil) @@ -683,12 +688,12 @@ pg_[A-Za-z0-9_] Add USING clause to allow additional tables to be - specified to DELETE (Euler Taveira de Oliveira) + specified to DELETE (Euler Taveira de Oliveira, Neil) In prior releases, there was no clear method for specifying additional tables to be used for joins in a DELETE - statement. UPDATE already has a FROM + statement. UPDATE already has a FROM clause for this purpose. @@ -723,14 +728,13 @@ pg_[A-Za-z0-9_] UPDATE/SHARE (Hans-Juergen Schoenig) - While SET statement_timeout allows a query - taking over a certain amount of time to be cancelled, the - NOWAIT option allows a query to be canceled as soon as a - SELECT ... FOR UPDATE/SHARE command cannot immediately - acquire a row lock. + While the statement_timeout configuration + parameter allows a query taking more than a certain amount of + time to be cancelled, the NOWAIT option allows a + query to be canceled as soon as a SELECT ... FOR + UPDATE/SHARE command cannot immediately acquire a row lock. - @@ -781,8 +785,8 @@ pg_[A-Za-z0-9_] - Add ALTER TABLE ENABLE/DISABLE TRIGGER to disable triggers - (Satoshi Nagayasu) + Add ALTER TABLE ENABLE/DISABLE TRIGGER to + disable triggers (Satoshi Nagayasu) @@ -812,7 +816,7 @@ pg_[A-Za-z0-9_] Properly process carriage returns and line feeds in - COPY CSV mode (Andrew Dunstan) + COPY CSV mode (Andrew) In release 8.0, carriage returns and line feeds in CSV @@ -876,28 +880,29 @@ pg_[A-Za-z0-9_] - Make initdb create a new standard database called - postgres, and convert utilities to use - postgres rather than template1 for + Make initdb create a new standard + database called postgres, and convert utilities to + use postgres rather than template1 for standard lookups (Dave) - In prior releases, template1 was used both as a default - connection for utilities like createuser, and as a template for + In prior releases, template1 was used both as a + default connection for utilities like + createuser, and as a template for new databases. This caused CREATE DATABASE to sometimes fail, because a new database cannot be created if anyone else is in the template database. With this change, the - default connection database is now postgres, meaning - it is much less likely someone will be using + default connection database is now postgres, + meaning it is much less likely someone will be using template1 during CREATE DATABASE. - Create new reindexdb command-line utility by moving - /contrib/reindexdb into the server (Euler Taveira - de Oliveira) + Create new reindexdb command-line + utility by moving /contrib/reindexdb into the + server (Euler Taveira de Oliveira) @@ -1023,8 +1028,8 @@ pg_[A-Za-z0-9_] - Add GREATEST() and LEAST() functions - (Pavel Stehule) + Add GREATEST() and LEAST() variadic + functions (Pavel Stehule) These functions take a variable number of arguments and return @@ -1180,7 +1185,6 @@ pg_[A-Za-z0-9_] - Add pg_rotate_logfile() to force rotation of the @@ -1236,6 +1240,7 @@ pg_[A-Za-z0-9_] + The original names still work. @@ -1262,8 +1267,7 @@ pg_[A-Za-z0-9_] Allow direct conversion between EUC_JP and - SJIS to improve performance (Atsushi - Ogawa) + SJIS to improve performance (Atsushi Ogawa) @@ -1343,8 +1347,9 @@ pg_[A-Za-z0-9_] Reduce memory usage of PL/PgSQL functions (Neil) - Each function now has its own memory context that can be freed - when the function exits. + The parsetree of each function is now stored in a separate + memory context. This allows the memory to be easily reclaimed + when it is no longer needed. @@ -1354,8 +1359,8 @@ pg_[A-Za-z0-9_] rather than at runtime (Neil) - Previously, syntax errors were reported only when the function - was executed. + Previously, most syntax errors were reported only when the + function was executed. @@ -1381,7 +1386,7 @@ pg_[A-Za-z0-9_] Add support for an optional INTO clause to - PL/PgSQL's EXECUTE command (Pavel Stehule) + PL/PgSQL's EXECUTE command (Pavel Stehule, Neil) @@ -1395,7 +1400,7 @@ pg_[A-Za-z0-9_] Define SQLSTATE and SQLERRM to return the SQLSTATE and error message of the current - exception (Pavel Stehule) + exception (Pavel Stehule, Neil) These variables are only accessible inside exception blocks. @@ -1405,13 +1410,13 @@ pg_[A-Za-z0-9_] Allow the parameters to the RAISE statement to be - expressions (Pavel Stehule) + expressions (Pavel Stehule, Neil) - Add a loop CONTINUE statement (Pavel Stehule) + Add a loop CONTINUE statement (Pavel Stehule, Neil) @@ -1442,7 +1447,7 @@ pg_[A-Za-z0-9_] - Allow one-row-at-a-time retrieval of query results (Abhijit) + Allow one-row-at-a-time retrieval of query results (Abhijit Menon-Sen) This allows functions to use spi_query() and @@ -1488,22 +1493,22 @@ pg_[A-Za-z0-9_] - Allow strict mode to be enabled (Andrew) + Allow Perl's strict mode to be enabled (Andrew) - - + + <application>psql</> Changes - Add psql \set ON_ERROR_ROLLBACK to allow statements - in a transaction to error without affecting the rest of the + Add \set ON_ERROR_ROLLBACK to allow statements in + a transaction to error without affecting the rest of the transaction (Greg Sabino Mullane) @@ -1514,8 +1519,8 @@ pg_[A-Za-z0-9_] - Add support for \x hex strings in psql variables - (Bruce) + Add support for \x hex strings in + psql variables (Bruce) Octal escapes were already supported. @@ -1524,14 +1529,14 @@ pg_[A-Za-z0-9_] - Add psql support for troff -ms output format (Roger + Add support for troff -ms output format (Roger Leigh) - Allow psql's history file location to be controlled by + Allow the history file location to be controlled by HISTFILE (Andreas Seltenreich) @@ -1541,14 +1546,15 @@ pg_[A-Za-z0-9_] - Prevent psql \x (expanded mode) from affecting + Prevent \x (expanded mode) from affecting backslash-command displays (Neil) - Add This option was added because some operating systems do not have @@ -1558,15 +1564,16 @@ pg_[A-Za-z0-9_] - Make psql \d show tablespaces of indexes (Qingqing + Make \d show the tablespaces of indexes (Qingqing Zhou) - Allow psql help (\h) to make a best guess on the - proper help information (Greg Sabino Mullane) + Allow psql help (\h) to + make a best guess on the proper help information (Greg Sabino + Mullane) This allows the user to just add \h to the front of @@ -1578,7 +1585,7 @@ pg_[A-Za-z0-9_] - Add psql \pset numericlocale to allow numbers to be + Add \pset numericlocale to allow numbers to be output in a locale-aware format (Eugen Nedelcu) @@ -1609,8 +1616,7 @@ pg_[A-Za-z0-9_] Allow pg_dump to dump a consistent snapshot of - large objects - (Tom) + large objects (Tom) @@ -1644,13 +1650,13 @@ pg_[A-Za-z0-9_] - libpq Changes + <application>libpq</application> Changes Add a PGPASSFILE environment variable to specify the - password file's filename (Andrew Dunstan) + password file's filename (Andrew) @@ -1673,8 +1679,7 @@ pg_[A-Za-z0-9_] Add spinlock support for the Itanium processor using Intel - compiler (Vikram - Kalsi) + compiler (Vikram Kalsi) @@ -1699,8 +1704,8 @@ pg_[A-Za-z0-9_] - Add support for wal_fsync_writethrough for Darwin (Chris - Campbell) + Add support for fsync_writethrough on + Darwin (Chris Campbell) @@ -1713,8 +1718,7 @@ pg_[A-Za-z0-9_] - Allow pg_config to be compiled using MSVC (Andrew - Dunstan) + Allow pg_config to be compiled using MSVC (Andrew) This is required to build DBD::Pg using MSVC. @@ -1727,7 +1731,7 @@ pg_[A-Za-z0-9_] Kerberos 4 had security vulnerabilities and is no longer being - maintained by the authors. + maintained. @@ -1755,7 +1759,8 @@ pg_[A-Za-z0-9_] - Allow libpq to be built thread-safe on Windows (Dave Page) + Allow libpq to be built thread-safe + on Windows (Dave Page) @@ -1829,7 +1834,7 @@ pg_[A-Za-z0-9_] - implementation of OpenPGP symmetric-key and public-key encryption + Implementation of OpenPGP symmetric-key and public-key encryption Both RSA and Elgamal public-key algorithms are supported. @@ -1850,7 +1855,7 @@ pg_[A-Za-z0-9_] - Take build parameters (OpenSSL, zlib) from ./configure result + Take build parameters (OpenSSL, zlib) from configure result No need to edit the Makefile anymore.