Copy-editing.

This commit is contained in:
Tom Lane 2001-11-23 22:06:20 +00:00
parent ec27da1ce3
commit b104ffbd3d
3 changed files with 11 additions and 10 deletions

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.16 2001/11/08 23:34:33 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.17 2001/11/23 22:06:20 tgl Exp $
--> -->
<sect1 id="history"> <sect1 id="history">
@ -42,8 +42,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.16 2001/11/08 23:34:33 pet
<productname>Postgres</productname> has undergone several major releases since <productname>Postgres</productname> has undergone several major releases since
then. The first <quote>demoware</quote> system became operational then. The first <quote>demoware</quote> system became operational
in 1987 and was shown at the 1988 <acronym>ACM-SIGMOD</acronym> in 1987 and was shown at the 1988 <acronym>ACM-SIGMOD</acronym>
Conference. We released Version 1, described in Conference. Version 1, described in
<xref linkend="STON90a">, <xref linkend="STON90a">, was released
to a few external users in June 1989. In response to a to a few external users in June 1989. In response to a
critique of the first rule system critique of the first rule system
(<xref linkend="STON89">), (<xref linkend="STON89">),
@ -54,7 +54,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.16 2001/11/08 23:34:33 pet
released in June 1990 with the new rule system. released in June 1990 with the new rule system.
Version 3 appeared in 1991 and added support for multiple Version 3 appeared in 1991 and added support for multiple
storage managers, an improved query executor, and a storage managers, an improved query executor, and a
rewritten rewrite rule system. For the most part, rewritten rewrite rule system. For the most part, subsequent
releases until <productname>Postgres95</productname> (see below) releases until <productname>Postgres95</productname> (see below)
focused on portability and reliability. focused on portability and reliability.
</para> </para>
@ -87,7 +87,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.16 2001/11/08 23:34:33 pet
obvious that maintenance of the prototype code and obvious that maintenance of the prototype code and
support was taking up large amounts of time that should support was taking up large amounts of time that should
have been devoted to database research. In an effort have been devoted to database research. In an effort
to reduce this support burden, the project officially to reduce this support burden, the Berkeley
<productname>Postgres</productname> project officially
ended with Version 4.2. ended with Version 4.2.
</para> </para>
</sect2> </sect2>

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.17 2001/11/21 05:53:41 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.18 2001/11/23 22:06:20 tgl Exp $
--> -->
<preface id="preface"> <preface id="preface">
@ -42,7 +42,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.17 2001/11/21 05:53:41 thoma
processing applications. processing applications.
The relational model successfully replaced previous The relational model successfully replaced previous
models in part because of its <quote>Spartan simplicity</quote>. models in part because of its <quote>Spartan simplicity</quote>.
However, as mentioned, this simplicity often makes the However, this simplicity makes the
implementation of certain applications very difficult. implementation of certain applications very difficult.
<productname>PostgreSQL</productname> offers substantial additional <productname>PostgreSQL</productname> offers substantial additional
power by incorporating the following additional power by incorporating the following additional
@ -86,7 +86,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.17 2001/11/21 05:53:41 thoma
category of databases referred to as category of databases referred to as
<firstterm>object-relational</firstterm>. Note that this is distinct <firstterm>object-relational</firstterm>. Note that this is distinct
from those referred to as <firstterm>object-oriented</firstterm>, from those referred to as <firstterm>object-oriented</firstterm>,
which in general are not as well suited to supporting the which in general are not as well suited to supporting
traditional relational database languages. traditional relational database languages.
So, although <productname>PostgreSQL</productname> has some So, although <productname>PostgreSQL</productname> has some
object-oriented features, it is firmly in the relational database object-oriented features, it is firmly in the relational database

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.18 2001/11/21 05:53:41 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.19 2001/11/23 22:06:20 tgl Exp $
--> -->
<sect1 id="notation"> <sect1 id="notation">
@ -33,7 +33,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.18 2001/11/21 05:53:41 th
Anything in braces Anything in braces
(<literal>{</literal> and <literal>}</literal>) and containing vertical bars (<literal>{</literal> and <literal>}</literal>) and containing vertical bars
(<literal>|</literal>) (<literal>|</literal>)
indicates that you must choose one. indicates that you must choose one alternative.
</para> </para>
<para> <para>