Deprecate 'current' date/time constant.

Purge "Postgres" in favor of "PostgreSQL" in docs. ref/ not yet done.

Author: Thomas G. Lockhart

doc/src/sgml/reference.sgml

@@ -1,5 +1,5 @@
 <!-- reference.sgml
-$Header: /cvsroot/pgsql/doc/src/sgml/reference.sgml,v 1.18 2001/09/03 12:57:49 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/reference.sgml,v 1.19 2001/11/21 06:09:44 thomas Exp $
 
 PostgreSQL Reference Manual
 -->
@@ -128,7 +128,7 @@ Disable this chapter until we have more functions documented.
    <para>
     This part provides reference information for the
     <acronym>SQL</acronym> functions supported by
-    <productname>Postgres</productname>.
+    <productname>PostgreSQL</productname>.
    </para>
 
    &currentDate;

doc/src/sgml/release.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.103 2001/11/08 23:42:23 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.104 2001/11/21 06:09:44 thomas Exp $
 -->
 
  <appendix id="release">
@@ -829,7 +829,7 @@ ecpg changes (Michael)
     <para>
      A dump/restore using <application>pg_dump</application>
      is required for those wishing to migrate data from any
-     previous release of <productname>Postgres</productname>.
+     previous release of <productname>PostgreSQL</productname>.
      For those upgrading from 6.5.*, you may instead use 
      <application>pg_upgrade</application> to upgrade to this
      release; however, a full dump/reload installation is always the
@@ -848,7 +848,7 @@ ecpg changes (Michael)
 	SQL92-defined types <type>timestamp</type> and
 	<type>interval</type>. Although there has been some effort to
 	ease the transition by allowing
-	<productname>Postgres</productname> to recognize
+	<productname>PostgreSQL</productname> to recognize
 	the deprecated type names and translate them to the new type
 	names, this mechanism may not be completely transparent to
 	your existing application.
@@ -1554,7 +1554,7 @@ Add Win1250 (Czech) support (Pavel Behal)
 	chapter on troubleshooting from Tom Lane.
 	And the <citetitle>Programmer's Guide</citetitle> has a
 	description of query processing, also from Stefan, and details 
-	on obtaining the <productname>Postgres</productname> source
+	on obtaining the <productname>PostgreSQL</productname> source
 	tree via anonymous <productname>CVS</productname> and
 	<productname>CVSup</productname>. 
        </para>
@@ -1569,7 +1569,7 @@ Add Win1250 (Czech) support (Pavel Behal)
     <para>
      A dump/restore using <application>pg_dump</application>
      is required for those wishing to migrate data from any
-     previous release of <productname>Postgres</productname>.
+     previous release of <productname>PostgreSQL</productname>.
      <application>pg_upgrade</application> can <emphasis>not</emphasis>
      be used to upgrade to this release because the on-disk structure
      of the tables has changed compared to previous releases.
@@ -1602,7 +1602,7 @@ Add Win1250 (Czech) support (Pavel Behal)
       concurrent updates one must use <command>SELECT FOR UPDATE</command> or
       an appropriate <command>LOCK TABLE</command> statement. This should be
       taken into account when porting applications from previous releases of
-      <productname>Postgres</productname> and other environments.
+      <productname>PostgreSQL</productname> and other environments.
      </para>
 
      <para>
@@ -1986,7 +1986,7 @@ asynchronous messages and interrupts thanks to Tom Lane.
 The parser will now perform automatic type coercion to match arguments
 to available operators and functions, and to match columns and expressions
 with target columns. This uses a generic mechanism which supports
-the type extensibility features of <productname>Postgres</productname>.
+the type extensibility features of <productname>PostgreSQL</productname>.
 There is a new chapter in the <citetitle>User's Guide</citetitle>
 which covers this topic.
 </para>
@@ -2029,7 +2029,7 @@ been.
 A dump/restore using <application>pg_dump</application> 
 or <application>pg_dumpall</application>
 is required for those wishing to migrate data from any
-previous release of <productname>Postgres</productname>.
+previous release of <productname>PostgreSQL</productname>.
 </para>
 </sect2>
 
@@ -2281,7 +2281,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 
 <literal>make distclean</>, <literal>make</>, and <literal>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 <productname>Postgres</productname> libraries.
+You should re-link any custom applications that use <productname>PostgreSQL</productname> libraries.
 </para>
 <para>
 For upgrades from pre-6.3 installations,
@@ -2369,7 +2369,7 @@ Improvements to the configuration autodetection for installation.
 A dump/restore is NOT required for those running 6.3.  A 
 <literal>make distclean</>, <literal>make</>, and <literal>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 <productname>Postgres</productname> libraries.
+You should re-link any custom applications that use <productname>PostgreSQL</productname> libraries.
 </para>
 <para>
 For upgrades from pre-6.3 installations,
@@ -2542,7 +2542,7 @@ Better identify tcl and tk libs and includes(Bruce)
     \d command for types, operators, etc.  Also, views have their own
     permissions now, not based on the underlying tables, so permissions on
     them have to be set separately.  Check <filename>/pgsql/interfaces</filename> for some new
-    ways to talk to <productname>Postgres</productname>.
+    ways to talk to <productname>PostgreSQL</productname>.
    </para>
    <para>
     This is the first release that really required an explanation for
@@ -2558,7 +2558,7 @@ Better identify tcl and tk libs and includes(Bruce)
      A dump/restore using <application>pg_dump</application> 
      or <application>pg_dumpall</application>
      is required for those wishing to migrate data from any
-     previous release of <productname>Postgres</productname>.
+     previous release of <productname>PostgreSQL</productname>.
     </para>
    </sect2>
 
@@ -2615,7 +2615,7 @@ Modify constraint syntax to be SQL92-compliant(Thomas)
 Implement SQL92 PRIMARY KEY and UNIQUE clauses using indexes(Thomas)
 Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas)
 Allow NOT NULL UNIQUE constraint clause (each allowed separately before)(Thomas)
-Allow Postgres-style casting ("::") of non-constants(Thomas)
+Allow PostgreSQL-style casting ("::") of non-constants(Thomas)
 Add support for SQL3 TRUE and FALSE boolean constants(Thomas)
 Support SQL92 syntax for IS TRUE/IS FALSE/IS NOT TRUE/IS NOT FALSE(Thomas)
 Allow shorter strings for boolean literals (e.g. "t", "tr", "tru")(Thomas)
@@ -2628,7 +2628,7 @@ Use shared lock when building indexes(Vadim)
 Free memory allocated for an user query inside transaction block after
 	this query is done, was turned off in <= 6.2.1(Vadim)
 New SQL statement CREATE PROCEDURAL LANGUAGE(Jan)
-New <productname>Postgres</productname> Procedural Language (PL) backend interface(Jan)
+New <productname>PostgreSQL</productname> Procedural Language (PL) backend interface(Jan)
 Rename pg_dump -H option to -h(Bruce)
 Add Java support for passwords, European dates(Peter)
 Use indexes for LIKE and ~, !~ operations(Bruce)
@@ -2637,7 +2637,7 @@ Time Travel removed(Vadim, Bruce)
 Add paging for \d and \z, and fix \i(Bruce)
 Add Unix domain socket support to backend and to frontend library(Goran)
 Implement CREATE DATABASE/WITH LOCATION and initlocation utility(Thomas)
-Allow more SQL92 and/or <productname>Postgres</productname> reserved words as column identifiers(Thomas)
+Allow more SQL92 and/or <productname>PostgreSQL</productname> reserved words as column identifiers(Thomas)
 Augment support for SQL92 SET TIME ZONE...(Thomas)
 SET/SHOW/RESET TIME ZONE uses TZ backend environment variable(Thomas)
 Implement SET keyword = DEFAULT and SET TIME ZONE DEFAULT(Thomas)
@@ -2850,7 +2850,7 @@ Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
 
 <para>
 A dump/restore is required for those wishing to migrate data from
-previous releases of <productname>Postgres</productname>.
+previous releases of <productname>PostgreSQL</productname>.
 </para>
 
 <sect2>
@@ -3071,19 +3071,19 @@ pg_dumpall now returns proper status, portability fix(Bruce)
 
 <para>
   The regression tests have been adapted and extensively modified for the
-  6.1 release of <productname>Postgres</productname>.
+  6.1 release of <productname>PostgreSQL</productname>.
 </para>
 
 <para>
   Three new data types (<type>datetime</type>, <type>timespan</type>, and <type>circle</type>) have been added to
-  the native set of <productname>Postgres</productname> types. Points, boxes, paths, and polygons
+  the native set of <productname>PostgreSQL</productname> types. Points, boxes, paths, and polygons
   have had their output formats made consistent across the data types.
   The polygon output in misc.out has only been spot-checked for correctness
   relative to the original regression output.
 </para>
 
 <para>
-  <productname>Postgres</productname> 6.1 introduces a new, alternate
+  <productname>PostgreSQL</productname> 6.1 introduces a new, alternate
 optimizer which uses <firstterm>genetic</firstterm>
   algorithms. These algorithms introduce a random behavior in the ordering
   of query results when the query contains multiple qualifiers or multiple
@@ -3253,7 +3253,7 @@ DG-UX, Ultrix, Irix, AIX portability fixes
 
 <para>
 A dump/restore is required for those wishing to migrate data from
-previous releases of <productname>Postgres</productname>.
+previous releases of <productname>PostgreSQL</productname>.
 </para>
 
 <sect2>

doc/src/sgml/rules.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/rules.sgml,v 1.18 2001/11/12 19:19:39 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/rules.sgml,v 1.19 2001/11/21 06:09:45 thomas Exp $ -->
 
 <Chapter Id="rules">
 <Title>The Rule System</Title>
@@ -18,15 +18,15 @@
      Production rule systems are conceptually simple, but
      there are many subtle points involved in actually using
      them. Some of these points and
-     the theoretical foundations of the <ProductName>Postgres</ProductName>
+     the theoretical foundations of the <ProductName>PostgreSQL</ProductName>
      rule system can be found in
 <XRef LinkEnd="STON90b">.
 </Para>
 
 <Para>
      Some other database systems define active database rules. These
      are usually stored procedures and triggers and are implemented
-     in <ProductName>Postgres</ProductName> as functions and triggers.
+     in <ProductName>PostgreSQL</ProductName> as functions and triggers.
 </Para>
 
 <Para>
@@ -64,7 +64,7 @@
     Now what is a query tree? It is an internal representation of an
     <Acronym>SQL</Acronym> statement where the single parts that built
     it are stored separately. These query trees are visible when starting
-    the <ProductName>Postgres</ProductName> backend with debug level 4
+    the <ProductName>PostgreSQL</ProductName> backend with debug level 4
     and typing queries into the interactive backend interface. The rule
     actions in the <FileName>pg_rewrite</FileName> system catalog are
     also stored as query trees. They are not formatted like the debug
@@ -268,10 +268,10 @@
 <indexterm zone="rules-views"><primary>rules</><secondary>and views</></>
 
 <Sect2>
-<Title>Implementation of Views in <ProductName>Postgres</ProductName></Title>
+<Title>Implementation of Views in <ProductName>PostgreSQL</ProductName></Title>
 
 <Para>
-    Views in <ProductName>Postgres</ProductName> are implemented
+    Views in <ProductName>PostgreSQL</ProductName> are implemented
     using the rule system. In fact there is absolutely no difference
     between a
 
@@ -289,7 +289,7 @@
 
     because this is exactly what the CREATE VIEW command does internally.
     This has some side effects. One of them is that
-    the information about a view in the <ProductName>Postgres</ProductName>
+    the information about a view in the <ProductName>PostgreSQL</ProductName>
     system catalogs is exactly the same as it is for a table. So for the
     query parser, there is absolutely no difference between
     a table and a view. They are the same thing - relations. That is the
@@ -785,7 +785,7 @@
     SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a;
 </ProgramListing>
 
-    Now another detail of <ProductName>Postgres</ProductName> enters the
+    Now another detail of <ProductName>PostgreSQL</ProductName> enters the
     stage. At this moment, table rows aren't overwritten and this is why
     ABORT TRANSACTION is fast. In an UPDATE, the new result row is inserted
     into the table (after stripping ctid) and in the tuple header of the row 
@@ -802,7 +802,7 @@
 </Sect2>
 
 <Sect2>
-<Title>The Power of Views in <ProductName>Postgres</ProductName></Title>
+<Title>The Power of Views in <ProductName>PostgreSQL</ProductName></Title>
 
 <Para>
     The above demonstrates how the rule system incorporates
@@ -826,7 +826,7 @@
     Now the planner has to decide which is
     the best path to execute the query. The more information
     the planner has, the better this decision can be. And
-    the rule system as implemented in <ProductName>Postgres</ProductName>
+    the rule system as implemented in <ProductName>PostgreSQL</ProductName>
     ensures, that this is all information available about the query
     up to now.
 </Para>
@@ -1604,7 +1604,7 @@ Merge Join
 </Para>
 
 <Para>
-    A final demonstration of the <ProductName>Postgres</ProductName>
+    A final demonstration of the <ProductName>PostgreSQL</ProductName>
     rule system and its power. There is a cute blonde that
     sells shoelaces. And what Al could never realize, she's not
     only cute, she's smart too - a little too smart. Thus, it
@@ -1644,7 +1644,7 @@ Merge Join
 
     For the 1000 magenta shoelaces we must debt Al before we can
     throw 'em away, but that's another problem. The pink entry we delete.
-    To make it a little harder for <ProductName>Postgres</ProductName>,
+    To make it a little harder for <ProductName>PostgreSQL</ProductName>,
     we don't delete it directly. Instead we create one more view
 
 <ProgramListing>
@@ -1708,7 +1708,7 @@ Merge Join
 <Title>Rules and Permissions</Title>
 
 <Para>
-    Due to rewriting of queries by the <ProductName>Postgres</ProductName>
+    Due to rewriting of queries by the <ProductName>PostgreSQL</ProductName>
     rule system, other tables/views than those used in the original
     query get accessed. Using update rules, this can include write access
     to tables.
@@ -1718,7 +1718,7 @@ Merge Join
     Rewrite rules don't have a separate owner. The owner of
     a relation (table or view) is automatically the owner of the
     rewrite rules that are defined for it.
-    The <ProductName>Postgres</ProductName> rule system changes the
+    The <ProductName>PostgreSQL</ProductName> rule system changes the
     behavior of the default access control system. Relations that
     are used due to rules get checked against the
     permissions of the rule owner, not the user invoking the rule.
@@ -1798,7 +1798,7 @@ Merge Join
 
 <Para>
     Many things that can be done using triggers can also be
-    implemented using the <ProductName>Postgres</ProductName>
+    implemented using the <ProductName>PostgreSQL</ProductName>
     rule system. What currently cannot be implemented by
     rules are some kinds of constraints. It is possible,
     to place a qualified rule that rewrites a query to NOTHING
@@ -1971,7 +1971,7 @@ Merge Join
 <Para>
     Another situation is cases on UPDATE where it depends on the
     change of an attribute if an action should be performed or
-    not. In <ProductName>Postgres</ProductName> version 6.4, the
+    not. In <ProductName>PostgreSQL</ProductName> version 6.4, the
     attribute specification for rule events is disabled (it will have
     its comeback latest in 6.5, maybe earlier 
     - stay tuned). So for now the only way to