Skip to content

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

Include mention of CASE, COALESCE, and IFNULL. 

Add date/time parsing procedure (perhaps should be in appendix).
Add time zone information (ditto).
Update keyword list.
parent 5dd715b5
Expand all Show whitespace changes
Inline Side-by-side
Showing with 1785 additions and 1689 deletions
doc/src/sgml/admin.sgml
View file @ 95e3cec6
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.11 1999/05/04 02:16:57 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.12 1999/05/12 07:32:42 thomas Exp $
Postgres Administrator's Guide. Postgres Administrator's Guide.
Derived from postgres.sgml. Derived from postgres.sgml.
- thomas 1998-10-27 - thomas 1998-10-27
$Log: admin.sgml,v $ $Log: admin.sgml,v $
Revision 1.11 1999/05/04 02:16:57 thomas Revision 1.12 1999/05/12 07:32:42 thomas
Include chapter on security. Include mention of CASE, COALESCE, and IFNULL.
Add date/time parsing procedure (perhaps should be in appendix).
Add time zone information (ditto).
Update keyword list.
Revision 1.10 1999/01/19 16:06:25 thomas Revision 1.10 1999/01/19 16:06:25 thomas
Merge current.sgml into release.sgml so all release notes are in the same Merge current.sgml into release.sgml so all release notes are in the same
...@@ -59,8 +62,8 @@ Bigger updates to the installation instructions (install and config). ...@@ -59,8 +62,8 @@ Bigger updates to the installation instructions (install and config).
<!-- Title information --> <!-- Title information -->
<Title>PostgreSQL Administrator's Guide</Title> <Title>PostgreSQL Administrator's Guide</Title>
<BookInfo> <BookInfo>
<ReleaseInfo>Covering v6.4 for general release</ReleaseInfo> <ReleaseInfo>Covering v6.4 for general release</ReleaseInfo>
<BookBiblio> <BookBiblio>
<AuthorGroup> <AuthorGroup>
...@@ -84,17 +87,17 @@ Bigger updates to the installation instructions (install and config). ...@@ -84,17 +87,17 @@ Bigger updates to the installation instructions (install and config).
<AuthorInitials>TGL</AuthorInitials> <AuthorInitials>TGL</AuthorInitials>
--> -->
<Date>(last updated 1998-10-27)</Date> <Date>(last updated 1999-04-08)</Date>
</BookBiblio> </BookBiblio>
<LegalNotice> <LegalNotice>
<Para> <Para>
<ProductName>PostgreSQL</ProductName> is copyright (C) 1998 <ProductName>PostgreSQL</ProductName> is copyright (C) 1998-9
by the Postgres Global Development Group. by the Postgres Global Development Group.
</Para> </Para>
</LegalNotice> </LegalNotice>
</BookInfo> </BookInfo>
<!-- <!--
<TOC> </TOC> <TOC> </TOC>
...@@ -109,36 +112,36 @@ Your name here... ...@@ -109,36 +112,36 @@ Your name here...
</Dedication> </Dedication>
--> -->
<Preface id="preface"> <Preface id="preface">
<Title>Summary</Title> <Title>Summary</Title>
<Para> <Para>
<ProductName>Postgres</ProductName>, <ProductName>Postgres</ProductName>,
developed originally in the UC Berkeley Computer Science Department, developed originally in the UC Berkeley Computer Science Department,
pioneered many of the object-relational concepts pioneered many of the object-relational concepts
now becoming available in some commercial databases. now becoming available in some commercial databases.
It provides SQL92/SQL3 language support, It provides SQL92/SQL3 language support,
transaction integrity, and type extensibility. transaction integrity, and type extensibility.
<ProductName>PostgreSQL</ProductName> is a public-domain, open source descendant <ProductName>PostgreSQL</ProductName> is a public-domain, open source descendant
of this original Berkeley code. of this original Berkeley code.
</Para> </Para>
</Preface> </Preface>
&intro-ag; &intro-ag;
&ports; &ports;
&config; &config;
&install; &install;
&installw; &installw;
&runtime; &runtime;
&security; &security;
&options; &options;
&start-ag; &start-ag;
&recovery; &recovery;
&regress; &regress;
&release; &release;
&biblio; &biblio;
<!-- <!--
Don't bother with an index until we get some index entries. Don't bother with an index until we get some index entries.
......
doc/src/sgml/biblio.sgml
View file @ 95e3cec6
...@@ -2,7 +2,8 @@ ...@@ -2,7 +2,8 @@
<title>Bibliography</title> <title>Bibliography</title>
<para> <para>
Selected references and readings for <acronym>SQL</acronym> and <productname>Postgres</productname>. Selected references and readings for <acronym>SQL</acronym>
and <productname>Postgres</productname>.
</para> </para>
<bibliodiv> <bibliodiv>
......
doc/src/sgml/datatype.sgml
View file @ 95e3cec6
<chapter id="datatype"> <chapter id="datatype">
<title>Data Types</title> <title>Data Types</title>
<abstract> <abstract>
<para> <para>
Describes the built-in data types available in Describes the built-in data types available in
<productname>Postgres</productname>. <productname>Postgres</productname>.
</para> </para>
</abstract> </abstract>
<para> <para>
<productname>Postgres</productname> has a rich set of native data <productname>Postgres</productname> has a rich set of native data
types available to users. types available to users.
Users may add new types to <productname>Postgres</productname> using the Users may add new types to <productname>Postgres</productname> using the
<command>DEFINE TYPE</command> <command>DEFINE TYPE</command>
command described elsewhere. command described elsewhere.
</para> </para>
<para> <para>
In the context of data types, the following sections will discuss In the context of data types, the following sections will discuss
<acronym>SQL</acronym> standards compliance, porting issues, and usage. <acronym>SQL</acronym> standards compliance, porting issues, and usage.
Some <productname>Postgres</productname> types correspond directly to Some <productname>Postgres</productname> types correspond directly to
<acronym>SQL92</acronym>-compatible types. In other <acronym>SQL92</acronym>-compatible types. In other
cases, data types defined by <acronym>SQL92</acronym> syntax are mapped directly cases, data types defined by <acronym>SQL92</acronym> syntax are mapped directly
into native <productname>Postgres</productname> types. into native <productname>Postgres</productname> types.
Many of the built-in types have obvious external formats. However, several Many of the built-in types have obvious external formats. However, several
types are either unique to <productname>Postgres</productname>, types are either unique to <productname>Postgres</productname>,
such as open and closed paths, or have such as open and closed paths, or have
several possibilities for formats, such as the date and time types. several possibilities for formats, such as the date and time types.
</para> </para>
<para> <para>
<table tocentry="1"> <table tocentry="1">
<title><productname>Postgres</productname> Data Types</title> <title><productname>Postgres</productname> Data Types</title>
<titleabbrev>Data Types</titleabbrev> <titleabbrev>Data Types</titleabbrev>
<tgroup cols="3"> <tgroup cols="3">
<thead> <thead>
<row> <row>
<entry><productname>Postgres</productname> Type</entry> <entry><productname>Postgres</productname> Type</entry>
<entry><acronym>SQL92</acronym> or <acronym>SQL3</acronym> Type</entry> <entry><acronym>SQL92</acronym> or <acronym>SQL3</acronym> Type</entry>
<entry>Description</entry> <entry>Description</entry>
</row> </row>
</thead> </thead>
<tbody> <tbody>
<row> <row>
<entry>bool</entry> <entry>bool</entry>
<entry>boolean</entry> <entry>boolean</entry>
...@@ -169,32 +169,32 @@ several possibilities for formats, such as the date and time types. ...@@ -169,32 +169,32 @@ several possibilities for formats, such as the date and time types.
<entry>character varying(n)</entry> <entry>character varying(n)</entry>
<entry>variable-length character string</entry> <entry>variable-length character string</entry>
</row> </row>
</tbody> </tbody>
</tgroup> </tgroup>
</table> </table>
</para> </para>
<para> <para>
<note> <note>
<para> <para>
The <type>cidr</type> and <type>inet</type> types are designed to handle any IP type The <type>cidr</type> and <type>inet</type> types are designed to handle any IP type
but only ipv4 is handled in the current implementation. but only ipv4 is handled in the current implementation.
Everything here that talks about ipv4 will apply to ipv6 in a future release.</para> Everything here that talks about ipv4 will apply to ipv6 in a future release.</para>
</note></para> </note></para>
<para> <para>
<table tocentry="1"> <table tocentry="1">
<title><productname>Postgres</productname> Function Constants</title> <title><productname>Postgres</productname> Function Constants</title>
<titleabbrev>Constants</titleabbrev> <titleabbrev>Constants</titleabbrev>
<tgroup cols="3"> <tgroup cols="3">
<thead> <thead>
<row> <row>
<entry><productname>Postgres</productname> Function</entry> <entry><productname>Postgres</productname> Function</entry>
<entry><acronym>SQL92</acronym> Constant</entry> <entry><acronym>SQL92</acronym> Constant</entry>
<entry>Description</entry> <entry>Description</entry>
</row> </row>
</thead> </thead>
<tbody> <tbody>
<row> <row>
<entry>getpgusername()</entry> <entry>getpgusername()</entry>
<entry>current_user</entry> <entry>current_user</entry>
...@@ -215,57 +215,57 @@ Everything here that talks about ipv4 will apply to ipv6 in a future release.</p ...@@ -215,57 +215,57 @@ Everything here that talks about ipv4 will apply to ipv6 in a future release.</p
<entry>current_timestamp</entry> <entry>current_timestamp</entry>
<entry>date and time of current transaction</entry> <entry>date and time of current transaction</entry>
</row> </row>
</tbody> </tbody>
</tgroup> </tgroup>
</table> </table>
</para> </para>
<para> <para>
<productname>Postgres</productname> has features at the forefront of <productname>Postgres</productname> has features at the forefront of
<acronym>ORDBMS</acronym> development. In addition to <acronym>ORDBMS</acronym> development. In addition to
<acronym>SQL3</acronym> conformance, substantial portions <acronym>SQL3</acronym> conformance, substantial portions
of <acronym>SQL92</acronym> are also supported. of <acronym>SQL92</acronym> are also supported.
Although we strive for <acronym>SQL92</acronym> compliance, Although we strive for <acronym>SQL92</acronym> compliance,
there are some aspects of the standard there are some aspects of the standard
which are ill considered and which should not live through subsequent standards. which are ill considered and which should not live through subsequent standards.
<productname>Postgres</productname> will not make great efforts to <productname>Postgres</productname> will not make great efforts to
conform to these features; however, these tend to apply in little-used conform to these features; however, these tend to apply in little-used
or obsure cases, and a typical user is not likely to run into them.</para> or obsure cases, and a typical user is not likely to run into them.</para>
<para> <para>
Most of the input and output functions corresponding to the Most of the input and output functions corresponding to the
base types (e.g., integers and floating point numbers) do some base types (e.g., integers and floating point numbers) do some
error-checking. error-checking.
Some of the operators and functions (e.g., Some of the operators and functions (e.g.,
addition and multiplication) do not perform run-time error-checking in the addition and multiplication) do not perform run-time error-checking in the
interests of improving execution speed. interests of improving execution speed.
On some systems, for example, the numeric operators for some data types may On some systems, for example, the numeric operators for some data types may
silently underflow or overflow. silently underflow or overflow.
</para> </para>
<para> <para>
Note that some of the input and output functions are not invertible. That is, Note that some of the input and output functions are not invertible. That is,
the result of an output function may lose precision when compared to the result of an output function may lose precision when compared to
the original input. the original input.
<note> <note>
<para> <para>
The original <productname>Postgres</productname> v4.2 code received from The original <productname>Postgres</productname> v4.2 code received from
Berkeley rounded all double precision floating point results to six digits for Berkeley rounded all double precision floating point results to six digits for
output. Starting with v6.1, floating point numbers are allowed to retain output. Starting with v6.1, floating point numbers are allowed to retain
most of the intrinsic precision of the type (typically 15 digits for doubles, most of the intrinsic precision of the type (typically 15 digits for doubles,
6 digits for 4-byte floats). 6 digits for 4-byte floats).
Other types with underlying floating point fields (e.g. geometric Other types with underlying floating point fields (e.g. geometric
types) carry similar precision.</para> types) carry similar precision.</para>
</note> </note>
</para> </para>
<sect1> <sect1>
<title>Numeric Types</title> <title>Numeric Types</title>
<para> <para>
Numeric types consist of two- and four-byte integers and four- and eight-byte Numeric types consist of two- and four-byte integers and four- and eight-byte
floating point numbers.</para> floating point numbers.</para>
<para> <para>
<table tocentry="1"> <table tocentry="1">
......
doc/src/sgml/func.sgml
View file @ 95e3cec6
This diff is collapsed.
doc/src/sgml/oper.sgml
View file @ 95e3cec6
This diff is collapsed.
doc/src/sgml/syntax.sgml
View file @ 95e3cec6
This diff is collapsed.
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