From 091b2620086282e8a4eb28309b726aca9ea59736 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 10 Jun 2001 03:46:31 +0000
Subject: [PATCH] Update or remove mentions of versions where appropriate.
---
doc/src/sgml/ref/create_trigger.sgml | 4 ++--
doc/src/sgml/ref/psql-ref.sgml | 6 +++---
doc/src/sgml/ref/select.sgml | 6 +++---
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml
index 1dc633ce9d1..71f26d1c5fa 100644
--- a/doc/src/sgml/ref/create_trigger.sgml
+++ b/doc/src/sgml/ref/create_trigger.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.13 2001/05/27 09:59:28 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.14 2001/06/10 03:46:31 momjian Exp $
Postgres documentation
-->
@@ -150,7 +150,7 @@ CREATE
Only the relation owner may create a trigger on this relation.
</para>
<para>
- As of the current release (v7.0), STATEMENT triggers are not implemented.
+ As of the current release, STATEMENT triggers are not implemented.
</para>
<para>
Refer to <command>DROP TRIGGER</command> for information on how to
diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml
index a3b49bc3f6f..2a4fe712201 100644
--- a/doc/src/sgml/ref/psql-ref.sgml
+++ b/doc/src/sgml/ref/psql-ref.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.55 2001/05/28 04:27:17 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.56 2001/06/10 03:46:31 momjian Exp $
Postgres documentation
-->
@@ -1051,7 +1051,7 @@ lo_import 152801
<note>
<para>
- As of <application>psql</application> version 7.0 it is no longer
+ In the current version, it is no longer
necessary to save the command history, since that will be done
automatically on program termination. The history is
also loaded automatically every time <application>psql</application>
@@ -1579,7 +1579,7 @@ Access permissions for database "test"
</para>
<para>
- As of version 7.0, <application>psql</application> automatically issues a
+ In the current version, <application>psql</application> automatically issues a
password prompt whenever the backend requests password authentication.
Because this is currently based on a hack, the automatic
recognition might mysteriously fail, hence this option to force a prompt.
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index 4d95b26e034..b6bbd7e5d1e 100644
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.42 2001/05/30 04:32:30 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.43 2001/06/10 03:46:31 momjian Exp $
Postgres documentation
-->
@@ -122,8 +122,8 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
table is scanned. If ONLY is not specified, the table and all its
descendant tables (if any) are scanned. * can be appended to the
table name to indicate that descendant tables are to be scanned,
- but as of <Productname>Postgres</Productname> 7.1 this is the default
- behavior. (In releases before 7.1, ONLY was the default behavior.)
+ but in the current version, this is the default behavior.
+ (In releases before 7.1, ONLY was the default behavior.)
</para>
</listitem>
</varlistentry>
--
GitLab