Stamp 9.0 release notes with expected release date; also some last-minute

copy-editing.

diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 833753aedeb3f2ecb445621265048dbe11b4857c..717a4c47f390e7a4123f548ae823f3ab17ee543b 100644 (file)
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -1,5 +1,5 @@
 
 
@@ -163,14 +163,14 @@ ALTER TABLE name
     RESET ( attribute_option [, ... ] )
     
      
-      This form sets or resets attribute-level options.  Currently, the only
-      define attribute-level options are n_distinct and
+      This form sets or resets per-attribute options.  Currently, the only
+      defined per-attribute options are n_distinct and
       n_distinct_inherited, which override the
-      number-of-distinct-values estimate made by subsequent
+      number-of-distinct-values estimates made by subsequent
       
       operations.  n_distinct affects the statistics for the table
       itself, while n_distinct_inherited affects the statistics
-      gathered for the table and its inheritance children.  When set to a
+      gathered for the table plus its inheritance children.  When set to a
       positive value, ANALYZE will assume that the column contains
       exactly the specified number of distinct nonnull values.  When set to a
       negative value, which must be greater

diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml
index 6d29ddd1e935f888696855ed63ebdcc21ca867ba..d1f081fa830a387521fee6ca9c70f7b9c83420fd 100644 (file)
--- a/doc/src/sgml/release-9.0.sgml
+++ b/doc/src/sgml/release-9.0.sgml
@@ -1,15 +1,14 @@
-
+
+
 
  
   Release 9.0
 
   
    Release date
-   2010-??-??
+   2010-09-20
   
 
-  CURRENT AS OF 2010-08-24
-
   
    Overview
 
@@ -47,7 +46,7 @@
       SCHEMA supports mass permissions changes on existing objects,
       while ALTER DEFAULT
       PRIVILEGES allows control of privileges for objects created in
-      the future.  Large objects (BLOBs) now support privilege management as
+      the future.  Large objects (BLOBs) now support permissions management as
       well.
      
     
@@ -189,9 +188,9 @@
   
    Version 9.0 contains a number of changes that selectively break backwards
    compatibility in order to support new features and code quality
-   improvements.  Also, users who make extensive use of PL/pgSQL,
-   Point-In-Time Recovery (PITR), and Warm Standby should test their
-   solutions because of slight user-visible changes in these areas.
+   improvements.  In particular, users who make extensive use of PL/pgSQL,
+   Point-In-Time Recovery (PITR), or Warm Standby should test their
+   applications because of slight user-visible changes in those areas.
    Observe the following incompatibilities:
   
 
@@ -751,7 +750,7 @@
 
      
       
-       Allow setting of distinct statistics using 
+       Allow setting of number-of-distinct-values statistics using 
        linkend="SQL-ALTERTABLE">ALTER TABLE
        (Robert Haas)
       
@@ -890,7 +889,7 @@
        linkend="monitoring-stats-funcs-table">pg_stat_reset_single_table_counters()
        and pg_stat_reset_single_function_counters()
        to allow resetting the statistics counters for individual
-       tables and indexes (Magnus Hagander)
+       tables and functions (Magnus Hagander)
       
      
 
@@ -913,7 +912,7 @@
       
        Previously only per-database and per-role settings were possible,
        not combinations. All role and database settings are now stored
-       in the new pg_db_role_setting system table. A new
+       in the new pg_db_role_setting system catalog. A new
        psql command \drds shows these settings.
        The legacy system views pg_roles,
        pg_shadow, and pg_user
@@ -990,7 +989,8 @@
        known to the server.  This allows the server to correctly check that
        superuser-only parameters are only set by superusers.  Previously,
        the SET would be allowed and then ignored at session start,
-       making superuser-only custom parameters practically useless.
+       making superuser-only custom parameters much less useful than they
+       should be.
       
      
 
@@ -1067,7 +1067,7 @@
 
      
       
-       Add Unicode surrogate pair (dual 16-bit) support to
+       Support Unicode surrogate pairs (dual 16-bit representation) in
        
        linkend="sql-syntax-strings-uescape">U&
        strings and identifiers (Peter Eisentraut)
@@ -1184,7 +1184,7 @@
 
      
       
-       Add support for copying all attributes in CREATE
+       Add a shortcut for copying all properties in CREATE
        TABLE ... LIKE commands (Itagaki Takahiro)
       
      
@@ -1661,31 +1661,31 @@
 
     
      
-      Support locale-specific 
-      linkend="functions-posix-regexp">regular expression
-      processing with UTF-8 server encoding (Tom Lane)
+      Allow function calls to supply parameter names and match them to named
+      parameters in the function definition (Pavel Stehule)
      
 
      
-      Locale-specific regular expression functionality includes
-      case-insensitive matching and locale-specific character classes.
-      Previously, these features only worked correctly for
-      non-ASCII characters when using a single-byte server
-      encoding (such as LATIN1).  They will still misbehave in multi-byte
-      encodings other than UTF-8.
+      For example, if a function is defined to take parameters a
+      and b, it can be called with func(a := 7, b
+      := 12) or func(b := 12, a := 7).
      
     
 
     
      
-      Allow function calls to supply parameter names and match them to named
-      parameters in the function definition (Pavel Stehule)
+      Support locale-specific 
+      linkend="functions-posix-regexp">regular expression
+      processing with UTF-8 server encoding (Tom Lane)
      
 
      
-      For example, if a function is defined to take parameters a
-      and b, it can be called with func(a := 7, b
-      := 12) or func(b := 12, a := 7).
+      Locale-specific regular expression functionality includes
+      case-insensitive matching and locale-specific character classes.
+      Previously, these features worked correctly for non-ASCII
+      characters only if the database used a single-byte server encoding (such
+      as LATIN1).  They will still misbehave in multi-byte encodings other
+      than UTF-8.
      
     
 
@@ -2009,7 +2009,7 @@
        rather than whenever the enclosing expression is reached.  For
        example, many people have tried to do this in triggers:
 
-if TG_OP = 'INSERT' AND NEW.col1 = ... then
+if TG_OP = 'INSERT' and NEW.col1 = ... then
 
        This will now actually work as expected.
       
@@ -2235,9 +2235,9 @@ if TG_OP = 'INSERT' AND NEW.col1 = ... then
 
     
     
-     Add vacuumdb
-     --analyze-only option to analyze without vacuuming
-     (Bruce Momjian)
+     Add an --analyze-only option to 
+     linkend="APP-VACUUMDB">vacuumdb, to analyze without
+     vacuuming (Bruce Momjian)
      
     
 
@@ -2573,7 +2573,8 @@ if TG_OP = 'INSERT' AND NEW.col1 = ... then
 
      
       
-       Load SSL certificate chains (Tom Lane)
+       Load all SSL certificates given in the client certificate file
+       (Tom Lane)
       
 
       
@@ -2601,16 +2602,15 @@ if TG_OP = 'INSERT' AND NEW.col1 = ... then
      
       
        Add the DESCRIBE
-       [OUTPUT] statement to ecpg
+       [ OUTPUT ] statement to ecpg
        (Boszormenyi Zoltan)
       
      
 
      
       
-       Add an ecpg function 
-       linkend="ecpg-library">ECPGtransactionStatus to return the
-       current transaction status (Bernd Helmle)
+       Add an ECPGtransactionStatus
+       function to return the current transaction status (Bernd Helmle)
       
      
 
@@ -2707,7 +2707,7 @@ if TG_OP = 'INSERT' AND NEW.col1 = ... then
      
 
      
-      Thread-safe builds can be disabled with 
+      The thread-safety option can be disabled with 
       linkend="configure">configure
       --disable-thread-safety.
      
@@ -2747,7 +2747,7 @@ if TG_OP = 'INSERT' AND NEW.col1 = ... then
 
       
        These are similar to the existing all, install,
-       and installcheck targets, but they also build
+       and installcheck targets, but they also build the
        HTML documentation, build and test contrib,
        and test server-side languages and ecpg.
       
@@ -2763,8 +2763,8 @@ if TG_OP = 'INSERT' AND NEW.col1 = ... then
 
     
      
-      Add Makefile rules to build documentation as a single HTML
-      file or as a single plain-text file
+      Add Makefile rules to build the PostgreSQL documentation
+      as a single HTML file or as a single plain-text file
       (Peter Eisentraut, Bruce Momjian)
      
     
@@ -3127,7 +3127,7 @@ if TG_OP = 'INSERT' AND NEW.col1 = ... then
 
       
        Existing calls will still work for the moment, but can be expected to
-       break in 9.1 or later if not converted.
+       break in 9.1 or later if not converted to the new style.
       
      
 
@@ -3170,13 +3170,6 @@ if TG_OP = 'INSERT' AND NEW.col1 = ... then
       
      
 
-     
-      
-       Allow the calling of parser hooks from SPI and cached
-       plans (Tom Lane)
-      
-     
-
      
       
        Add a ProcessUtility hook so loadable modules can control utility




This is the main PostgreSQL git repository.
RSS
Atom



window.onload = function () {
	var tz_cookie = { name: 'gitweb_tz', expires: 14, path: '/' };
	onloadTZSetup('local', tz_cookie, 'datetime');
};