diff --git a/doc/src/sgml/Makefile b/doc/src/sgml/Makefile
index 8756602fac..4dadb039bd 100644
--- a/doc/src/sgml/Makefile
+++ b/doc/src/sgml/Makefile
@@ -8,7 +8,7 @@
#
#
# IDENTIFICATION
-# $Header: /cvsroot/pgsql/doc/src/sgml/Makefile,v 1.45 2001/11/18 20:35:02 petere Exp $
+# $Header: /cvsroot/pgsql/doc/src/sgml/Makefile,v 1.46 2001/12/08 03:24:21 thomas Exp $
#
#----------------------------------------------------------------------------
@@ -96,16 +96,27 @@ programmer.html: catalogs.gif connections.gif
postgres.html: catalogs.gif connections.gif
-COLLATEINDEX = $(PERL) $(DOCBOOKSTYLE)/bin/collateindex.pl -f -g -t 'Index'
+#COLLATEINDEX = $(PERL) $(DOCBOOKSTYLE)/bin/collateindex.pl -f -g -t 'Index'
+COLLATEINDEX = $(PERL) /usr/bin/collateindex.pl -f -g -t 'Index'
ifeq (,$(wildcard HTML.index))
bookindex.sgml:
+ifeq (,$(wildcard $(COLLATEINDEX)))
+ touch $@
+else
$(COLLATEINDEX) -o $@ -N
+endif
+
setindex.sgml:
+ifeq (,$(wildcard $(COLLATEINDEX)))
+ touch $@
+else
$(COLLATEINDEX) -x -o $@ -N
+endif
else
bookindex.sgml: HTML.index
$(COLLATEINDEX) -i 'bookindex' -o $@ $<
+
setindex.sgml: HTML.index
$(COLLATEINDEX) -i 'setindex' -x -o $@ $<
endif
diff --git a/doc/src/sgml/cvs.sgml b/doc/src/sgml/cvs.sgml
index ce7f4f2cbd..303a4b6962 100644
--- a/doc/src/sgml/cvs.sgml
+++ b/doc/src/sgml/cvs.sgml
@@ -1,5 +1,5 @@
@@ -409,12 +409,12 @@ $ cvsup -L 2 postgres.cvsup
# at the date specified below
#*default date=97.08.29.00.00.00
-# base directory points to where CVSup will store its 'bookmarks' file(s)
+# base directory where CVSup will store its 'bookmarks' file(s)
# will create subdirectory sup/
#*default base=/opt/postgres # /usr/local/pgsql
*default base=/home/cvs
-# prefix directory points to where CVSup will store the actual distribution(s)
+# prefix directory where CVSup will store the actual distribution(s)
*default prefix=/home/cvs
# complete distribution, including all below
@@ -444,10 +444,10 @@ pgsql
*default delete use-rel-suffix
*default tag=.
-# base directory points to where CVSup will store its 'bookmarks' file(s)
+# base directory where CVSup will store its 'bookmarks' file(s)
*default base=/usr/local/pgsql
-# prefix directory points to where CVSup will store the actual distribution(s)
+# prefix directory where CVSup will store the actual distribution(s)
*default prefix=/usr/local/pgsql
# complete distribution, including all below
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index d9a4b7450c..badfea023f 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -1,5 +1,5 @@
@@ -219,25 +219,25 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.77 2001/11/28 20:49:09 pe
- time [ without time zone ]
+ time [ (p) ] [ without time zone ]
time of day
- time with time zone
+ time [ (p) ] with time zone
timetz
time of day, including time zone
- timestamp without time zone
+ timestamp [ (p) ] without time zone
timestamp
date and time
- timestamp [ with time zone ]
+ timestamp [ (p) ] [ with time zone ]
timestamptz
date and time, including time zone
@@ -1274,7 +1274,7 @@ SELECT b, char_length(b) FROM test2;
- timestamp without time zone
+ timestamp [ (p) ] without time zone
both date and time
8 bytes
4713 BC
@@ -1282,7 +1282,7 @@ SELECT b, char_length(b) FROM test2;
1 microsecond / 14 digits
- timestamp [ with time zone ]
+ timestamp [ (p) ] [ with time zone ]
both date and time
8 bytes
4713 BC
@@ -1324,28 +1324,38 @@ SELECT b, char_length(b) FROM test2;
+
-
-
- Time zones, and time-zone conventions, are influenced by
- political conventions, not just physical effects. Time zones have
- become somewhat standardized during the 1900's, but continue to
- be prone to arbitrary changes with time.
- PostgreSQL uses your operating
- system's underlying features to provide time-zone
- support, and these systems usually contain information for only
- the time period 1902 through 2038 (corresponding to the full
- range of conventional Unix system time).
- timestamp with time zone will use time zone
- information only within that year range, and assumes that times
- are in UTC outside that range.
-
-
+
+ time and timestamp both accept an
+ option precision field p which
+ determines the number of digits retained beyond the seconds
+ decimal point. By default, there is no explicit bound on precision
+ and the actual precision is determined by the underlying double
+ precision floating point number used to store values in seconds
+ for interval and
+ since 2000-01-01 in the case of timestamp.
+
+
+
+ Time zones, and time-zone conventions, are influenced by
+ political decisions, not just physical effects. Time zones have
+ become somewhat standardized around the world during the 1900's,
+ but continue to
+ be prone to arbitrary changes.
+ PostgreSQL uses your operating
+ system's underlying features to provide time-zone
+ support, and these systems usually contain information for only
+ the time period 1902 through 2038 (corresponding to the full
+ range of conventional Unix system time).
+ timestamp with time zone will use time zone
+ information only within that year range, and assumes that times
+ are in UTC outside that range.
To ensure compatibility to earlier versions of PostgreSQL
- we also continue to provide datetime
+ we continue to provide datetime
(equivalent to timestamp) and
timespan (equivalent to interval),
however support for these is now restricted to having an
@@ -1384,11 +1394,16 @@ SELECT b, char_length(b) FROM test2;
Remember that any date or time input needs to be enclosed into
single quotes, like text strings. Refer to for more information.
- SQL requires the following syntax
+ SQL9x requires the following syntax
-type 'value'
+type [ (p) ] 'value'
- but PostgreSQL is more flexible.
+ where p is an integer specifying the
+ number of fractional digits in the seconds field, and is allowed
+ for time, timestamp, and interval types.
+ PostgreSQL is more flexible in
+ handling date/time than the
+ SQL standard requires.
@@ -1569,7 +1584,7 @@ SELECT b, char_length(b) FROM test2;
- time [ without time zone ]
+ time [ ( p ) ] [ without time zone ]
time
@@ -1581,8 +1596,10 @@ SELECT b, char_length(b) FROM test2;
- Per SQL99, this type can be referenced as time and
- as time without time zone.
+ Per SQL99, this type can be specified as time or
+ as time without time zone. The optional precision
+ p should be between 0 and 13, and
+ defaults to the precision of the input time literal.
@@ -1641,7 +1658,7 @@ SELECT b, char_length(b) FROM test2;
- time with time zone
+ time [ ( precision ) ] with time zone
time with time zone
@@ -1662,6 +1679,12 @@ SELECT b, char_length(b) FROM test2;
required by any application.
+
+ The optional precision
+ p should be between 0 and 13, and
+ defaults to the precision of the input time literal.
+
+
time with time zone accepts all input also legal
for the time type, appended with a legal time zone,
@@ -1705,7 +1728,7 @@ SELECT b, char_length(b) FROM test2;
- timestamp without time zone
+ timestamp [ (precision) ] without time zone
timestamp without time zone
@@ -1713,7 +1736,7 @@ SELECT b, char_length(b) FROM test2;
- Valid input for the timestamp without time zone
+ Valid input for the timestamp [ (p) ] without time zone
type consists of a concatenation
of a date and a time, followed by an optional AD or
BC, followed by an optional time zone. (See below.)
@@ -1733,6 +1756,12 @@ January 8 04:05:06 1999 PST
is supported.
+
+ The optional precision
+ p should be between 0 and 13, and
+ defaults to the precision of the input timestamp literal.
+
+
For timestamp without time zone, any explicit time
zone specified in the input is silently swallowed. That is, the
@@ -1742,7 +1771,7 @@ January 8 04:05:06 1999 PST
- timestamp with time zone
+ timestamp [ (precision) ] with time zone
timestamp
@@ -1768,6 +1797,12 @@ January 8 04:05:06 1999 PST
is supported.
+
+ The optional precision
+ p should be between 0 and 13, and
+ defaults to the precision of the input timestamp literal.
+
+
Time Zone Input
@@ -1852,7 +1887,9 @@ January 8 04:05:06 1999 PST
The following SQL-compatible functions can be
used as date or time
input for the corresponding data type: CURRENT_DATE,
- CURRENT_TIME, CURRENT_TIMESTAMP.
+ CURRENT_TIME,
+ CURRENT_TIMESTAMP. The latter two accept an
+ optional precision specification.
diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml
index 7b2bf52934..734ea73519 100644
--- a/doc/src/sgml/docguide.sgml
+++ b/doc/src/sgml/docguide.sgml
@@ -1,4 +1,4 @@
-
+
Documentation
@@ -682,7 +682,7 @@ gmake man
The hardcopy Postscript documentation is generated by converting the
SGML source code to RTF, then
- importing into ApplixWare-4.4.1.
+ importing into ApplixWare.
After a little cleanup (see the following
section) the output is printed
to a postscript file.
@@ -735,28 +735,35 @@ gmake man
Repair the RTF file to correctly specify all
- styles, in particular the default style. The field can be added
- using vi or the following small
- sed procedure:
+ styles, in particular the default style. If the document
+ contains REFENTRY sections, one must also
+ replace formatting hints which tie a
+ preceeding paragraph to the current
+ paragraph, and instead tie the current paragraph to the
+ following one. A utility, fixrtf is
+ available in
+ doc/src/sgml to accomplish these repairs:
-
-#!/bin/sh
-# fixrtf.sh
-# Utility to repair slight damage in RTF files generated by jade
-# Thomas Lockhart <lockhart@alumni.caltech.edu>
-#
-for i in $* ; do
- mv $i $i.orig
- cat $i.orig | sed 's#\\stylesheet#\\stylesheet{\\s0 Normal;}#' > $i
-done
+
+% cd doc/src/sgml
+% fixrtf tutorial.rtf
+
-exit
-
+ or
- where the script is adding {\s0 Normal;} as
+
+% cd doc/src/sgml
+% fixrtf --refentry reference.rtf
+
+
+
+
+ The script adds {\s0 Normal;} as
the zero-th style in the document. According to ApplixWare, the
RTF standard would prohibit adding an implicit zero-th style,
- though M$Word happens to handle this case.
+ though M$Word happens to handle this case. For repairing
+ REFENTRY sections, the script replaces
+ \keepn tags with \keep.
@@ -822,10 +829,10 @@ exit
TOC-Heading 1
- 0.6
+ 0.4
- 0.6
+ 0.4
@@ -834,10 +841,10 @@ exit
TOC-Heading 2
- 1.0
+ 0.8
- 1.0
+ 0.8
@@ -846,10 +853,10 @@ exit
TOC-Heading 3
- 1.4
+ 1.2
- 1.4
+ 1.2
@@ -905,6 +912,8 @@ exit
+
+
+
+
+ Delete the index section from the document if it is empty.
+
+
+
+
+
+ Regenerate and adjust the table of contents.
+
+
+
+
+
+ Select the ToC field.
+
+
+
+
+
+ Select
+ Tools->Book Building->Create Table of
+ Contents.
+
+
+
+
+
+ Unbind the ToC by selecting
+ Tools->Field Editing->Unprotect.
+
+
+
+
+
+ Delete the first line in the ToC, which is an entry for the
+ ToC itself.
+
+
+
+
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index 73ed0cd851..4316cea55c 100644
--- a/doc/src/sgml/installation.sgml
+++ b/doc/src/sgml/installation.sgml
@@ -1,4 +1,4 @@
-
+
PostgreSQL>]]>
@@ -1367,208 +1367,250 @@ gunzip -c user.ps.gz \
- AIX 4.3.3>
+ AIX>
RS6000>
- 7.1
- 2001-03-21, Gilles Darold (gilles@darold.net)
- see also doc/FAQ_AIX
+ 7.2
+ 2001-11-28,
+ Andreas Zeugswetter (ZeugswetterA@spardat.at)
+ 4.3; see also doc/FAQ_AIX
- BeOS 5.0.4>
- x86>
- 7.1
- 2001-02-26, Cyril Velter (cyril.velter@libertysurf.fr)
- requires new BONE networking stack
-
-
- BSD/OS 4.2>
+ BeOS>
x86>
7.2
- 2001-11-27, Bruce Momjian (pgman@candle.pha.pa.us)
-
+ 2001-11-29,
+ Cyril Velter (cyril.velter@libertysurf.fr)
+ 5.0.4
+
+
+ BSD/OS>
+ x86>
+ 7.2
+ 2001-11-27,
+ Bruce Momjian (pgman@candle.pha.pa.us)
+ 4.2
FreeBSD>
x86>
7.2
- 2001-11-14, Chris Kings-Lynne
- (chriskl@familyhealth.com.au)
+ 2001-11-14,
+ Chris Kings-Lynne (chriskl@familyhealth.com.au)
HP-UX>
PA-RISC>
7.2
- 2001-11-16, 10.20 Tom Lane (tgl@sss.pgh.pa.us),
- 2001-03-22, 11.00, 11i Giles Lean (giles@nemeton.com.au)
- 32- and 64-bit on 11.00; see also doc/FAQ_HPUX
+ 2001-11-29,
+ Joseph Conway (Joseph.Conway@home.com),
+ Tom Lane (tgl@sss.pgh.pa.us)
+ 11.00 and 10.20; see also doc/FAQ_HPUX
- IRIX 6.5.11>
+ IRIX>
MIPS>
- 7.1
- 2001-03-22, Robert Bruccoleri (bruc@acm.org)
- 32-bit compilation model
+ 7.2
+ 2001-11-28,
+ Luis Amigo (lamigo@atc.unican.es)
+ 6.5.13, MIPSPro 7.30
- Linux 2.2.18>
+ Linux>
Alpha>
7.2
- 2001-11-16, Tom Lane (tgl@sss.pgh.pa.us)
- Tested at SourceForge
+ 2001-11-16,
+ Tom Lane (tgl@sss.pgh.pa.us)
+ 2.2.18; tested at SourceForge
- Linux 2.2.x>
+ Linux>
armv4l>
7.1
- 2001-02-22, Mark Knox (segfault@hardline.org)
-
+ 2001-02-22,
+ Mark Knox (markk@pixin.net)
+ 2.2.x
- Linux 2.0.x>
+ Linux>
MIPS>
7.2
- 2001-11-15, Hisao Shibuya (shibuya@alpha.or.jp>)
- Cobalt Qube2>
+ 2001-11-15,
+ Hisao Shibuya (shibuya@alpha.or.jp>)
+ 2.0.x; Cobalt Qube2>
- Linux 2.2.18>
+ Linux>
PPC74xx>
7.2
- 2001-11-16, Tom Lane (tgl@sss.pgh.pa.us)
- Apple G3
+ 2001-11-16,
+ Tom Lane (tgl@sss.pgh.pa.us)
+ 2.2.18; Apple G3
Linux>
S/390>
7.1
- 2000-11-17, Neale Ferguson (Neale.Ferguson@softwareAG-usa.com)
+ 2000-11-17,
+ Neale Ferguson (Neale.Ferguson@softwareAG-usa.com)
- Linux 2.2.15>
+ Linux>
Sparc>
- 7.1
- 2001-01-30, Ryan Kirkpatrick (pgsql@rkirkpat.net)
-
+ 7.2
+ 2001-11-28,
+ Doug McNaught (doug@wireboard.com)
+ 2.2.19
Linux>
x86>
7.2
- 2001-11-15, Thomas Lockhart (lockhart@fourpalms.org)
+ 2001-11-15,
+ Thomas Lockhart (lockhart@fourpalms.org)
2.0.x, 2.2.x, 2.4.x
MacOS X>
PPC>
7.2
- 2001-11-16, Tom Lane (tgl@sss.pgh.pa.us)
- Darwin 10.1
+ 2001-11-28,
+ Gavin Sherry (swm@linuxworld.com.au)
+ Darwin 10.1.x
- NetBSD 1.5W>
+ NetBSD>
Alpha>
7.2
- 2001-11-20, Thomas Thai (tom@minnesota.com)
-
+ 2001-11-20,
+ Thomas Thai (tom@minnesota.com)
+ 1.5W
- NetBSD 1.5E>
+ NetBSD>
arm32>
7.1
- 2001-03-21, Patrick Welche (prlw1@cam.ac.uk)
-
+ 2001-03-21,
+ Patrick Welche (prlw1@cam.ac.uk)
+ 1.5E
NetBSD>
m68k>
7.0
- 2000-04-10, Henry B. Hotz (hotz@jpl.nasa.gov)
+ 2000-04-10,
+ Henry B. Hotz (hotz@jpl.nasa.gov)
Mac 8xx
NetBSD>
PPC>
- 7.1
- 2001-04-05, Henry B. Hotz (hotz@jpl.nasa.gov)
- Mac G4
+ 7.2
+ 2001-11-28,
+ Bill Studenmund (wrstuden@netbsd.org)
+ 1.5
NetBSD>
Sparc>
- 7.1
- 2000-04-05, Matthew Green (mrg@eterna.com.au)
+ 7.2
+ 2001-12-03,
+ Matthew Green (mrg@eterna.com.au)
32- and 64-bit builds
- NetBSD 1.5>
+ NetBSD>
VAX>
7.1
- 2001-03-30, Tom I. Helbekkmo (tih@kpnQwest.no)
-
+ 2001-03-30,
+ Tom I. Helbekkmo (tih@kpnQwest.no)
+ 1.5
- NetBSD 1.5>
+ NetBSD>
x86>
- 7.1
- 2001-03-23, Giles Lean (giles@nemeton.com.au)
-
+ 7.2
+ 2001-11-28,
+ Bill Studenmund (wrstuden@netbsd.org)
+ 1.5
- OpenBSD 2.8>
+ OpenBSD>
Sparc>
- 7.1
- 2001-03-23, Brandon Palmer (bpalmer@crimelabs.net)
-
+ 7.2
+ 2001-11-27,
+ Brandon Palmer (bpalmer@crimelabs.net)
+ OBSD-3.0
- OpenBSD 2.8>
+ OpenBSD>
x86>
- 7.1
- 2001-03-21, Brandon Palmer (bpalmer@crimelabs.net)
-
+ 7.2
+ 2001-11-26,
+ Brandon Palmer (bpalmer@crimelabs.net)
+ OBSD-3.0
- SCO UnixWare 7.1.1>
+ OpenUnix>
x86>
- 7.1
- 2001-03-19, Larry Rosenman (ler@lerctr.org)
- UDK FS compiler; see also doc/FAQ_SCO
+ 7.2
+ 2001-11-28,
+ OU-8 Larry Rosenman (ler@lerctr.org),
+ UW-7 Olivier Prenant (ohp@pyrenet.fr)
+ see also doc/FAQ_SCO
+
+ QNX 4.25>
+ x86>
+ 7.1
+ 2001-05-24,
+ Bernd Tegge (tegge@repas-aeg.de)
+
+ 7.2 w/patches on QNX 6; see also doc/FAQ_QNX4
+
Solaris>
Sparc>
7.2
- 2001-11-12, Andrew Sullivan (andrew@libertyrms.com)
+ 2001-11-12,
+ Andrew Sullivan (andrew@libertyrms.com)
2.6-8; see also doc/FAQ_Solaris
- Solaris 2.8>
+ Solaris>
x86>
- 7.1
- 2001-03-27, Mathijs Brands (mathijs@ilse.nl)
- see also doc/FAQ_Solaris
+ 7.2
+ 2001-11-28,
+ Martin Renters (martin@datafax.com)
+ 2.8; see also doc/FAQ_Solaris
+
- Tru64 UNIX>
+ Tru64>
Alpha>
- 7.1
- 2001-03-26, Adriaan Joubert (a.joubert@albourne.com)
- 4.0-5.0, cc> and gcc>
+ 7.2
+ 2001-11-26,
+ Alessio Bragadini (alessio@albourne.com)
+ 4.0g, with cc and gcc
- Windows NT/2000> with Cygwin>
+ Windows NT/2000>
x86>
7.1
- 2001-03-16, Jason Tishler (Jason.Tishler@dothill.com)
+ 2001-03-16,
+ Jason Tishler (jason@tishler.net)
with Cygwin tool set, see doc/FAQ_MSWIN
@@ -1607,6 +1649,8 @@ gunzip -c user.ps.gz \
1998-03-01, Brian E Gallew (geek+@cmu.edu)
6.4 probably OK
+
NextStep>
x86>
@@ -1621,13 +1666,6 @@ gunzip -c user.ps.gz \
1998-03-01, David Wetzel (dave@turbocat.de)
bit rot suspected
-
- QNX 4.25>
- x86>
- 7.0
- 2000-04-01, Dr. Andreas Kardos (kardos@repas-aeg.de)
- Spinlock code needs work. See also doc/FAQ_QNX4.
-
SCO OpenServer 5>
x86>
@@ -1661,7 +1699,7 @@ gunzip -c user.ps.gz \
VAX>
6.x
1998-03-01
- No recent reports. Obsolete?
+ No recent reports
Windows 9x, ME, NT, 2000> (native)
diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml
index 9fb542bf96..e1fbeeb3d5 100644
--- a/doc/src/sgml/syntax.sgml
+++ b/doc/src/sgml/syntax.sgml
@@ -1,5 +1,5 @@
@@ -265,7 +265,8 @@ SELECT 'foobar';
SELECT 'foo' 'bar';
- is not valid syntax.
+ is not valid syntax, and PostgreSQL is
+ consistant with SQL9x in this regard.
@@ -293,7 +294,7 @@ SELECT 'foo' 'bar';
Integer constants in SQL are sequences of decimal digits (0
- though 9) with no decimal point. The range of legal values
+ though 9) with no decimal point and no exponent. The range of legal values
depends on which integer data type is used, but the plain
integer type accepts values ranging from -2147483648
to +2147483647. (The optional plus or minus sign is actually a
@@ -318,25 +319,26 @@ SELECT 'foo' 'bar';
where digits is one or more decimal
digits. At least one digit must be before or after the decimal
- point, and after the e if you use that option.
+ point. At least one digit must follow the exponent delimiter
+ (e) if that field is present.
Thus, a floating point constant is distinguished from an integer
constant by the presence of either the decimal point or the
exponent clause (or both). There must not be a space or other
characters embedded in the constant.
-
-
- These are some examples of valid floating point constants:
-
+
+
+ These are some examples of valid floating point constants:
+
3.5
4.
.001
5e2
1.925e-3
-
-
-
+
+
+
Floating point constants are of type DOUBLE
@@ -344,12 +346,12 @@ SELECT 'foo' 'bar';
by using SQL string notation or
PostgreSQL type notation:
-
+
REAL '1.23' -- string style
-'1.23'::REAL -- Postgres (historical) style
-
-
-
+'1.23'::REAL -- PostgreSQL (historical) style
+
+
+
Constants of Other Types