head	1.36;
access;
symbols
	REL9_0_0:1.36
	REL9_1_ALPHA1:1.36
	REL9_0_RC1:1.36
	REL9_0_BETA4:1.36
	REL9_0_STABLE:1.36.0.4
	REL9_0_BETA3:1.36
	REL9_0_BETA2:1.36
	REL7_4_29:1.23
	REL8_0_25:1.27
	REL8_1_21:1.30
	REL8_2_17:1.31
	REL8_3_11:1.32
	REL8_4_4:1.35
	REL9_0_BETA1:1.36
	REL9_0_ALPHA5_BRANCH:1.36.0.2
	REL9_0_ALPHA5:1.36
	REL7_4_28:1.23
	REL8_0_24:1.27
	REL8_1_20:1.30
	REL8_2_16:1.31
	REL8_3_10:1.32
	REL8_4_3:1.35
	REL9_0_ALPHA4:1.35
	REL9_0_ALPHA4_BRANCH:1.35.0.10
	REL8_5_ALPHA3:1.35
	REL8_5_ALPHA3_BRANCH:1.35.0.8
	REL7_4_27:1.23
	REL8_0_23:1.27
	REL8_1_19:1.30
	REL8_2_15:1.31
	REL8_3_9:1.32
	REL8_4_2:1.35
	REL8_5_ALPHA2:1.35
	REL8_5_ALPHA2_BRANCH:1.35.0.6
	REL7_4_26:1.23
	REL8_0_22:1.27
	REL8_1_18:1.30
	REL8_2_14:1.31
	REL8_3_8:1.32
	REL8_4_1:1.35
	REL8_5_ALPHA1:1.35
	REL8_5_ALPHA1_BRANCH:1.35.0.4
	REL8_4_STABLE:1.35.0.2
	REL8_4_0:1.35
	REL8_4_RC2:1.35
	REL8_4_RC1:1.35
	REL8_4_BETA2:1.35
	REL8_4_BETA1:1.34
	REL7_4_25:1.23
	REL8_0_21:1.27
	REL8_1_17:1.30
	REL8_2_13:1.31
	REL8_3_7:1.32
	REL7_4_24:1.23
	REL8_0_20:1.27
	REL8_1_16:1.30
	REL8_2_12:1.31
	REL8_3_6:1.32
	REL7_4_23:1.23
	REL8_0_19:1.27
	REL8_1_15:1.30
	REL8_2_11:1.31
	REL8_3_5:1.32
	REL7_4_22:1.23
	REL8_0_18:1.27
	REL8_1_14:1.30
	REL8_2_10:1.31
	REL8_3_4:1.32
	REL7_4_21:1.23
	REL8_0_17:1.27
	REL8_1_13:1.30
	REL8_2_9:1.31
	REL8_3_3:1.32
	REL7_4_20:1.23
	REL8_0_16:1.27
	REL8_1_12:1.30
	REL8_2_8:1.31
	REL8_3_2:1.32
	REL8_2_7:1.31
	REL8_3_1:1.32
	REL8_3_STABLE:1.32.0.2
	REL8_3_0:1.32
	REL8_3_RC2:1.32
	REL7_3_21:1.20
	REL7_4_19:1.23
	REL8_0_15:1.27
	REL8_1_11:1.30
	REL8_2_6:1.31
	REL8_3_RC1:1.32
	REL8_3_BETA4:1.32
	REL8_3_BETA3:1.32
	REL8_3_BETA2:1.32
	REL8_3_BETA1:1.32
	REL7_3_20:1.20
	REL7_4_18:1.23
	REL8_0_14:1.27
	REL8_1_10:1.30
	REL8_2_5:1.31
	REL7_3_19:1.20
	REL7_4_17:1.23
	REL8_0_13:1.27
	REL8_1_9:1.30
	REL8_2_4:1.31
	REL8_0_12:1.27
	REL8_1_8:1.30
	REL8_2_3:1.31
	REL7_3_18:1.20
	REL7_4_16:1.23
	REL8_0_11:1.27
	REL8_1_7:1.30
	REL8_2_2:1.31
	REL8_0_10:1.27
	REL8_1_6:1.30
	REL8_2_1:1.31
	REL7_4_15:1.23
	REL7_3_17:1.20
	REL8_2_STABLE:1.31.0.2
	REL8_2_0:1.31
	REL8_2_RC1:1.31
	REL8_2_BETA3:1.31
	REL8_2_BETA2:1.31
	REL8_1_5:1.30
	REL8_0_9:1.27
	REL7_4_14:1.23
	REL7_3_16:1.20
	REL8_2_BETA1:1.31
	REL7_3_15:1.20
	REL7_4_13:1.23
	REL8_0_8:1.27
	REL8_1_4:1.30
	REL7_3_14:1.20
	REL7_4_12:1.23
	REL8_0_7:1.27
	REL8_1_3:1.30
	REL7_3_13:1.20
	REL7_4_11:1.23
	REL8_0_6:1.27
	REL8_1_2:1.30
	REL7_3_12:1.20
	REL7_4_10:1.23
	REL8_0_5:1.27
	REL8_1_1:1.30
	REL8_1_STABLE:1.30.0.2
	REL8_1_0:1.30
	REL8_1_0RC1:1.29
	REL8_1_0BETA4:1.29
	REL8_1_0BETA3:1.29
	REL7_3_11:1.20
	REL7_4_9:1.23
	REL8_0_4:1.27
	REL8_1_0BETA2:1.29
	REL8_1_0BETA1:1.29
	REL7_2_8:1.19
	REL7_3_10:1.20
	REL7_4_8:1.23
	REL8_0_3:1.27
	REL8_0_2:1.27
	REL7_2_7:1.19
	REL7_3_9:1.20
	REL7_4_7:1.23
	REL8_0_1:1.27
	REL8_0_STABLE:1.27.0.4
	REL8_0_0:1.27.0.2
	REL8_0_0RC5:1.27
	REL8_0_0RC4:1.27
	REL8_0_0RC3:1.27
	REL8_0_0RC2:1.26
	REL8_0_0RC1:1.26
	REL8_0_0BETA5:1.25
	REL8_0_0BETA4:1.25
	REL7_4_6:1.23
	REL7_3_8:1.20
	REL7_2_6:1.19
	REL8_0_0BETA3:1.25
	REL8_0_0BETA2:1.25
	REL7_2_5:1.19
	REL7_4_5:1.23
	REL7_3_7:1.20
	REL7_4_4:1.23
	REL8_0_0BETA1:1.25
	REL7_4_3:1.23
	REL7_4_2:1.23
	REL7_3_6:1.20
	REL7_4_1:1.23
	REL7_3_5:1.20
	REL7_4:1.23
	REL7_4_RC2:1.23
	REL7_4_STABLE:1.23.0.2
	REL7_4_RC1:1.23
	REL7_4_BETA5:1.23
	REL7_4_BETA4:1.22
	REL7_4_BETA3:1.22
	REL7_4_BETA2:1.20
	WIN32_DEV:1.20.0.4
	REL7_4_BETA1:1.20
	REL7_3_4:1.20
	REL7_3_2:1.20
	REL7_2_4:1.19
	REL7_3_STABLE:1.20.0.2
	REL7_2_3:1.19
	REL7_2_STABLE:1.19.0.2
	REL7_2:1.19
	REL7_2_RC2:1.19
	REL7_2_RC1:1.19
	REL7_2_BETA5:1.19
	REL7_2_BETA4:1.18
	REL7_2_BETA3:1.16
	REL7_2_BETA2:1.16
	REL7_2_BETA1:1.16
	REL7_1_2:1.14
	REL7_1_STABLE:1.14.0.2
	REL7_1_BETA:1.12
	REL7_1_BETA3:1.12
	REL7_1_BETA2:1.12
	REL7_1:1.14
	REL7_0_PATCHES:1.11.0.2
	REL7_0:1.11
	REL6_5_PATCHES:1.7.0.2
	REL6_5:1.7
	REL6_4:1.5.0.2
	release-6-3:1.1;
locks; strict;
comment	@# @;


1.36
date	2010.03.17.17.12.31;	author petere;	state Exp;
branches;
next	1.35;

1.35
date	2009.04.27.16.27.36;	author momjian;	state Exp;
branches;
next	1.34;

1.34
date	2009.01.27.12.40.14;	author petere;	state Exp;
branches;
next	1.33;

1.33
date	2009.01.22.17.27.54;	author petere;	state Exp;
branches;
next	1.32;

1.32
date	2007.01.31.20.56.17;	author momjian;	state Exp;
branches;
next	1.31;

1.31
date	2006.03.10.19.10.48;	author momjian;	state Exp;
branches;
next	1.30;

1.30
date	2005.11.04.02.56.31;	author tgl;	state Exp;
branches;
next	1.29;

1.29
date	2005.04.09.03.52.43;	author momjian;	state Exp;
branches;
next	1.28;

1.28
date	2005.03.31.03.54.38;	author momjian;	state Exp;
branches;
next	1.27;

1.27
date	2004.12.23.05.37.39;	author tgl;	state Exp;
branches;
next	1.26;

1.26
date	2004.11.27.21.27.06;	author petere;	state Exp;
branches;
next	1.25;

1.25
date	2004.08.08.01.52.14;	author momjian;	state Exp;
branches;
next	1.24;

1.24
date	2003.11.29.19.51.37;	author pgsql;	state Exp;
branches;
next	1.23;

1.23
date	2003.10.21.22.47.54;	author tgl;	state Exp;
branches;
next	1.22;

1.22
date	2003.09.11.21.42.20;	author momjian;	state Exp;
branches;
next	1.21;

1.21
date	2003.09.08.23.02.28;	author petere;	state Exp;
branches;
next	1.20;

1.20
date	2002.10.24.17.48.54;	author petere;	state Exp;
branches;
next	1.19;

1.19
date	2002.01.07.02.29.12;	author petere;	state Exp;
branches;
next	1.18;

1.18
date	2001.11.23.22.06.20;	author tgl;	state Exp;
branches;
next	1.17;

1.17
date	2001.11.21.05.53.41;	author thomas;	state Exp;
branches;
next	1.16;

1.16
date	2001.10.09.18.46.00;	author petere;	state Exp;
branches;
next	1.15;

1.15
date	2001.10.04.22.27.58;	author petere;	state Exp;
branches;
next	1.14;

1.14
date	2001.02.03.19.03.27;	author petere;	state Exp;
branches;
next	1.13;

1.13
date	2001.01.13.23.58.55;	author petere;	state Exp;
branches;
next	1.12;

1.12
date	2000.09.29.20.21.34;	author petere;	state Exp;
branches;
next	1.11;

1.11
date	2000.04.07.13.30.58;	author thomas;	state Exp;
branches;
next	1.10;

1.10
date	2000.03.31.03.27.40;	author thomas;	state Exp;
branches;
next	1.9;

1.9
date	2000.03.30.22.22.40;	author thomas;	state Exp;
branches;
next	1.8;

1.8
date	2000.03.09.12.00.08;	author petere;	state Exp;
branches;
next	1.7;

1.7
date	99.06.01.17.26.18;	author thomas;	state Exp;
branches;
next	1.6;

1.6
date	98.12.29.02.24.16;	author thomas;	state Exp;
branches;
next	1.5;

1.5
date	98.10.25.00.24.36;	author thomas;	state Exp;
branches;
next	1.4;

1.4
date	98.09.30.05.41.45;	author thomas;	state Exp;
branches;
next	1.3;

1.3
date	98.07.29.06.35.16;	author thomas;	state Exp;
branches;
next	1.2;

1.2
date	98.04.28.14.54.24;	author thomas;	state Exp;
branches;
next	1.1;

1.1
date	98.03.01.08.15.55;	author thomas;	state Exp;
branches;
next	;


desc
@@


1.36
log
@Update broken and permanently moved links
@
text
@<!-- $PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.35 2009/04/27 16:27:36 momjian Exp $ -->

<preface id="preface">
 <title>Preface</title>

 <para>
  This book is the official documentation of
  <productname>PostgreSQL</productname>.  It has been written by the
  <productname>PostgreSQL</productname> developers and other
  volunteers in parallel to the development of the
  <productname>PostgreSQL</productname> software.  It describes all
  the functionality that the current version of
  <productname>PostgreSQL</productname> officially supports.
 </para>

 <para>
  To make the large amount of information about
  <productname>PostgreSQL</productname> manageable, this book has been
  organized in several parts.  Each part is targeted at a different
  class of users, or at users in different stages of their
  <productname>PostgreSQL</productname> experience:

  <itemizedlist>
   <listitem>
    <para>
     <xref linkend="tutorial"> is an informal introduction for new users.
    </para>
   </listitem>

   <listitem>
    <para>
     <xref linkend="sql"> documents the <acronym>SQL</acronym> query
     language environment, including data types and functions, as well
     as user-level performance tuning.  Every
     <productname>PostgreSQL</> user should read this.
    </para>
   </listitem>

   <listitem>
    <para>
     <xref linkend="admin"> describes the installation and
     administration of the server.  Everyone who runs a
     <productname>PostgreSQL</productname> server, be it for private
     use or for others, should read this part.
    </para>
   </listitem>

   <listitem>
    <para>
     <xref linkend="client-interfaces"> describes the programming
     interfaces for <productname>PostgreSQL</productname> client
     programs.
    </para>
   </listitem>


   <listitem>
    <para>
     <xref linkend="server-programming"> contains information for
     advanced users about the extensibility capabilities of the
     server.  Topics include user-defined data types and
     functions.
    </para>
   </listitem>

   <listitem>
    <para>
     <xref linkend="reference"> contains reference information about
     SQL commands, client and server programs.  This part supports
     the other parts with structured information sorted by command or
     program.
    </para>
   </listitem>

   <listitem>
    <para>
     <xref linkend="internals"> contains assorted information that might be of
     use to <productname>PostgreSQL</> developers.
    </para>
   </listitem>
  </itemizedlist>
 </para>

 <sect1 id="intro-whatis">
  <title> What is <productname>PostgreSQL</productname>?</title>

  <para>
   <productname>PostgreSQL</productname> is an object-relational
   database management system (<acronym>ORDBMS</acronym>) based on
   <ulink url="http://db.cs.berkeley.edu/postgres.html">
   <productname>POSTGRES, Version 4.2</productname></ulink>,
   developed at the University of California at Berkeley Computer Science
   Department.  POSTGRES pioneered many concepts that only became
   available in some commercial database systems much later.
  </para>

  <para>
   <productname>PostgreSQL</productname> is an open-source descendant
   of this original Berkeley code.  It supports a large part of the SQL
   standard and offers many modern features:

   <itemizedlist spacing="compact">
    <listitem>
     <simpara>complex queries</simpara>
    </listitem>
    <listitem>
     <simpara>foreign keys</simpara>
    </listitem>
    <listitem>
     <simpara>triggers</simpara>
    </listitem>
    <listitem>
     <simpara>views</simpara>
    </listitem>
    <listitem>
     <simpara>transactional integrity</simpara>
    </listitem>
    <listitem>
     <simpara>multiversion concurrency control</simpara>
    </listitem>
   </itemizedlist>

   Also, <productname>PostgreSQL</productname> can be extended by the
   user in many ways, for example by adding new

   <itemizedlist spacing="compact">
    <listitem>
     <simpara>data types</simpara>
    </listitem>
    <listitem>
     <simpara>functions</simpara>
    </listitem>
    <listitem>
     <simpara>operators</simpara>
    </listitem>
    <listitem>
     <simpara>aggregate functions</simpara>
    </listitem>
    <listitem>
     <simpara>index methods</simpara>
    </listitem>
    <listitem>
     <simpara>procedural languages</simpara>
    </listitem>
   </itemizedlist>
  </para>

  <para>
   And because of the liberal license,
   <productname>PostgreSQL</productname> can be used, modified, and
   distributed by anyone free of charge for any purpose, be it
   private, commercial, or academic.
  </para>
 </sect1>

 &history;
 &notation;
 &info;
 &problems;

</preface>
@


1.35
log
@Proofreading adjustments for first two parts of documentation (Tutorial
and SQL).
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.34 2009/01/27 12:40:14 petere Exp $ -->
d90 1
a90 1
   <ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
@


1.34
log
@Revert updatable views
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.33 2009/01/22 17:27:54 petere Exp $ -->
d8 1
a8 1
  <productname>PostgreSQL</productname>.  It is being written by the
d61 1
a61 1
     server.  Topics are, for instance, user-defined data types and
d151 1
a151 1
   distributed by everyone free of charge for any purpose, be it
@


1.33
log
@Automatic view update rules

Bernd Helmle
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.32 2007/01/31 20:56:17 momjian Exp $ -->
d113 1
a113 1
     <simpara>updatable views</simpara>
@


1.32
log
@Update documentation on may/can/might:

Standard English uses "may", "can", and "might" in different ways:

        may - permission, "You may borrow my rake."

        can - ability, "I can lift that log."

        might - possibility, "It might rain today."

Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice.  Similarly, "It may crash" is better stated, "It might crash".

Also update two error messages mentioned in the documenation to match.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.31 2006/03/10 19:10:48 momjian Exp $ -->
d113 1
a113 1
     <simpara>views</simpara>
@


1.31
log
@Make $PostgreSQL CVS tags consistent for SGML files.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/advanced.sgml,v 1.49 2005/04/09 03:52:43 momjian Exp $ -->
d77 1
a77 1
     <xref linkend="internals"> contains assorted information that may be of
@


1.30
log
@Avoid referring to a specific version of the SQL standard except where
necessary, and be careful to refer to the right version where it is
useful to do so.  This partially reverts an ill-considered search and
replace from a few months ago.
@
text
@d1 1
a1 3
<!--
$PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.29 2005/04/09 03:52:43 momjian Exp $
-->
@


1.29
log
@We don't put URL's in ulink's because the URL is always generated, but
we can put words in ulink and the URL will still be printed.

per Peter
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.28 2005/03/31 03:54:38 momjian Exp $
d101 1
a101 1
   of this original Berkeley code.  It supports a large part of the SQL:2003
@


1.28
log
@Adjust SGML ulink tags to the URL is always displayed in our printed docs.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.27 2004/12/23 05:37:39 tgl Exp $
a91 1
   <productname>POSTGRES, Version 4.2</productname>,
d93 2
a94 1
   </ulink>, developed at the University of California at Berkeley Computer Science
@


1.27
log
@A small pass of docs review and copy-editing.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.26 2004/11/27 21:27:06 petere Exp $
d92 1
d94 1
a94 2
   <productname>POSTGRES, Version 4.2</productname></ulink>, developed
   at the University of California at Berkeley Computer Science
@


1.26
log
@Update of conformance information to SQL:2003
by Troels Arvin, Simon Riggs, Elein Mustain

Make spelling of SQL standard names uniform.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/intro.sgml,v 1.25 2004/08/08 01:52:14 momjian Exp $
d44 1
a44 1
     administration of the server.  Everyone that runs a
d70 2
a71 2
     <xref linkend="reference"> contains information about the syntax
     of SQL commands, client and server programs.  This part supports
d79 1
a79 1
     <xref linkend="internals"> contains assorted information that can be of
@


1.25
log
@This patch adds SQL2003 to the set of standards with which PostgreSQL
is attempting to comply.

David Fetter
@
text
@d2 1
a2 1
$PostgreSQL: pgsql-server/doc/src/sgml/intro.sgml,v 1.24 2003/11/29 19:51:37 pgsql Exp $
d101 2
a102 2
   of this original Berkeley code.  It supports SQL92, SQL99 and
   SQL2003 and offers many modern features:
@


1.24
log
@
$Header: -> $PostgreSQL Changes ...
@
text
@d2 1
a2 1
$PostgreSQL: /cvsroot/pgsql-server/doc/src/sgml/intro.sgml,v 1.23 2003/10/21 22:47:54 tgl Exp $
d101 2
a102 2
   of this original Berkeley code.  It supports SQL92 and SQL99 and
   offers many modern features:
@


1.23
log
@For some reason, the preface mentions just six of the seven major parts
of the book.  Fix it.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql-server/doc/src/sgml/intro.sgml,v 1.22 2003/09/11 21:42:20 momjian Exp $
@


1.22
log
@This patch fixes a few missed GUC variables that were still upper case,
makes a few more small improvements to runtime.sgml, and makes some SGML
conventions more consistent.

Neil Conway
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql-server/doc/src/sgml/intro.sgml,v 1.21 2003/09/08 23:02:28 petere Exp $
d74 7
@


1.21
log
@Update preface.

Use question marks rather than brackets to delimit optional elements in
Tcl synopses.

Fix stylesheet misfeature leading to excessively long cross-reference text
when linking to a different "part".

Remove <body> attributes -- CSS stylesheets should handle that.

Improve bibliography formatting.

Add fast-forward links for more convenient navigation.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql-server/doc/src/sgml/intro.sgml,v 1.20 2002/10/24 17:48:54 petere Exp $
d9 7
a15 5
  This book is the official documentation of PostgreSQL.  It is being
  written by the PostgreSQL developers and other volunteers in
  parallel to the development of the PostgreSQL software.  It
  describes all the functionality that the current version of
  PostgreSQL officially supports.
d19 5
a23 4
  To make the large amount of information about PostgreSQL manageable,
  this book has been organized in several parts.  Each part is
  targeted at a different class of users, or at users in different
  stages of their PostgreSQL experience:
d44 3
a46 3
     administration of the server.  Everyone that runs a PostgreSQL
     server, be it for private use or for others, should read this
     part.
d53 2
a54 1
     interfaces for PostgreSQL client programs.
d118 2
a119 2
   Also, PostgreSQL can be extended by the user in many ways, for
   example by adding new
d144 4
a147 3
   And because of the liberal license, PostgreSQL can be used,
   modified, and distributed by everyone free of charge for any
   purpose, be it private, commercial, or academic.
@


1.20
log
@Add introductory sections explaining what each book is about.  Remove Y2K
statement.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql-server/doc/src/sgml/intro.sgml,v 1.19 2002/01/07 02:29:12 petere Exp $
d5 2
a6 2
  <sect1 id="intro-whatis">
   <title> What is <productname>PostgreSQL</productname>?</title>
d8 144
a151 103
   <para>
    <productname>PostgreSQL</productname> is an object-relational
    database management system (<acronym>ORDBMS</acronym>) based on
    <ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
    <productname>POSTGRES, Version 4.2</productname></ulink>,
    developed at the University of California at Berkeley Computer
    Science Department.  The <productname>POSTGRES</productname>
    project, led by Professor Michael Stonebraker, was sponsored by
    the Defense Advanced Research Projects Agency
    (<acronym>DARPA</acronym>), the Army Research Office
    (<acronym>ARO</acronym>), the National Science Foundation
    (<acronym>NSF</acronym>), and ESL, Inc.
   </para>

   <para>
    <productname>PostgreSQL</productname> is an open-source descendant of
    this original Berkeley code.  It provides SQL92/SQL99 language support
    and other modern features.
   </para>

   <para>
    <productname>POSTGRES</productname> pioneered many of the
    object-relational concepts now becoming available in some commercial
    databases.
    Traditional   relational  database  management  systems
    (<acronym>RDBMS</acronym>) support a data model consisting of a collection
    of named relations, containing attributes of a specific
    type.  In current commercial  systems,  possible  types
    include  floating  point  numbers,  integers, character
    strings, money, and dates.  It is  commonly  recognized
    that  this model is inadequate for future data-processing applications.
    The relational  model  successfully  replaced  previous
    models  in  part  because  of its <quote>Spartan simplicity</quote>.
    However, this simplicity makes  the
    implementation  of  certain applications very difficult.
    <productname>PostgreSQL</productname> offers  substantial additional
    power  by  incorporating  the following additional
    concepts in such a way that  users  can  easily
    extend the system:

    <itemizedlist spacing="compact">
     <listitem>
      <simpara>inheritance</>
     </listitem>
     <listitem>
      <simpara>data types</>
     </listitem>
     <listitem>
      <simpara>functions</simpara>
     </listitem>
    </itemizedlist>
   </para>

   <para>
    Other features provide additional power and flexibility:

    <itemizedlist spacing="compact">
     <listitem>
      <simpara>constraints</simpara>
     </listitem>
     <listitem>
      <simpara>triggers</simpara>
     </listitem>
     <listitem>
      <simpara>rules</simpara>
     </listitem>
     <listitem>
      <simpara>transactional integrity</simpara>
     </listitem>
    </itemizedlist>
   </para>

   <para>
    These features put <productname>PostgreSQL</productname> into the
    category of databases referred to as
    <firstterm>object-relational</firstterm>. Note that this is distinct
    from those referred to as <firstterm>object-oriented</firstterm>,
    which in general are not as well suited to supporting
    traditional relational database languages.
    So, although <productname>PostgreSQL</productname> has some
    object-oriented features, it is firmly in the relational database
    world. In fact, some commercial databases have recently
    incorporated features pioneered by <productname>PostgreSQL</productname>.
   </para>

  </sect1>

<!-- Keep this comment at the end of the file
Local variables:
mode:sgml
sgml-omittag:nil
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"./reference.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:("/usr/lib/sgml/catalog")
sgml-local-ecat-files:nil
End:
-->
@


1.19
log
@Editorial review
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.18 2001/11/23 22:06:20 tgl Exp $
a4 3
 <preface id="preface">
  <title>Preface</title>

a93 8

   &history;
   &info;
   &notation;
   &problems;
   &y2k;

 </preface>
@


1.18
log
@Copy-editing.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.17 2001/11/21 05:53:41 thomas Exp $
d41 1
a41 2
    that  this model is inadequate for future data 
    processing applications.
d78 1
a78 1
      <simpara>transaction integrity</simpara>
@


1.17
log
@Deprecate 'current' for date/time input.
Fix up references to "PostgreSQL" rather than "Postgres". Was roughly
 evenly split between the two before. ref/ files not yet done.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.16 2001/10/09 18:46:00 petere Exp $
d45 1
a45 1
    However, as mentioned, this simplicity often makes  the
d89 1
a89 1
    which in general are not as well suited to supporting the
@


1.16
log
@Bunch of copy fitting and style sheet tweakage to get decent looking print
output (from pdfjadetex).  Also updated instructions to install documentation
processing toolchain.
@
text
@d2 1
a2 1
$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.15 2001/10/04 22:27:58 petere Exp $
d47 1
a47 1
    <productname>Postgres</productname> offers  substantial additional
d85 1
a85 1
    These features put <productname>Postgres</productname> into the
d91 1
a91 1
    So, although <productname>Postgres</productname> has some
d94 1
a94 1
    incorporated features pioneered by <productname>Postgres</productname>.
@


1.15
log
@Replace simplelists with itemizedlists for better formatting
@
text
@d2 1
a2 1
$Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.14 2001/02/03 19:03:27 petere Exp $
d52 1
a52 1
    <itemizedlist>
d68 1
a68 1
    <itemizedlist>
@


1.14
log
@Update, polish, consistencify preface/intro sections.
@
text
@d2 1
a2 1
$Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.13 2001/01/13 23:58:55 petere Exp $
d52 11
a62 5
    <simplelist>
     <member>inheritance</member>
     <member>data types</member>
     <member>functions</member>
    </simplelist>
d68 14
a81 6
    <simplelist>
     <member>constraints</member>
     <member>triggers</member>
     <member>rules</member>
     <member>transaction integrity</member>
    </simplelist>
@


1.13
log
@Terminology cleanup: class -> table, instance -> row, attribute -> column,
etc.
@
text
@d2 1
a2 1
$Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.12 2000/09/29 20:21:34 petere Exp $
d5 2
a6 2
 <chapter id="intro">
  <title>Introduction</title>
d8 16
a23 16
  <para>
   This document is the user  manual  for  the  
   <ulink url="http://postgresql.org/"><productname>PostgreSQL</productname></ulink>
   database  management system, originally developed at the University
   of California at  Berkeley.   

   <productname>PostgreSQL</productname>  is  based  on
   <ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
    <productname>Postgres release 4.2</productname></ulink>. 
   The <productname>Postgres</productname> project, 
   led by Professor Michael Stonebraker, was sponsored  by  the
   Defense  Advanced Research Projects Agency
   (<acronym>DARPA</acronym>), the
   Army Research Office (<acronym>ARO</acronym>), the National Science  
   Foundation (<acronym>NSF</acronym>), and ESL, Inc.
  </para>
d25 5
a29 2
  <sect1 id="intro-whatis">
   <title> What is <productname>Postgres</productname>?</title>
d32 3
d36 1
a36 1
    (DBMSs) support a data model consisting of a collection
d44 1
a44 1
    models  in  part  because  of its "Spartan simplicity".
d48 2
a49 2
    power  by  incorporating  the following four additional
    basic concepts in such a way that  users  can  easily
a52 1
     <member>tables</member>
d54 1
a54 1
     <member>types</member>
a85 1
   &about;
a89 1
   &legal;
d91 1
a91 1
 </chapter>
@


1.12
log
@Add `id' attributes to all `chapter' and `sect1' tags, to generate useful
names for the HTML files (e.g., not x4856.htm).
@
text
@d2 1
a2 1
$Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.11 2000/04/07 13:30:58 thomas Exp $
d47 1
a47 1
     <member>classes</member>
@


1.11
log
@Fix path to initdb in installation instructions.
General cleanup for 7.0.
@
text
@d2 1
a2 1
$Header: /usr/local/cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.10 2000/03/31 03:27:40 thomas Exp $
d25 1
a25 1
  <sect1>
@


1.10
log
@Minor markup changes. Refer to (".../catalog") in the emacs hints.
@
text
@d2 1
a2 1
$Header$
d19 2
a20 1
   Defense  Advanced Research Projects Agency (<acronym>DARPA</acronym>), the
d41 1
a41 1
    <productname>Postgres</productname> offers  substantial  additional
d66 10
a75 7
    These features put <productname>Postgres</productname> into the category of databases
    referred to as <firstterm>object-relational</firstterm>. Note that this is distinct
    from those referred to as <firstterm>object-oriented</firstterm>, which in general
    are not as well suited to supporting the traditional relational database languages.
    So, although <productname>Postgres</productname> has some object-oriented features,
    it is firmly in the relational database world. In fact, some commercial databases
    have recently incorporated features pioneered by <productname>Postgres</productname>.
@


1.9
log
@Accumulated fixups.
Add some chapters on new topics.
Change to referencing OASIS/Docbook v3.1 rather than Davenport/Docbook v3.0
Grepped for and fixed apparent tag mangling from emacs
 "Normalize" operation. Should be the last of those.
@
text
@d1 4
d88 1
a88 1
mode: sgml
d98 1
a98 1
sgml-local-catalogs:"/usr/lib/sgml/CATALOG"
@


1.8
log
@Added bug reporting guidelines
Some corrections in installation procedure
@
text
@d76 1
a76 1
   &bug-reporting;
@


1.7
log
@Make sure that only one intro is included in the integrated doc.
Multiple intros cause trouble since they have some section elements
 (e.g. "y2k.sgml") in common leading to duplicate labels.
Include emacs formatting hints in the intro*.sgml sources.
@
text
@d76 1
@


1.6
log
@Clean up to ensure tag completion as required by the newest versions
 of Norm's Modular Style Sheets and jade/docbook.
From Vince Vielhaber <vev@@michvhf.com>.
@
text
@d1 2
a2 2
<Chapter Id="intro">
<TITLE>Introduction</TITLE>
d4 93
a96 81
<Para>
     This document is the user  manual  for  the  
     <Ulink url="http://postgresql.org/"><ProductName>PostgreSQL</ProductName></Ulink>
     database  management system, originally developed at the University
     of California at  Berkeley.   

<ProductName>PostgreSQL</ProductName>  is  based  on
     <Ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
     <ProductName>Postgres release 4.2</ProductName></Ulink>. 
The <ProductName>Postgres</ProductName> project, 
     led by Professor Michael Stonebraker, was sponsored  by  the
     Defense  Advanced Research Projects Agency (<Acronym>DARPA</Acronym>), the
     Army Research Office (<Acronym>ARO</Acronym>), the National Science  
     Foundation (<Acronym>NSF</Acronym>), and ESL, Inc.
</Para>

<Sect1>
<Title> What is <ProductName>Postgres</ProductName>?</Title>

<Para>
     Traditional   relational  database  management  systems
     (DBMSs) support a data model consisting of a collection
     of named relations, containing attributes of a specific
     type.  In current commercial  systems,  possible  types
     include  floating  point  numbers,  integers, character
     strings, money, and dates.  It is  commonly  recognized
     that  this model is inadequate for future data 
     processing applications.
     The relational  model  successfully  replaced  previous
     models  in  part  because  of its "Spartan simplicity".
     However, as mentioned, this simplicity often makes  the
     implementation  of  certain applications very difficult.
     <ProductName>Postgres</ProductName> offers  substantial  additional
     power  by  incorporating  the following four additional
     basic concepts in such a way that  users  can  easily
     extend the system:

<SimpleList>
<Member>classes</Member>
<Member>inheritance</Member>
<Member>types</Member>
<Member>functions</Member>
</SimpleList>
</Para>

<Para>
Other features provide additional power and flexibility:

<SimpleList>
<Member>constraints</Member>
<Member>triggers</Member>
<Member>rules</Member>
<Member>transaction integrity</Member>
</SimpleList>
</Para>

<Para>
These features put <ProductName>Postgres</ProductName> into the category of databases
referred to as <FirstTerm>object-relational</FirstTerm>. Note that this is distinct
from those referred to as <FirstTerm>object-oriented</FirstTerm>, which in general
are not as well suited to supporting the traditional relational database languages.
So, although <ProductName>Postgres</ProductName> has some object-oriented features,
it is firmly in the relational database world. In fact, some commercial databases
have recently incorporated features pioneered by <ProductName>Postgres</ProductName>.
</Para>

</Sect1>

&history;

&about;

&info;

&notation;

&y2k;

&legal;

</Chapter>
@


1.5
log
@Add Y2K statement for intros.
Make sure notation section is included in most intros.
@
text
@d68 1
@


1.4
log
@Clean up pages. Add information for operator precedence.
Split introduction sections into separate files to allow the legal notice
 and notation sections appear in all documents without having the history
 show up everplace too.
Add full list of reserved and non-reserved key words in syntax.sgml.
Add a separate chapter to the admin guide on security.
@
text
@d77 4
@


1.3
log
@Add port information for NS32532.
Fix Id tag in chapter headings to allow meaningful file names in html.
@
text
@d8 3
a10 1
     of California at  Berkeley.   <ProductName>PostgreSQL</ProductName>  is  based  on
d14 1
a14 1
     led by Professor Michael Stonebraker, has been sponsored  by  the
a69 233
     
<Sect1>
<Title>A Short History of <ProductName>Postgres</ProductName></Title>

<Sect2>
<Title>The Berkeley <ProductName>Postgres</ProductName> Project</Title>

<Para>
     Implementation of the <ProductName>Postgres</ProductName> <Acronym>DBMS</Acronym> began in 1986.  The
     initial  concepts  for  the  system  were  presented in
<!--
<XRef LinkEnd="STON86">
-->
<Citation>[STON86]</Citation>
 and the definition of the initial  data  model
     appeared in 
<!--
<XRef LinkEnd="ROWE87">.
-->
<Citation>[ROWE87]</Citation>.
The design of the rule system at
     that time was described in  
<!--
<XRef LinkEnd="STON87a">.
-->
<Citation>[STON87a]</Citation>.
The  rationale
     and  architecture  of the storage manager were detailed in 
<!--
<XRef LinkEnd="STON87b">.
-->
<Citation>[STON87b]</Citation>.
</Para>

<Para>
     <ProductName>Postgres</ProductName> has undergone  several  major  releases  since
     then.   The  first "demoware" system became operational
     in 1987 and was shown at the  1988  <Acronym>ACM-SIGMOD</Acronym>  
     Conference.   We  released Version 1, described in 
<!--
<XRef LinkEnd="STON90a">,
-->
<Citation>[STON90a]</Citation>,
     to a few external users in June 1989.  In response to a
     critique  of  the  first rule system 
<!--
(<XRef LinkEnd="STON89">), 
-->
(<Citation>[STON89]</Citation>),
the rule
     system was  redesigned 
<!--
(<XRef LinkEnd="STON90b">)
-->
(<Citation>[STON90b]</Citation>)
and  Version  2  was
     released  in  June 1990 with the new rule system.  
     Version 3 appeared in 1991 and added support for  multiple
     storage  managers,  an  improved  query executor, and a
     rewritten rewrite rule  system.   For  the  most  part,
     releases  since  then  have  focused on portability and
     reliability.
</Para>

<Para>
     <ProductName>Postgres</ProductName> has been  used  to  implement  many  different
     research and production applications.  These include: a
     financial data analysis system, a  jet  engine  
     performance   monitoring   package,   an   asteroid  tracking
     database, a medical information database,  and  several
     geographic information systems.  <ProductName>Postgres</ProductName> has also been
     used as an educational tool  at  several  universities.
     Finally,  <Ulink url="http://www.illustra.com/">Illustra  Information  Technologies</Ulink> picked up
     the code and commercialized it.
     <ProductName>Postgres</ProductName>  became  the  primary  data  manager  for  the
     <Ulink url="http://www.sdsc.edu/0/Parts_Collabs/S2K/s2k_home.html">Sequoia 2000</Ulink>
 scientific computing project in late 1992.
     Furthermore, the size of the  external  user  community
     nearly  doubled  during  1993.   It became increasingly
     obvious that maintenance of the prototype code and 
     support  was  taking  up large amounts of time that should
     have been devoted to database research.  In  an  effort
     to  reduce  this support burden, the project officially
     ended with Version 4.2.
</Para>
</Sect2>
     
<Sect2>
<Title><ProductName>Postgres95</ProductName></Title>

<Para>
In 1994,
<ULink url="mailto:ayu@@informix.com">Andrew Yu</ULink>
and
<ULink url="http://http.cs.berkeley.edu/~jolly/">Jolly Chen</ULink>
added a SQL language interpreter to <ProductName>Postgres</ProductName>, and the code was subsequently released to
the Web to find its own way in the world. <ProductName>Postgres95</ProductName> was a public-domain, open source descendant
of this original Berkeley code.
</Para>

<Para>
     <ProductName>Postgres95</ProductName> is a derivative of the last official release
     of  <ProductName>Postgres</ProductName>  (version 4.2). The code is now completely
     ANSI C and the code size has been trimmed by 25%. There
     are  a lot of internal changes that improve performance
     and code maintainability. <ProductName>Postgres95</ProductName> v1.0.x runs about  30-50%
     faster  on  the  Wisconsin  Benchmark compared to v4.2.
     Apart from bug fixes, these are the major enhancements:

<ItemizedList>
<ListItem>
<Para>
      	The query language <ProductName>Postquel</ProductName> has been replaced with
        	<Acronym>SQL</Acronym> (implemented in the server). We do  not yet support
        	subqueries  (which can be imitated with user defined
        	<Acronym>SQL</Acronym> functions). Aggregates  have  been
        	re-implemented.  We also added support for ``GROUP BY''.
        	The <FileName>libpq</FileName> interface is still available  for  <Acronym>C</Acronym>  
        	programs.
</Para>
</ListItem>
<ListItem>
<Para>
      	In addition to the monitor program, we provide a new
        	program (<Application>psql</Application>) which supports <Acronym>GNU</Acronym> <FileName>readline</FileName>.
</Para>
</ListItem>
<ListItem>
<Para>
      	We added a new  front-end  library,  <FileName>libpgtcl</FileName>,  that
        	supports  <Acronym>Tcl</Acronym>-based  clients.   A sample shell, 
        	pgtclsh, provides new Tcl  commands  to  interface  <Application>tcl</Application>
        	programs with the <ProductName>Postgres95</ProductName> backend.
</Para>
</ListItem>
<ListItem>
<Para>
      	The  large  object interface has been overhauled. We
        	kept Inversion large objects as the  only  mechanism
        	for  storing  large objects. (This is not to be 
        	confused with the Inversion file system which has  been
        	removed.)
</Para>
</ListItem>
<ListItem>
<Para>
      	The  instance-level  rule  system  has been removed.
        	Rules are still available as rewrite rules.
</Para>
</ListItem>
<ListItem>
<Para>
      	A short tutorial introducing regular <Acronym>SQL</Acronym> features as
        	well as those of ours is distributed with the source
        	code.
</Para>
</ListItem>
<ListItem>
<Para>
      	<Acronym>GNU</Acronym> make (instead of  <Acronym>BSD</Acronym>  make)  is  used  for  the
        	build.  Also,  <ProductName>Postgres95</ProductName>  can  be  compiled with an
        	unpatched <ProductName>gcc</ProductName> (data alignment of  doubles  has  been
        	fixed).
</Para>
</ListItem>
</ItemizedList>
</Para>
</Sect2>

<Sect2>
<Title><ProductName>PostgreSQL</ProductName></Title>

<Para>
By 1996, it became clear that the name <Quote>Postgres95</Quote> would not stand
the test of time. A new name, <ProductName>PostgreSQL</ProductName>, was chosen to reflect the
relationship between original <ProductName>Postgres</ProductName> and the more recent
versions with <Acronym>SQL</Acronym> capability. At the same time, the version numbering
was reset to start at 6.0, putting the numbers back into the sequence originally begun by
the <ProductName>Postgres</ProductName> Project.

<Para>
The emphasis on development for the v1.0.x releases of <ProductName>Postgres95</ProductName>
was on stabilizing the backend code.
With the v6.x series of <ProductName>PostgreSQL</ProductName>, the emphasis has shifted from
identifying and understanding existing problems in the backend to augmenting features and capabilities, although
work continues in all areas.

<Para>
Major enhancements include:

<ItemizedList>
<ListItem>
<Para>
Important backend features, including subselects, defaults, constraints, and triggers, have been implemented.
</Para>
</ListItem>
<ListItem>
<Para>
Additional <Acronym>SQL92</Acronym>-compliant language features have been added,
 including primary keys, quoted identifiers, literal string type coersion, type casting,
 and binary and hexadecimal integer input.
</Para>
</ListItem>
<ListItem>
<Para>
Built-in types have been improved, including new wide-range date/time types and additional geometric type support.
</Para>
</ListItem>
<ListItem>
<Para>
Overall backend code speed has been increased by approximately 20%, and backend startup time has decreased 80%.
</Para>
</ListItem>
</ItemizedList>
</Para>
</Sect2>

<Sect1>
<Title>About This Release</Title>

<Para>
     From  now  on, We will use <ProductName>Postgres</ProductName> to mean <ProductName>PostgreSQL</ProductName>.

<Para>
     <ProductName>PostgreSQL</ProductName>  is  available  without cost. This manual
     describes version 6.3 of <ProductName>PostgreSQL</ProductName>.

<Para>
Check the Administrator's Guide for a list of currently supported machines. In general,
<ProductName>PostgreSQL</ProductName> is portable to any Unix/Posix-compatible system
with full libc library support.

</Sect1>
d71 1
a71 2
<Sect1>
<Title>Resources</Title>
d73 1
a73 2
<Para>
This manual set is organized into several parts:
d75 1
a75 9
<VariableList>
<VarListEntry>
<Term>Tutorial</Term>
<ListItem>
<Para>
An introduction for new users. Does not cover advanced features.
</Para>
</ListItem>
</VarListEntry>
d77 1
a77 163
<VarListEntry>
<Term>User's Guide</Term>
<ListItem>
<Para>
General information for users, including available commands and data types.
</Para>
</ListItem>
</VarListEntry>

<VarListEntry>
<Term>Programmer's Guide</Term>
<ListItem>
<Para>
Advanced information for application programmers. Topics include
type and function extensibility, library interfaces, and application design issues.
</Para>
</ListItem>
</VarListEntry>

<VarListEntry>
<Term>Administrator's Guide</Term>
<ListItem>
<Para>
Installation and management information. List of supported machines.
</Para>
</ListItem>
</VarListEntry>

<VarListEntry>
<Term>Developer's Guide</Term>
<ListItem>
<Para>
Information for <ProductName>Postgres</ProductName> developers. This is intended
for those who are contributing to the <ProductName>Postgres</ProductName>
project; application development information should appear in the Programmer's Guide.
</Para>
</ListItem>
</VarListEntry>

<VarListEntry>
<Term>Reference Manual</Term>
<ListItem>
<Para>
Detailed reference information on command syntax.
At the moment, this manual is very sparse, but eventually should contain
information similar to that in the man pages.
</Para>
</ListItem>
</VarListEntry>
</VariableList>

<Para>
In addition to this manual set, there are other resources to help you with
<ProductName>Postgres</ProductName> installation and use:

<VariableList>
<VarListEntry>
<Term>man pages</Term>
<ListItem>
<Para>
The man pages have general information on command syntax.
</Para>
</ListItem>
</VarListEntry>

<VarListEntry>
<Term>FAQs</Term>
<ListItem>
<Para>
The Frequently Asked Questions (FAQ) documents address both general issues
and some platform-specific issues.
</Para>
</ListItem>
</VarListEntry>

<VarListEntry>
<Term>READMEs</Term>
<ListItem>
<Para>
README files are available for some contributed packages.
</Para>
</ListItem>
</VarListEntry>

<VarListEntry>
<Term>Web Site</Term>
<ListItem>
<Para>
The <ULink url="postgresql.org"><ProductName>Postgres</ProductName></ULink> web site has some information
not appearing in the distribution. There is a <ProductName>mhonarc</ProductName> catalog of mailing list traffic
which is a rich resource for many topics.
</Para>
</ListItem>
</VarListEntry>

<VarListEntry>
<Term>Mailing Lists</Term>
<ListItem>
<Para>
The <ULink url="mailto:questions@@postgresql.org"><ProductName>Postgres</ProductName> Questions</ULink>
mailing list is a good place to have user questions answered. Other mailing lists are available; consult
the web page for details.
</Para>
</ListItem>
</VarListEntry>

<VarListEntry>
<Term>Yourself!</Term>
<ListItem>
<Para>
<ProductName>Postgres</ProductName> is an open source product. As such, it depends on the user community for
ongoing support. As you begin to use <ProductName>Postgres</ProductName>, you will rely on others
for help, either through the documentation or through the mailing lists. Consider contributing your
knowledge back. If you learn something which is not in the documentation, write it up and contribute it.
If you add features to the code, contribute it. Even those without a lot of experience can provide
corrections and minor changes in the documentation, and that is a good way to start.
The <ULink url="mailto:docs@@postgresql.org"><ProductName>Postgres</ProductName> Documentation</ULink>
mailing list is the place to get going.
</Para>
</ListItem>
</VarListEntry>
</VariableList>

</Sect1>

<Sect1>
<Title>Copyrights and Trademarks</Title>

<Para>
<ProductName>PostgreSQL</ProductName> is copyright (C) 1996-8 by the PostgreSQL Global Development Group,
and is distributed under the terms of the Berkeley license.

<Para>
<ProductName>Postgres95</ProductName> is copyright (C) 1994-5 by the Regents of the University of California.
Permission to use, copy, modify, and distribute this software and its documentation
for any purpose, without fee, and without a written agreement is hereby granted,
provided that the above copyright notice and this paragraph and the following two
paragraphs appear in all copies.
</Para>
<Para>
In no event shall the University of California be liable to
any party for direct, indirect, special, incidental, or consequential
damages, including lost profits, arising out of the use of this
software and its documentation, even if the University of California
has been advised of the possibility of such damage.
</Para>
<Para>
The University of California specifically disclaims any
warranties, including, but not limited to, the implied warranties
of merchantability and fitness for a particular purpose.
The software provided hereunder is on an "as-is" basis, and
the University of California has no obligations to provide
maintainance, support, updates, enhancements, or modifications.
</Para>

<Para>
<Acronym>UNIX</Acronym> is a trademark of X/Open, Ltd.  Sun4,  SPARC,  SunOS
and  Solaris  are trademarks of Sun Microsystems, Inc.  DEC,
DECstation, Alpha AXP and ULTRIX are trademarks  of  Digital
Equipment   Corp.   PA-RISC  and  HP-UX  are  trademarks  of
Hewlett-Packard Co.  OSF/1 is a trademark of the Open  
Software Foundation.
</Para>
@


1.2
log
@Fix some typos.
@
text
@d1 1
a1 1
<Chapter>
@


1.1
log
@SGML source for new documentation.
@
text
@d278 1
a278 1
Overall backend code speed has been increased by approximately 20%, and backend startup speed has decreased 80%.
@
