From 53a04e005b6daa0f5f78005a377af590e1352713 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 23 Aug 2005 12:46:35 +0000 Subject: [PATCH] Release note updates. --- doc/src/sgml/release.sgml | 232 ++++++++++++++++++-------------------- 1 file changed, 109 insertions(+), 123 deletions(-) diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index d27d659045..22c2bd52b1 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,5 +1,5 @@ @@ -23,11 +23,11 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian - + Improve concurrent access to the shared buffer cache (Tom) - + - + This was accomplished by eliminating global locks and using a clock sweep algorithm to find free buffers. @@ -37,59 +37,87 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian - Allow indexes to be used for MIN/MAX (Tom) + Allow indexes to be used for MIN/MAX (Tom) - + In previous releases, the only way to use index for MIN/MAX was to rewrite - the query as SELECT col FROM tab ORDER BY col LIMIT 1. This now happens + the query as SELECT col FROM tab ORDER BY col LIMIT 1. This now happens automatically. - + - Add in-memory bitmaps which allows multiple indexes to be merged in a - single query (Tom) - + Add in-memory bitmaps which allows multiple indexes to be merged in a + single query (Tom) + - + This allows multiple indexes to be combined to access a single table. - + - + Add two-phase commit (Heikki Linnakangas, Alvaro, Tom) + + + + + Two-phase commit allows transactions to be "prepared" on several + computers, and once all computers have successfully prepared their + transactions (and can not be rolled back) all transactions can be + committed. Even if a machine crashes after a prepare, the prepared + transaction can be committed after it is restarted. New syntax + includes PREPARE TRANSACTION and COMMIT/ROLLBACK PREPARED. A new + system view pg_prepared_xacts has also been added. + + + - + + + Replace pg_shadow and pg_group by new role-capable catalogs pg_authid + and pg_auth_members. + + + - + Add SET ROLE (Stephen Frost) + - + Move /contrib/pgautovacuum into the main server (Alvaro Herrera) + - + - + Add SET ROLE (Stephen Frost) + - + Add shared row level locks using SELECT ... FOR SHARE (Alvaro) + - + - + While PostgreSQL's MVCC locking allows SELECT to never be blocked by writers + and therefore does not need shared row locks for typical operations, + shared locks are useful for applications that require shared row locking, + and to reduce the locking requirements to maintain referential integrity. + @@ -154,6 +182,50 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian + + + Add E'' syntax so eventually normal strings can treat backslashes + literally (Bruce) + + + Currently PostgreSQL considers a backslash to be a special character + so the character after the backslash is treated specially. While this + allows easy entry of special values, it is non-standard and makes + porting of application from other databases more difficult. For this + reason, the PostgreSQL project is moving to remove the special meaning + of backslashes in strings, and allow only an E preceeding a string to + turn on the special handling of backslashes. For this reason, this + release adds several new GUC variables related to backslash + processing: + + escape_string_warning - warn about backslashes in non-E strings + escape_string_syntax - does this release support the E'' syntax? + standard_conforming_strings - does this release treat backslashes + literally in non-E strings + + + The last two values are read-only and should assist in the porting of + applications. Applications can retrieve these values to know how + backslashes are processed. In a later 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''. + + + + + + Make REINDEX DATABASE reindex all indexes in the database (Tom) + + + The old behavior of REINDEX database reindexed only system tables. + This new behavior seems more intuitive. A new command REINDEX SYSTEM + allows for reindexing just the system tables. + + + In psql, treat unquoted \{digit}+ sequences as octal (Bruce) @@ -325,6 +397,13 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian + + + Fix problem of OID wraparound conflicting with existing system objects + (Tom) + + + Add warning about the need to increase "max_fsm_relations" and @@ -360,7 +439,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian Allow Kerberos name and user name case sensitivity to be specified from - postgresql.conf + postgresql.conf (Magnus) @@ -401,25 +480,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian - - - Replace pg_shadow and pg_group by new role-capable catalogs pg_authid - and pg_auth_members. - - - - - - Add SET ROLE (Stephen Frost) - - - - - - Move /contrib/pgautovacuum into the main server (Alvaro Herrera) - - - Add GUC variables to control keep-alive times for idle, interval, and @@ -433,13 +493,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian - - - Fix problem of OID wraparound conflicting with existing system objects - (Tom) - - - @@ -478,18 +531,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian - - - Add shared row level locks using SELECT ... FOR SHARE (Alvaro) - - - While PostgreSQL's MVCC locking allows SELECT to never be blocked by writers - and therefore does not need shared row locks for typical operations, - shared locks are useful for applications that require shared row locking, - and to reduce the locking requirements to maintain referential integrity. - - - Add BETWEEN SYMMETRIC query syntax (Pavel Stehule) @@ -502,39 +543,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian - - - Add E'' syntax so eventually normal strings can treat backslashes - literally (Bruce) - - - Currently PostgreSQL considers a backslash to be a special character - so the character after the backslash is treated specially. While this - allows easy entry of special values, it is non-standard and makes - porting of application from other databases more difficult. For this - reason, the PostgreSQL project is moving to remove the special meaning - of backslashes in strings, and allow only an E preceeding a string to - turn on the special handling of backslashes. For this reason, this - release adds several new GUC variables related to backslash - processing: - - escape_string_warning - warn about backslashes in non-E strings - escape_string_syntax - does this release support the E'' syntax? - standard_conforming_strings - does this release treat backslashes - literally in non-E strings - - - The last two values are read-only and should assist in the porting of - applications. Applications can retrieve these values to know how - backslashes are processed. In a later 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''. - - - Add NOWAIT option to SELECT ... FOR UPDATE/SHARE (Hans-Juergen Schoenig) @@ -675,22 +683,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian - Add two-phase commit (Heikki Linnakangas, Alvaro, Tom) - - Two-phase commit allows transactions to be "prepared" on several - computers, and once all computers have successfully prepared their - transactions (and can not be rolled back) all transactions can be - committed. Even if a machine crashes after a prepare, the prepared - transaction can be committed after it is restarted. New syntax - includes PREPARE TRANSACTION and COMMIT/ROLLBACK PREPARED. A new - system view pg_prepared_xacts has also been added. - - - - - - Have initdb create new standard database called "postgres" and convert utilities - to use "postgres" rather than "template1" for standard lookups (Dave) + Have initdb create 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 @@ -703,17 +698,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian - - - Make REINDEX DATABASE reindex all indexes in the database (Tom) - - - The old behavior of REINDEX database reindexed only system tables. - This new behavior seems more intuitive. A new command REINDEX SYSTEM - allows for reindexing just the system tables. - - - Create new reindexdb command-line utility by moving /contrib/reindexdb @@ -960,7 +944,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian Change pg_stat_* views to show TOAST tables (Tom) - + + + @@ -1388,7 +1374,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian - Streamline the passing information within the server, the optimizer, + Streamline the passing of information within the server, the optimizer, and the lock system (Tom) -- 2.40.0