Skip to content

P
Postgres FD Implementation
Commit 8593e1ff authored by Thomas G. Lockhart's avatar Thomas G. Lockhart
Browse files
Options

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.
parent bbf37e94
Hide whitespace changes
Inline Side-by-side
Showing with 212 additions and 156 deletions
doc/src/sgml/intro-ag.sgml
View file @ 8593e1ff
<Chapter Id="intro-ag"> <chapter id="intro-ag">
<TITLE>Introduction</TITLE> <title>Introduction</title>
<Para> <para>
This document is the Administrator's Manual for the This document is the Administrator's Manual for the
<Ulink url="http://postgresql.org/"><ProductName>PostgreSQL</ProductName></Ulink> <ulink url="http://postgresql.org/"><productname>PostgreSQL</productname></ulink>
database management system, originally developed at the University database management system, originally developed at the University
of California at Berkeley. of California at Berkeley.
<ProductName>PostgreSQL</ProductName> is based on <productname>PostgreSQL</productname> is based on
<Ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html"> <ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
<ProductName>Postgres release 4.2</ProductName></Ulink>. <productname>Postgres release 4.2</productname></ulink>.
The <ProductName>Postgres</ProductName> project, The <productname>Postgres</productname> project,
led by Professor Michael Stonebraker, was sponsored by the led by Professor Michael Stonebraker, was sponsored by the
Defense Advanced Research Projects Agency (<Acronym>DARPA</Acronym>), the Defense Advanced Research Projects Agency (<acronym>DARPA</acronym>), the
Army Research Office (<Acronym>ARO</Acronym>), the National Science Army Research Office (<acronym>ARO</acronym>), the National Science
Foundation (<Acronym>NSF</Acronym>), and ESL, Inc. Foundation (<acronym>NSF</acronym>), and ESL, Inc.
</Para> </para>
&info; &info;
&notation;
&y2k;
&legal;
&notation; </chapter>
&y2k; <!-- Keep this comment at the end of the file
Local variables:
&legal; mode: sgml
sgml-omittag:nil
</Chapter> 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:
-->
doc/src/sgml/intro-pg.sgml
View file @ 8593e1ff
<Chapter Id="intro-pg"> <chapter id="intro-pg">
<TITLE>Introduction</TITLE> <title>Introduction</title>
<Para> <para>
This document is the programmer's manual for the This document is the programmer's manual for the
<Ulink url="http://postgresql.org/"><ProductName>PostgreSQL</ProductName></Ulink> <ulink url="http://postgresql.org/"><productname>PostgreSQL</productname></ulink>
database management system, originally developed at the University database management system, originally developed at the University
of California at Berkeley. of California at Berkeley.
<ProductName>PostgreSQL</ProductName> is based on <productname>PostgreSQL</productname> is based on
<Ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html"> <ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
<ProductName>Postgres release 4.2</ProductName></Ulink>. <productname>Postgres release 4.2</productname></ulink>.
The <ProductName>Postgres</ProductName> project, The <productname>Postgres</productname> project,
led by Professor Michael Stonebraker, has been sponsored by the led by Professor Michael Stonebraker, has been sponsored by the
Defense Advanced Research Projects Agency (<Acronym>DARPA</Acronym>), the Defense Advanced Research Projects Agency (<acronym>DARPA</acronym>), the
Army Research Office (<Acronym>ARO</Acronym>), the National Science Army Research Office (<acronym>ARO</acronym>), the National Science
Foundation (<Acronym>NSF</Acronym>), and ESL, Inc. Foundation (<acronym>NSF</acronym>), and ESL, Inc.
</Para> </para>
<Para> <para>
The first part of this manual The first part of this manual
explains the <ProductName>Postgres</ProductName> explains the <productname>Postgres</productname>
approach to extensibility and describe how approach to extensibility and describe how
users can extend <ProductName>Postgres</ProductName> users can extend <productname>Postgres</productname>
by adding user-defined types, by adding user-defined types,
operators, aggregates, and both query language and programming operators, aggregates, and both query language and programming
language functions. language functions.
After a discussion of the <ProductName>Postgres</ProductName> After a discussion of the <productname>Postgres</productname>
rule system, we discuss rule system, we discuss
the trigger and SPI interfaces. the trigger and SPI interfaces.
The manual concludes with a detailed description of The manual concludes with a detailed description of
the programming interfaces and the programming interfaces and
support libraries for various languages. support libraries for various languages.
</Para> </para>
<Para> <para>
We assume proficiency with UNIX and C programming. We assume proficiency with UNIX and C programming.
</Para> </para>
&info; &info;
&notation;
&notation; &y2k;
&legal;
&y2k;
</chapter>
&legal;
<!-- Keep this comment at the end of the file
</Chapter> 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:
-->
doc/src/sgml/intro.sgml
View file @ 8593e1ff
<Chapter Id="intro"> <chapter id="intro">
<TITLE>Introduction</TITLE> <title>Introduction</title>
<Para> <para>
This document is the user manual for the This document is the user manual for the
<Ulink url="http://postgresql.org/"><ProductName>PostgreSQL</ProductName></Ulink> <ulink url="http://postgresql.org/"><productname>PostgreSQL</productname></ulink>
database management system, originally developed at the University database management system, originally developed at the University
of California at Berkeley. of California at Berkeley.
<ProductName>PostgreSQL</ProductName> is based on <productname>PostgreSQL</productname> is based on
<Ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html"> <ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
<ProductName>Postgres release 4.2</ProductName></Ulink>. <productname>Postgres release 4.2</productname></ulink>.
The <ProductName>Postgres</ProductName> project, The <productname>Postgres</productname> project,
led by Professor Michael Stonebraker, was sponsored by the led by Professor Michael Stonebraker, was sponsored by the
Defense Advanced Research Projects Agency (<Acronym>DARPA</Acronym>), the Defense Advanced Research Projects Agency (<acronym>DARPA</acronym>), the
Army Research Office (<Acronym>ARO</Acronym>), the National Science Army Research Office (<acronym>ARO</acronym>), the National Science
Foundation (<Acronym>NSF</Acronym>), and ESL, Inc. Foundation (<acronym>NSF</acronym>), and ESL, Inc.
</Para> </para>
<Sect1> <sect1>
<Title> What is <ProductName>Postgres</ProductName>?</Title> <title> What is <productname>Postgres</productname>?</title>
<Para> <para>
Traditional relational database management systems Traditional relational database management systems
(DBMSs) support a data model consisting of a collection (DBMSs) support a data model consisting of a collection
of named relations, containing attributes of a specific of named relations, containing attributes of a specific
type. In current commercial systems, possible types type. In current commercial systems, possible types
include floating point numbers, integers, character include floating point numbers, integers, character
strings, money, and dates. It is commonly recognized strings, money, and dates. It is commonly recognized
that this model is inadequate for future data that this model is inadequate for future data
processing applications. processing applications.
The relational model successfully replaced previous The relational model successfully replaced previous
models in part because of its "Spartan simplicity". models in part because of its "Spartan simplicity".
However, as mentioned, this simplicity often makes the However, as mentioned, this simplicity often makes the
implementation of certain applications very difficult. implementation of certain applications very difficult.
<ProductName>Postgres</ProductName> offers substantial additional <productname>Postgres</productname> offers substantial additional
power by incorporating the following four additional power by incorporating the following four additional
basic concepts in such a way that users can easily basic concepts in such a way that users can easily
extend the system: extend the system:
<SimpleList> <simplelist>
<Member>classes</Member> <member>classes</member>
<Member>inheritance</Member> <member>inheritance</member>
<Member>types</Member> <member>types</member>
<Member>functions</Member> <member>functions</member>
</SimpleList> </simplelist>
</Para> </para>
<Para> <para>
Other features provide additional power and flexibility: Other features provide additional power and flexibility:
<SimpleList> <simplelist>
<Member>constraints</Member> <member>constraints</member>
<Member>triggers</Member> <member>triggers</member>
<Member>rules</Member> <member>rules</member>
<Member>transaction integrity</Member> <member>transaction integrity</member>
</SimpleList> </simplelist>
</Para> </para>
<Para> <para>
These features put <ProductName>Postgres</ProductName> into the category of databases These features put <productname>Postgres</productname> into the category of databases
referred to as <FirstTerm>object-relational</FirstTerm>. Note that this is distinct referred to as <firstterm>object-relational</firstterm>. Note that this is distinct
from those referred to as <FirstTerm>object-oriented</FirstTerm>, which in general from those referred to as <firstterm>object-oriented</firstterm>, which in general
are not as well suited to supporting the traditional relational database languages. are not as well suited to supporting the traditional relational database languages.
So, although <ProductName>Postgres</ProductName> has some object-oriented features, So, although <productname>Postgres</productname> has some object-oriented features,
it is firmly in the relational database world. In fact, some commercial databases it is firmly in the relational database world. In fact, some commercial databases
have recently incorporated features pioneered by <ProductName>Postgres</ProductName>. have recently incorporated features pioneered by <productname>Postgres</productname>.
</Para> </para>
</Sect1> </sect1>
&history; &history;
&about;
&about; &info;
&notation;
&info; &y2k;
&legal;
&notation;
</chapter>
&y2k;
<!-- Keep this comment at the end of the file
&legal; Local variables:
mode: sgml
</Chapter> 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:
-->
doc/src/sgml/postgres.sgml
View file @ 8593e1ff
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.25 1999/05/27 15:49:08 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.26 1999/06/01 17:26:18 thomas Exp $
Postgres integrated documentation. Postgres integrated documentation.
Other subset docs should be copied and shrunk from here. Other subset docs should be copied and shrunk from here.
thomas 1998-02-23 thomas 1998-02-23
$Log: postgres.sgml,v $ $Log: postgres.sgml,v $
Revision 1.26 1999/06/01 17:26:18 thomas
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.
Revision 1.25 1999/05/27 15:49:08 thomas Revision 1.25 1999/05/27 15:49:08 thomas
Markup fixes. Markup fixes.
Update for v6.5 release. Update for v6.5 release.
...@@ -293,7 +299,12 @@ Your name here... ...@@ -293,7 +299,12 @@ Your name here...
Installation and maintenance information. Installation and maintenance information.
</Para> </Para>
</PartIntro> </PartIntro>
<!--
Disable these extra intro chapters since some elements (e.g. y2k
statement) are included in the first intro.sgml and cause errors if
included twice.
&intro-ag; &intro-ag;
-->
&ports; &ports;
&config; &config;
&layout; &layout;
...@@ -315,7 +326,12 @@ Your name here... ...@@ -315,7 +326,12 @@ Your name here...
Information for extending <ProductName>Postgres</ProductName>. Information for extending <ProductName>Postgres</ProductName>.
</Para> </Para>
</PartIntro> </PartIntro>
<!--
Disable these extra intro chapters since some elements (e.g. y2k
statement) are included in the first intro.sgml and cause errors if
included twice.
&intro-pg; &intro-pg;
-->
&arch-pg; &arch-pg;
&extend; &extend;
&xfunc; &xfunc;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment