Skip to content

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

Add chapters on CVS access, MVCC, SQL theory to the docs. 

Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
 *except* for the porting list which will require a report
 from a successful installation to be updated.
parent 0807dbb2
Expand all Show whitespace changes
Inline Side-by-side
Showing with 778 additions and 1159 deletions
doc/src/sgml/admin.sgml
View file @ 9474dd7e
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.13 1999/05/20 05:39:25 thomas Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.14 1999/05/26 17:30:27 thomas Exp $
Postgres Administrator's Guide.
Derived from postgres.sgml.
- thomas 1998-10-27
$Log: admin.sgml,v $
Revision 1.14 1999/05/26 17:30:27 thomas
Add chapters on CVS access, MVCC, SQL theory to the docs.
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
*except* for the porting list which will require a report
from a successful installation to be updated.
Revision 1.13 1999/05/20 05:39:25 thomas
Rearrange and consolidate the Admin Guide.
Add reference pages for utilities and remove standalone chapters for same.
......@@ -73,7 +80,7 @@ Bigger updates to the installation instructions (install and config).
<Title>PostgreSQL Administrator's Guide</Title>
<BookInfo>
<ReleaseInfo>Covering v6.4 for general release</ReleaseInfo>
<ReleaseInfo>Covering v6.5 for general release</ReleaseInfo>
<BookBiblio>
<AuthorGroup>
<CorpAuthor>The PostgreSQL Development Team</CorpAuthor>
......@@ -96,12 +103,12 @@ Bigger updates to the installation instructions (install and config).
<AuthorInitials>TGL</AuthorInitials>
-->
<Date>(last updated 1999-05-19)</Date>
<Date>(last updated 1999-06-01)</Date>
</BookBiblio>
<LegalNotice>
<Para>
<ProductName>PostgreSQL</ProductName> is copyright (&copy;) 1998-9
<ProductName>PostgreSQL</ProductName> is &copy; 1998-9
by the Postgres Global Development Group.
</Para>
</LegalNotice>
......
doc/src/sgml/biblio.sgml
View file @ 9474dd7e
......@@ -98,6 +98,39 @@
<!--
<BIBLIOMISC>&dash;</BIBLIOMISC>
<BOOKBIBLIO ID="DATE94">
-->
<title id="DATE94-full">
An Introduction to Database Systems
</title>
<titleabbrev id="DATE94">
Date, 1994
</titleabbrev>
<edition>6</edition>
<authorgroup>
<author>
<firstname>C. J.</firstname>
<surname>Date</surname>
</author>
</authorgroup>
<volumenum>1</volumenum>
<pubdate>1994</pubdate>
<publisher>
<publishername>Addison-Wesley</publishername>
</publisher>
<copyright>
<year>1994</year>
<holder>Addison-Wesley Longman, Inc.</holder>
</copyright>
<!--
</BOOKBIBLIO>
-->
</biblioentry>
<biblioentry>
<!--
<BIBLIOMISC>&dash;</BIBLIOMISC>
<BOOKBIBLIO ID="MELT93">
-->
<title id="MELT93-full">
......@@ -135,6 +168,38 @@
-->
</biblioentry>
<biblioentry>
<!--
<BIBLIOMISC>&dash;</BIBLIOMISC>
<BOOKBIBLIO ID="ULL88">
-->
<title id="ULL88-full">
Principles of Database and Knowledge
</title>
<subtitle>
Base Systems
</subtitle>
<titleabbrev id="ULL88">
Ullman, 1988
</titleabbrev>
<authorgroup>
<author>
<firstname>Jeffrey D.</firstname>
<surname>Ullman</surname>
</author>
</authorgroup>
<volumenum>1</volumenum>
<publisher>
<publishername>
Computer Science Press
</publishername>
</publisher>
<pubdate>
1988
</pubdate>
</biblioentry>
</bibliodiv>
<bibliodiv>
......
doc/src/sgml/cvs.sgml
View file @ 9474dd7e
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.5 1999/05/22 02:27:23 thomas Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.6 1999/05/26 17:30:28 thomas Exp $
CVS code repository
Thomas Lockhart
$Log: cvs.sgml,v $
Revision 1.6 1999/05/26 17:30:28 thomas
Add chapters on CVS access, MVCC, SQL theory to the docs.
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
*except* for the porting list which will require a report
from a successful installation to be updated.
Revision 1.5 1999/05/22 02:27:23 thomas
Finish initial markup of cvs.sgml, and include it in the programmer's guide
and the integrated doc. Clean up other markup.
......@@ -52,7 +59,7 @@ Not yet included in a document (should go in the developer's doc?).
</para>
<para>
At least two options,
At least two methods,
anonymous CVS and <productname>CVSup</productname>,
are available to pull the <productname>CVS</productname> code tree from the
<productname>Postgres</productname> server to your local machine.
......@@ -496,7 +503,7 @@ pgsql
<title><productname>CVSup</productname> Installation from Binaries</title>
<para>
You can instead use pre-built binaries
You can use pre-built binaries
if you have a platform for which binaries
are posted on
<ulink url="ftp://postgresql.org/pub">the <productname>Postgres</productname> ftp site</ulink>,
......@@ -517,7 +524,7 @@ pgsql
<para>
At the time of writing, binaries are available for
Alpha/Tru64, ix86/xBSD,
HPPA/HPUX-10.20, and MIPS/irix.
HPPA/HPUX-10.20, MIPS/irix,
ix86/linux-libc5, ix86/linux-glibc,
Sparc/Solaris, and Sparc/SunOS.
</para>
......@@ -540,7 +547,7 @@ pgsql
<step performance="optional">
<para>
If you have another platform, check for and download the appropriate binary from
<ulink url="ftp://postgresql.org/pub">the <productname>Postgres</productname> ftp site</ulink>,
<ulink url="ftp://postgresql.org/pub">the <productname>Postgres</productname> ftp site</ulink>.
</para>
</step>
</substeps>
......
doc/src/sgml/datatype.sgml
View file @ 9474dd7e
This diff is collapsed.
doc/src/sgml/datetime.sgml
View file @ 9474dd7e
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.2 1999/05/22 02:27:23 thomas Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.3 1999/05/26 17:30:28 thomas Exp $
Date/time details
$Log: datetime.sgml,v $
Revision 2.3 1999/05/26 17:30:28 thomas
Add chapters on CVS access, MVCC, SQL theory to the docs.
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
*except* for the porting list which will require a report
from a successful installation to be updated.
Revision 2.2 1999/05/22 02:27:23 thomas
Finish initial markup of cvs.sgml, and include it in the programmer's guide
and the integrated doc. Clean up other markup.
-->
<appendix label="UG1" id="datetime-append">
<title>Date/Time Support</title>
<appendix label="UG1" id="datetime-appendix">
<title id="datetime-appendix-title">Date/Time Support</title>
<sect1>
<title>Time Zones</title>
......
doc/src/sgml/installation.sgml
View file @ 9474dd7e
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.3 1998/11/02 15:53:02 thomas Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.4 1999/05/26 17:30:29 thomas Exp $
Postgres quick Installation Guide.
- thomas 1998-10-26
$Log: installation.sgml,v $
Revision 1.4 1999/05/26 17:30:29 thomas
Add chapters on CVS access, MVCC, SQL theory to the docs.
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
*except* for the porting list which will require a report
from a successful installation to be updated.
Revision 1.3 1998/11/02 15:53:02 thomas
Move configuration info to after installation procedure.
Include only the current release in the release notes section.
......@@ -50,7 +57,7 @@ First cut at standalone installation guide to replace INSTALL text source.
<Title>PostgreSQL Installation Guide</Title>
<BookInfo>
<ReleaseInfo>Covering v6.4 for general release</ReleaseInfo>
<ReleaseInfo>Covering v6.5 for general release</ReleaseInfo>
<BookBiblio>
<AuthorGroup>
<CorpAuthor>The PostgreSQL Development Team</CorpAuthor>
......@@ -73,12 +80,12 @@ First cut at standalone installation guide to replace INSTALL text source.
<AuthorInitials>TGL</AuthorInitials>
-->
<Date>(last updated 1998-02-23)</Date>
<Date>(last updated 1999-06-01)</Date>
</BookBiblio>
<LegalNotice>
<Para>
<ProductName>PostgreSQL</ProductName> is copyright (C) 1998
<ProductName>PostgreSQL</ProductName> is &copy; 1998-9
by the Postgres Global Development Group.
</Para>
</LegalNotice>
......
doc/src/sgml/ports.sgml
View file @ 9474dd7e
This diff is collapsed.
doc/src/sgml/postgres.sgml
View file @ 9474dd7e
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.23 1999/05/22 02:27:24 thomas Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.24 1999/05/26 17:30:29 thomas Exp $
Postgres integrated documentation.
Other subset docs should be copied and shrunk from here.
thomas 1998-02-23
$Log: postgres.sgml,v $
Revision 1.24 1999/05/26 17:30:29 thomas
Add chapters on CVS access, MVCC, SQL theory to the docs.
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
*except* for the porting list which will require a report
from a successful installation to be updated.
Revision 1.23 1999/05/22 02:27:24 thomas
Finish initial markup of cvs.sgml, and include it in the programmer's guide
and the integrated doc. Clean up other markup.
......@@ -100,6 +107,7 @@ Move SQL reference pages up into the User's Guide.
<!entity inherit SYSTEM "inherit.sgml">
<!entity keys SYSTEM "keys.sgml">
<!entity manage SYSTEM "manage.sgml">
<!entity mvcc SYSTEM "mvcc.sgml">
<!entity oper SYSTEM "oper.sgml">
<!entity pgaccess SYSTEM "pgaccess.sgml">
<!entity psql SYSTEM "psql.sgml">
......@@ -125,6 +133,7 @@ Move SQL reference pages up into the User's Guide.
<!entity release SYSTEM "release.sgml">
<!entity security SYSTEM "security.sgml">
<!entity start-ag SYSTEM "start-ag.sgml">
<!entity trouble SYSTEM "trouble.sgml">
<!-- programmer's guide -->
<!entity intro-pg SYSTEM "intro-pg.sgml">
......@@ -156,6 +165,7 @@ Move SQL reference pages up into the User's Guide.
<!entity bki SYSTEM "bki.sgml">
<!entity compiler SYSTEM "compiler.sgml">
<!entity contacts SYSTEM "contacts.sgml">
<!entity cvs SYSTEM "cvs.sgml">
<!entity docguide SYSTEM "docguide.sgml">
<!entity geqo SYSTEM "geqo.sgml">
<!entity options SYSTEM "pg_options.sgml">
......@@ -193,12 +203,12 @@ Move SQL reference pages up into the User's Guide.
<AuthorInitials>TGL</AuthorInitials>
-->
<Date>(last updated 1998-05-19)</Date>
<Date>(last updated 1999-06-01)</Date>
</BookBiblio>
<LegalNotice>
<Para>
<ProductName>PostgreSQL</ProductName> is copyright (C) 1998
<ProductName>PostgreSQL</ProductName> is &copy; 1998-9
by the Postgres Global Development Group.
</Para>
</LegalNotice>
......@@ -264,6 +274,7 @@ Your name here...
&keys;
&array;
&inherit;
&mvcc;
&environ;
&manage;
&storage;
......@@ -285,6 +296,7 @@ Your name here...
&runtime;
&security;
&start-ag;
&trouble;
&recovery;
&regress;
&release;
......@@ -356,7 +368,9 @@ Your name here...
Additional related information.
</Para>
</PartIntro>
&datetime;
&cvs;
&docguide;
<!--
&contacts;
......
doc/src/sgml/programmer.sgml
View file @ 9474dd7e
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/programmer.sgml,v 1.15 1999/05/22 02:27:24 thomas Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/programmer.sgml,v 1.16 1999/05/26 17:30:30 thomas Exp $
Postgres Programmer's Guide.
- thomas 1998-10-27
$Log: programmer.sgml,v $
Revision 1.16 1999/05/26 17:30:30 thomas
Add chapters on CVS access, MVCC, SQL theory to the docs.
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
*except* for the porting list which will require a report
from a successful installation to be updated.
Revision 1.15 1999/05/22 02:27:24 thomas
Finish initial markup of cvs.sgml, and include it in the programmer's guide
and the integrated doc. Clean up other markup.
......@@ -136,12 +143,12 @@ Bigger updates to the installation instructions (install and config).
<AuthorInitials>TGL</AuthorInitials>
-->
<Date>(last updated 1999-05-19)</Date>
<Date>(last updated 1999-06-01)</Date>
</BookBiblio>
<LegalNotice>
<Para>
<ProductName>PostgreSQL</ProductName> is copyright (&copy;) 1998-9
<ProductName>PostgreSQL</ProductName> is &copy; 1998-9
by the Postgres Global Development Group.
</Para>
</LegalNotice>
......
doc/src/sgml/reference.sgml
View file @ 9474dd7e
<!-- reference.sgml
$Header: /cvsroot/pgsql/doc/src/sgml/reference.sgml,v 1.5 1998/10/31 09:36:37 thomas Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/reference.sgml,v 1.6 1999/05/26 17:30:30 thomas Exp $
Postgres User's Reference documentation.
- thomas 1998-08-31
$Log: reference.sgml,v $
Revision 1.6 1999/05/26 17:30:30 thomas
Add chapters on CVS access, MVCC, SQL theory to the docs.
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
*except* for the porting list which will require a report
from a successful installation to be updated.
Revision 1.5 1998/10/31 09:36:37 thomas
Cleanup for v6.4 release.
Make new file current.sgml to hold release info for the current release.
......@@ -32,7 +39,7 @@ Bigger updates to the installation instructions (install and config).
<Title>PostgreSQL Reference Manual</Title>
<BookInfo>
<ReleaseInfo>Covering v6.4 for general release</ReleaseInfo>
<ReleaseInfo>Covering v6.5 for general release</ReleaseInfo>
<BookBiblio>
<AuthorGroup>
<Author>
......@@ -69,12 +76,12 @@ Bigger updates to the installation instructions (install and config).
</AuthorGroup>
-->
<Date>(last updated 1998-08-31)</Date>
<Date>(last updated 1999-06-01)</Date>
</BookBiblio>
<LegalNotice>
<Para>
<ProductName>PostgreSQL</ProductName> is copyright (C) 1998
<ProductName>PostgreSQL</ProductName> is &copy; 1998-9
by the Postgres Global Development Group.
</Para>
</LegalNotice>
......
doc/src/sgml/sql.sgml
View file @ 9474dd7e
This diff is collapsed.
doc/src/sgml/user.sgml
View file @ 9474dd7e
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/user.sgml,v 1.10 1999/05/22 02:27:25 thomas Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/user.sgml,v 1.11 1999/05/26 17:30:30 thomas Exp $
Postgres User's Manual.
Derived from postgres.sgml.
thomas 1998-02-24
$Log: user.sgml,v $
Revision 1.11 1999/05/26 17:30:30 thomas
Add chapters on CVS access, MVCC, SQL theory to the docs.
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
*except* for the porting list which will require a report
from a successful installation to be updated.
Revision 1.10 1999/05/22 02:27:25 thomas
Finish initial markup of cvs.sgml, and include it in the programmer's guide
and the integrated doc. Clean up other markup.
......@@ -60,6 +67,7 @@ Move SQL reference pages up into the User's Guide.
<!entity intro SYSTEM "intro.sgml">
<!entity keys SYSTEM "keys.sgml">
<!entity manage SYSTEM "manage.sgml">
<!entity mvcc SYSTEM "mvcc.sgml">
<!entity oper SYSTEM "oper.sgml">
<!entity sql SYSTEM "sql.sgml">
<!entity storage SYSTEM "storage.sgml">
......@@ -100,12 +108,12 @@ Move SQL reference pages up into the User's Guide.
<AuthorInitials>TGL</AuthorInitials>
-->
<Date>(last updated 1999-05-19)</Date>
<Date>(last updated 1999-06-01)</Date>
</BookBiblio>
<LegalNotice>
<Para>
<ProductName>PostgreSQL</ProductName> is copyright (&copy;) 1998-9
<ProductName>PostgreSQL</ProductName> is &copy; 1998-9
by the Postgres Global Development Group.
</Para>
</LegalNotice>
......@@ -150,11 +158,14 @@ Your name here...
&keys;
&array;
&inherit;
&mvcc;
&environ;
&manage;
&storage;
&commands;
<!-- appendices -->
&datetime;
<!--
&contacts;
......
doc/src/sgml/xoper.sgml
View file @ 9474dd7e
......@@ -91,7 +91,7 @@ SELECT (a + b) AS c FROM test_complex;
sure that they are right! Incorrect use of an optimization clause can
result in backend crashes, subtly wrong output, or other Bad Things.
You can always leave out an optimization clause if you are not sure
about it --- the only consequence is that queries might run slower than
about it; the only consequence is that queries might run slower than
they need to.
</para>
......@@ -128,8 +128,9 @@ SELECT (a + b) AS c FROM test_complex;
a little trickier: how can the first one to be defined refer to the
other one, which you haven't defined yet? There are two solutions
to this problem:
</para>
<itemizedlist>
<listitem>
<para>
One way is to omit the COMMUTATOR clause in the first operator that
you define, and then provide one in the second operator's definition.
......@@ -138,7 +139,9 @@ SELECT (a + b) AS c FROM test_complex;
automatically go back and fill in the missing COMMUTATOR clause in
the first definition.
</para>
</listitem>
<listitem>
<para>
The other, more straightforward way is just to include COMMUTATOR clauses
in both definitions. When <ProductName>Postgres</ProductName> processes
......@@ -155,7 +158,9 @@ SELECT (a + b) AS c FROM test_complex;
reliably in <ProductName>Postgres</ProductName> versions before 6.5,
but it is now the recommended way to do things.)
</para>
</listitem>
</itemizedlist>
</para>
</sect2>
<sect2>
......@@ -288,8 +293,8 @@ SELECT (a + b) AS c FROM test_complex;
<para>
The HASHES clause, if present, tells the system that it is OK to
use the hash join method for a join based on this operator. HASHES
only makes sense for binary operators that return boolean --- and
in practice, the operator had better be equality for some data type.
only makes sense for binary operators that return boolean, and
in practice the operator had better be equality for some data type.
</para>
<para>
......@@ -302,7 +307,7 @@ SELECT (a + b) AS c FROM test_complex;
</para>
<para>
In fact, logical equality is not good enough either --- the operator
In fact, logical equality is not good enough either; the operator
had better represent pure bitwise equality, because the hash function
will be computed on the memory representation of the values regardless
of what the bits mean. For example, equality of
......@@ -344,7 +349,7 @@ SELECT (a + b) AS c FROM test_complex;
<title>SORT1 and SORT2</title>
<para>
The SORT clauses, if present, tell the system that it is OK to use
The SORT clauses, if present, tell the system that it is permissible to use
the merge join method for a join based on the current operator.
Both must be specified if either is. The current operator must be
equality for some pair of data types, and the SORT1 and SORT2 clauses
......@@ -391,25 +396,30 @@ SELECT (a + b) AS c FROM test_complex;
mergejoinable. These restrictions are not currently checked by
CREATE OPERATOR, but a merge join may fail at runtime if any are
not true:
</para>
<itemizedlist>
<listitem>
<para>
The mergejoinable equality operator must have a commutator
(itself if the two data types are the same, or a related equality operator
if they are different).
</para>
</listitem>
<listitem>
<para>
There must be '<' and '>' ordering operators having the same left and
right input datatypes as the mergejoinable operator itself. These
operators <emphasis>must</emphasis> be named '<' and '>' --- you do
operators <emphasis>must</emphasis> be named '<' and '>'; you do
not have any choice in the matter, since there is no provision for
specifying them explicitly. Note that if the left and right data types
are different, neither of these operators is the same as either
SORT operator. But they had better order the data values compatibly
with the SORT operators, or mergejoin will fail to work.
</para>
</listitem>
</itemizedlist>
</para>
</sect2>
</sect1>
......
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