mirror of https://github.com/postgres/postgres
Thomas G. Lockhart
27 years ago
parent
7d831b5379
commit
b805230906
@ -1,18 +1,37 @@ |
||||
<Sect1> |
||||
<Title>About This Release</Title> |
||||
<sect1 id="about"> |
||||
<title>About This Release</title> |
||||
|
||||
<Para> |
||||
<ProductName>PostgreSQL</ProductName> is available without cost. This manual |
||||
describes version 6.4 of <ProductName>PostgreSQL</ProductName>. |
||||
</Para> |
||||
<Para> |
||||
We will use <ProductName>Postgres</ProductName> |
||||
to mean the version distributed as <ProductName>PostgreSQL</ProductName>. |
||||
</Para> |
||||
<Para> |
||||
Check the Administrator's Guide for a list of currently supported machines. |
||||
In general, |
||||
<ProductName>Postgres</ProductName> is portable to any Unix/Posix-compatible system |
||||
with full libc library support. |
||||
</Para> |
||||
</Sect1> |
||||
<para> |
||||
<productname>PostgreSQL</productname> is available without cost. This manual |
||||
describes version 6.5 of <productname>PostgreSQL</productname>. |
||||
</para> |
||||
|
||||
<para> |
||||
We will use <productname>Postgres</productname> |
||||
to mean the version distributed as <productname>PostgreSQL</productname>. |
||||
</para> |
||||
|
||||
<para> |
||||
Check the Administrator's Guide for a list of currently supported machines. |
||||
In general, |
||||
<productname>Postgres</productname> is portable to any Unix/Posix-compatible system |
||||
with full libc library support. |
||||
</para> |
||||
</sect1> |
||||
|
||||
<!-- Keep this comment at the end of the file |
||||
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: |
||||
--> |
||||
|
||||
@ -1,110 +1,127 @@ |
||||
<sect1> |
||||
<title>Terminology</title> |
||||
<title>Terminology</title> |
||||
|
||||
<para> |
||||
In the following documentation, |
||||
<firstterm>site</firstterm> |
||||
may be interpreted as the host machine on which |
||||
<Productname>Postgres</Productname> is installed. |
||||
Since it is possible to install more than one set of |
||||
<Productname>Postgres</Productname> |
||||
databases on a single host, this term more precisely denotes any |
||||
particular set of installed |
||||
<Productname>Postgres</Productname> binaries and databases. |
||||
</para> |
||||
<para> |
||||
In the following documentation, |
||||
<firstterm>site</firstterm> |
||||
may be interpreted as the host machine on which |
||||
<Productname>Postgres</Productname> is installed. |
||||
Since it is possible to install more than one set of |
||||
<Productname>Postgres</Productname> |
||||
databases on a single host, this term more precisely denotes any |
||||
particular set of installed |
||||
<Productname>Postgres</Productname> binaries and databases. |
||||
</para> |
||||
|
||||
<para> |
||||
The |
||||
<Productname>Postgres</Productname> <firstterm>superuser</firstterm> |
||||
is the user named <replaceable>postgres</replaceable> |
||||
who owns the <Productname>Postgres</Productname> |
||||
binaries and database files. As the database superuser, all |
||||
protection mechanisms may be bypassed and any data accessed |
||||
arbitrarily. |
||||
In addition, the <Productname>Postgres</Productname> superuser is allowed to execute |
||||
some support programs which are generally not available to all users. |
||||
Note that the <Productname>Postgres</Productname> superuser is |
||||
<emphasis>not</emphasis> |
||||
the same as the Unix superuser (which will be referred to as <firstterm>root</firstterm>). |
||||
The superuser should have a non-zero user identifier (<firstterm>UID</firstterm>) |
||||
for security reasons. |
||||
</para> |
||||
<para> |
||||
The |
||||
<Productname>Postgres</Productname> <firstterm>superuser</firstterm> |
||||
is the user named <replaceable>postgres</replaceable> |
||||
who owns the <Productname>Postgres</Productname> |
||||
binaries and database files. As the database superuser, all |
||||
protection mechanisms may be bypassed and any data accessed |
||||
arbitrarily. |
||||
In addition, the <Productname>Postgres</Productname> superuser is allowed to execute |
||||
some support programs which are generally not available to all users. |
||||
Note that the <Productname>Postgres</Productname> superuser is |
||||
<emphasis>not</emphasis> |
||||
the same as the Unix superuser (which will be referred to as <firstterm>root</firstterm>). |
||||
The superuser should have a non-zero user identifier (<firstterm>UID</firstterm>) |
||||
for security reasons. |
||||
</para> |
||||
|
||||
<para> |
||||
The |
||||
<firstterm>database administrator</firstterm> |
||||
or <acronym>DBA</acronym>, is the person who is responsible for installing |
||||
<Productname>Postgres</Productname> with mechanisms to |
||||
enforce a security policy for a site. The DBA can add new users by |
||||
the method described below |
||||
and maintain a set of template databases for use by |
||||
<application>createdb</application>. |
||||
</para> |
||||
<para> |
||||
The |
||||
<firstterm>database administrator</firstterm> |
||||
or <acronym>DBA</acronym>, is the person who is responsible for installing |
||||
<Productname>Postgres</Productname> with mechanisms to |
||||
enforce a security policy for a site. The DBA can add new users by |
||||
the method described below |
||||
and maintain a set of template databases for use by |
||||
<application>createdb</application>. |
||||
</para> |
||||
|
||||
<para> |
||||
The <application>postmaster</application> |
||||
is the process that acts as a clearing-house for requests |
||||
to the <Productname>Postgres</Productname> system. |
||||
Frontend applications connect to the <application>postmaster</application>, |
||||
which keeps tracks of any system errors and communication between the |
||||
backend processes. The <application>postmaster</application> |
||||
can take several command-line arguments to tune its behavior. |
||||
However, supplying arguments is necessary only if you intend to run multiple |
||||
sites or a non-default site. |
||||
</para> |
||||
<para> |
||||
The <application>postmaster</application> |
||||
is the process that acts as a clearing-house for requests |
||||
to the <Productname>Postgres</Productname> system. |
||||
Frontend applications connect to the <application>postmaster</application>, |
||||
which keeps tracks of any system errors and communication between the |
||||
backend processes. The <application>postmaster</application> |
||||
can take several command-line arguments to tune its behavior. |
||||
However, supplying arguments is necessary only if you intend to run multiple |
||||
sites or a non-default site. |
||||
</para> |
||||
|
||||
<para> |
||||
The <Productname>Postgres</Productname> backend |
||||
(the actual executable program <application>postgres</application>) may be executed |
||||
directly from the user shell by the |
||||
<Productname>Postgres</Productname> super-user |
||||
(with the database name as an argument). However, |
||||
doing this bypasses the shared buffer pool and lock table associated |
||||
with a postmaster/site, therefore this is not recommended in a multiuser |
||||
site. |
||||
</para> |
||||
<para> |
||||
The <Productname>Postgres</Productname> backend |
||||
(the actual executable program <application>postgres</application>) may be executed |
||||
directly from the user shell by the |
||||
<Productname>Postgres</Productname> super-user |
||||
(with the database name as an argument). However, |
||||
doing this bypasses the shared buffer pool and lock table associated |
||||
with a postmaster/site, therefore this is not recommended in a multiuser |
||||
site. |
||||
</para> |
||||
</sect1> |
||||
|
||||
<sect1> |
||||
<title>Notation</title> |
||||
<title>Notation</title> |
||||
|
||||
<para> |
||||
<quote>...</quote> or <filename>/usr/local/pgsql/</filename> |
||||
at the front of a file name is used to represent the |
||||
path to the <Productname>Postgres</Productname> superuser's home directory. |
||||
</para> |
||||
<para> |
||||
<quote>...</quote> or <filename>/usr/local/pgsql/</filename> |
||||
at the front of a file name is used to represent the |
||||
path to the <Productname>Postgres</Productname> superuser's home directory. |
||||
</para> |
||||
|
||||
<para> |
||||
In a command synopsis, brackets |
||||
(<quote>[</quote> and <quote>]</quote>) indicate an optional phrase or keyword. |
||||
Anything in braces |
||||
(<quote>{</quote> and <quote>}</quote>) and containing vertical bars (<quote>|</quote>) |
||||
indicates that you must choose one. |
||||
</para> |
||||
<para> |
||||
In a command synopsis, brackets |
||||
(<quote>[</quote> and <quote>]</quote>) indicate an optional phrase or keyword. |
||||
Anything in braces |
||||
(<quote>{</quote> and <quote>}</quote>) and containing vertical bars (<quote>|</quote>) |
||||
indicates that you must choose one. |
||||
</para> |
||||
|
||||
<para> |
||||
In examples, parentheses (<quote>(</quote> and <quote>)</quote>) are used to group boolean |
||||
expressions. <quote>|</quote> is the boolean operator OR. |
||||
</para> |
||||
<para> |
||||
In examples, parentheses (<quote>(</quote> and <quote>)</quote>) are used to group boolean |
||||
expressions. <quote>|</quote> is the boolean operator OR. |
||||
</para> |
||||
|
||||
<para> |
||||
Examples will show commands executed from various accounts and programs. |
||||
Commands executed from the root account will be preceeded with <quote>></quote>. |
||||
Commands executed from the <Productname>Postgres</Productname> |
||||
superuser account will be preceeded with <quote>%</quote>, while commands |
||||
executed from an unprivileged user's account will be preceeded with |
||||
<quote>$</quote>. |
||||
<acronym>SQL</acronym> commands will be preceeded with <quote>=></quote> |
||||
or will have no leading prompt, depending on the context. |
||||
</para> |
||||
<para> |
||||
Examples will show commands executed from various accounts and programs. |
||||
Commands executed from the root account will be preceeded with <quote>></quote>. |
||||
Commands executed from the <Productname>Postgres</Productname> |
||||
superuser account will be preceeded with <quote>%</quote>, while commands |
||||
executed from an unprivileged user's account will be preceeded with |
||||
<quote>$</quote>. |
||||
<acronym>SQL</acronym> commands will be preceeded with <quote>=></quote> |
||||
or will have no leading prompt, depending on the context. |
||||
</para> |
||||
|
||||
<note> |
||||
<para> |
||||
At the time of writing (<Productname>Postgres</Productname> v6.4) the notation for |
||||
flagging commands is not universally consistant throughout the documentation set. |
||||
Please report problems to |
||||
<ulink url="mailto:docs@postgresql.org">the Documentation Mailing List</ulink>. |
||||
</para> |
||||
</note> |
||||
<note> |
||||
<para> |
||||
At the time of writing (<Productname>Postgres</Productname> v6.5) the notation for |
||||
flagging commands is not universally consistant throughout the documentation set. |
||||
Please report problems to |
||||
<ulink url="mailto:docs@postgresql.org">the Documentation Mailing List</ulink>. |
||||
</para> |
||||
</note> |
||||
|
||||
</sect1> |
||||
|
||||
<!-- Keep this comment at the end of the file |
||||
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: |
||||
--> |
||||
|
||||
@ -1,74 +1,90 @@ |
||||
<sect1> |
||||
<title>Y2K Statement</title> |
||||
<sect1 id="y2k"> |
||||
<title>Y2K Statement</title> |
||||
|
||||
<note> |
||||
<title>Author</title> |
||||
<note> |
||||
<title>Author</title> |
||||
|
||||
<para> |
||||
Written by |
||||
<ulink url="mailto:lockhart@alumni.caltech.edu">Thomas Lockhart</ulink> |
||||
on 1998-10-22. |
||||
</para> |
||||
</note> |
||||
<para> |
||||
Written by |
||||
<ulink url="mailto:lockhart@alumni.caltech.edu">Thomas Lockhart</ulink> |
||||
on 1998-10-22. |
||||
</para> |
||||
</note> |
||||
|
||||
<para> |
||||
The <productname>PostgreSQL</productname> Global Development Team provides |
||||
the <productname>Postgres</productname> software code tree as a public service, |
||||
without warranty and without liability for it's behavior or performance. |
||||
However, at the time of writing: |
||||
</para> |
||||
<para> |
||||
The <productname>PostgreSQL</productname> Global Development Team provides |
||||
the <productname>Postgres</productname> software code tree as a public service, |
||||
without warranty and without liability for it's behavior or performance. |
||||
However, at the time of writing: |
||||
</para> |
||||
|
||||
<itemizedlist> |
||||
<listitem> |
||||
<para> |
||||
The author of this statement, a volunteer on the <productname>Postgres</productname> |
||||
support team since November, 1996, is not aware of |
||||
any problems in the <productname>Postgres</productname> code base related |
||||
to time transitions around Jan 1, 2000 (Y2K). |
||||
</para> |
||||
</listitem> |
||||
<itemizedlist> |
||||
<listitem> |
||||
<para> |
||||
The author of this statement, a volunteer on the <productname>Postgres</productname> |
||||
support team since November, 1996, is not aware of |
||||
any problems in the <productname>Postgres</productname> code base related |
||||
to time transitions around Jan 1, 2000 (Y2K). |
||||
</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para> |
||||
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 <productname>Postgres</productname>. 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. |
||||
</para> |
||||
</listitem> |
||||
<listitem> |
||||
<para> |
||||
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 <productname>Postgres</productname>. 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. |
||||
</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para> |
||||
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 |
||||
<ulink url="http://www.postgresql.org/docs/user/datatype.htm">User's Guide</ulink> |
||||
in the chapter on data types. |
||||
For two-digit years, the significant transition year is 1970, not 2000; |
||||
e.g. <quote>70-01-01</quote> is interpreted as <quote>1970-01-01</quote>, |
||||
whereas <quote>69-01-01</quote> is interpreted as <quote>2069-01-01</quote>. |
||||
</para> |
||||
</listitem> |
||||
<listitem> |
||||
<para> |
||||
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 |
||||
<ulink url="http://www.postgresql.org/docs/user/datatype.htm">User's Guide</ulink> |
||||
in the chapter on data types. |
||||
For two-digit years, the significant transition year is 1970, not 2000; |
||||
e.g. <quote>70-01-01</quote> is interpreted as <quote>1970-01-01</quote>, |
||||
whereas <quote>69-01-01</quote> is interpreted as <quote>2069-01-01</quote>. |
||||
</para> |
||||
</listitem> |
||||
|
||||
<listitem> |
||||
<para> |
||||
Any Y2K problems in the underlying OS related to obtaining "the |
||||
current time" may propagate into apparent Y2K problems in |
||||
<productname>Postgres</productname>. |
||||
</para> |
||||
</listitem> |
||||
<listitem> |
||||
<para> |
||||
Any Y2K problems in the underlying OS related to obtaining "the |
||||
current time" may propagate into apparent Y2K problems in |
||||
<productname>Postgres</productname>. |
||||
</para> |
||||
</listitem> |
||||
</itemizedlist> |
||||
|
||||
</itemizedlist> |
||||
|
||||
<para> |
||||
Refer to |
||||
<ulink url="http://www.gnu.org/software/year2000.html">The Gnu Project</ulink> |
||||
and |
||||
<ulink url="http://language.perl.com/news/y2k.html">The Perl Institute</ulink> |
||||
for further discussion of Y2K issues, particularly |
||||
as it relates to open source, no fee software. |
||||
</para> |
||||
<para> |
||||
Refer to |
||||
<ulink url="http://www.gnu.org/software/year2000.html">The Gnu Project</ulink> |
||||
and |
||||
<ulink url="http://language.perl.com/news/y2k.html">The Perl Institute</ulink> |
||||
for further discussion of Y2K issues, particularly |
||||
as it relates to open source, no fee software. |
||||
</para> |
||||
|
||||
</sect1> |
||||
|
||||
<!-- Keep this comment at the end of the file |
||||
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: |
||||
--> |
||||
|
||||
Loading…
Reference in new issue