Make sure notation section is included in most intros.
Foundation (
NSF), and ESL, Inc.
+&info;
+
¬ation;
+&y2k;
+
&legal;
Introduction
- This document is the programmer's manual for the
- database management system, originally developed at the University
- of California at Berkeley.
+This document is the programmer's manual for the
+database management system, originally developed at the University
+of California at Berkeley.
- The first part of this manual
+The first part of this manual
approach to extensibility and describe how
-
users can extend
Postgres
+users can extend
Postgres
by adding user-defined types,
- operators, aggregates, and both query language and programming
+operators, aggregates, and both query language and programming
language functions.
- After an extremely brief
-
overview of the Postgres rule system, we discuss
- the trigger and SPI interfaces.
+ After a
discussion of the Postgres
+rule system, we discuss
+the trigger and SPI interfaces.
The manual concludes with a detailed description of
the programming interfaces and
support libraries for various languages.
We assume proficiency with UNIX and C programming.
+&info;
+
¬ation;
+&y2k;
+
&legal;
&info;
+¬ation;
+
+&y2k;
+
&legal;
The
is the user named postgres
-binaries and database files. As the database super-user, all
+binaries and database files. As the database superuser, all
protection mechanisms may be bypassed and any data accessed
arbitrarily.
-In addition, the
Postgres super
-user is allowed to execute
+In addition, the
Postgres superuser is allowed to execute
some support programs which are generally not available to all users.
-Note that the
Postgres super
-user is
+Note that the
Postgres superuser is
not
-the same as the Unix super-user (root),
-and should have a non-zero userid for security reasons.
+the same as the Unix superuser (which will be referred to as root).
+The superuser should have a non-zero user identifier (UID)
+for security reasons.
The
-database base administrator
+database administrator
or
DBA, is the person who is responsible for installing
Postgres with mechanisms to
enforce a security policy for a site. The DBA can add new users by
Notation
-...
at the front of a file name is used to represent the
-path to the
Postgres super-user's home directory.
-Anything in brackets
-[
and ]
) is optional. Anything in braces
-({
and }
) can be repeated 0 or more times.
-Parentheses ((
and )
) are used to group boolean
+...
or /usr/local/pgsql/
+at the front of a file name is used to represent the
+path to the
Postgres superuser's home directory.
+
+In a command synopsis, brackets
+[
and ]
) indicate an optional phrase or keyword.
+Anything in braces
+({
and }
) and containing vertical bars (|
)
+ indicates that you must choose one.
+
+In examples, parentheses ((
and )
) are used to group boolean
expressions. |
is the boolean operator OR.
-
\ No newline at end of file
+Examples will show commands executed from various accounts and programs.
+Commands executed from the root account will be preceeded with >
.
+Commands executed from the superuser account will be preceeded with $
.
+
SQL commands will be preceeded with
=>
+or will have no leading prompt.
+
+
+At the time of writing (
Postgres v6.4) the notation for
+flagging commands is not universally consistant throughout the documentation set.
+Please report problems to
+
the Documentation Mailing List.
+
+
+
&intro-ag;
&ports;
&install;
+&runtime;
&options;
&start-ag;
&recovery;
+
&xaggr;
&rules;
&xindex;
+&xplang;
&gist;
&dfunc;
&ecpg;
&odbc;
&jdbc;
-&xplang;
-&arch-dev;
+
+
&geqo;
&protocol;
&signals;
--- /dev/null
+
+
Y2K Statement
+
+
+
Author
+
+Written by
+on 1998-10-22.
+
+
+The
PostgreSQL Global Development Team provides
+the
Postgres software code tree as a public service,
+without warranty and without liability for it's behavior or performance.
+However, at the time of writing:
+
+
+
+The author of this statement, a volunteer on the
Postgres
+ support team since November, 1996, is not aware of
+any problems in the
Postgres code base related
+to time transitions around Jan 1, 2000 (Y2K).
+
+
+The author of this statement is not aware of any reports of Y2K problems
+uncovered in regression testing
+or in other field use of recent or current versions
+of
Postgres. We might have expected
+to hear about problems if they existed, given the installed base and
+the active participation of users on the support mailing lists.
+
+
+To the best of the author's knowledge, the
+assumptions Postgres makes about dates specified with a two-digit year
+are documented in the current
+ in the chapter on data types.
+For two-digit years, the significant transition year is 1970, not 2000;
+i.e. 70-01-01
is interpreted as 1970-01-01
,
+whereas 69-01-01
is interpreted as 2069-01-01
.
+
+
+Any Y2K problems in the underlying OS related to obtaining "the
+current time" may propagate into apparent Y2K problems in
+
+
+
+Refer to
+and
+for further discussion of Y2K issues, particularly
+ as it relates to open source, no fee software.
+
+
\ No newline at end of file