Skip to content

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

Fix path to initdb in installation instructions. 

General cleanup for 7.0.
parent b2096a55
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 1304 additions and 967 deletions
doc/src/sgml/advanced.sgml
View file @ 30e355fc
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.9 2000/03/31 03:27:40 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.10 2000/04/07 13:30:58 thomas Exp $
--> -->
<chapter id="advanced"> <chapter id="advanced">
...@@ -106,10 +106,10 @@ SELECT c.name, c.altitude ...@@ -106,10 +106,10 @@ SELECT c.name, c.altitude
Here the <quote>*</quote> after cities indicates that the query should Here the <quote>*</quote> after cities indicates that the query should
be run over cities and all classes below cities in the be run over cities and all classes below cities in the
inheritance hierarchy. Many of the commands that we inheritance hierarchy. Many of the commands that we
have already discussed (<command>select</command>, have already discussed (<command>SELECT</command>,
<command>update</command> and <command>delete</command>) <command>UPDATE</command> and <command>DELETE</command>)
support this <quote>*</quote> notation, as do others, like support this <quote>*</quote> notation, as do others, like
<command>alter</command>. <command>ALTER</command>.
</para> </para>
</sect1> </sect1>
...@@ -118,7 +118,8 @@ SELECT c.name, c.altitude ...@@ -118,7 +118,8 @@ SELECT c.name, c.altitude
<para> <para>
One of the tenets of the relational model is that the One of the tenets of the relational model is that the
attributes of a relation are atomic. <productname>Postgres</productname> does not attributes of a relation are atomic.
<productname>Postgres</productname> does not
have this restriction; attributes can themselves contain have this restriction; attributes can themselves contain
sub-values that can be accessed from the query sub-values that can be accessed from the query
language. For example, you can create attributes that language. For example, you can create attributes that
...@@ -129,7 +130,8 @@ SELECT c.name, c.altitude ...@@ -129,7 +130,8 @@ SELECT c.name, c.altitude
<title>Arrays</title> <title>Arrays</title>
<para> <para>
<productname>Postgres</productname> allows attributes of an instance to be defined <productname>Postgres</productname> allows attributes of an
instance to be defined
as fixed-length or variable-length multi-dimensional as fixed-length or variable-length multi-dimensional
arrays. Arrays of any base type or user-defined type arrays. Arrays of any base type or user-defined type
can be created. To illustrate their use, we first create a can be created. To illustrate their use, we first create a
...@@ -149,11 +151,14 @@ CREATE TABLE SAL_EMP ( ...@@ -149,11 +151,14 @@ CREATE TABLE SAL_EMP (
a <firstterm>text</firstterm> string (name), a one-dimensional a <firstterm>text</firstterm> string (name), a one-dimensional
array of <firstterm>int4</firstterm> array of <firstterm>int4</firstterm>
(pay_by_quarter), which represents the employee's (pay_by_quarter), which represents the employee's
salary by quarter and a two-dimensional array of <firstterm>text</firstterm> salary by quarter and a two-dimensional array of
<firstterm>text</firstterm>
(schedule), which represents the employee's weekly (schedule), which represents the employee's weekly
schedule. Now we do some <firstterm>INSERTS</firstterm>s; note that when schedule. Now we do some <firstterm>INSERTS</firstterm>s;
note that when
appending to an array, we enclose the values within appending to an array, we enclose the values within
braces and separate them by commas. If you know <firstterm>C</firstterm>, braces and separate them by commas. If you know
<firstterm>C</firstterm>,
this is not unlike the syntax for initializing structures. this is not unlike the syntax for initializing structures.
<programlisting> <programlisting>
...@@ -168,7 +173,8 @@ INSERT INTO SAL_EMP ...@@ -168,7 +173,8 @@ INSERT INTO SAL_EMP
'{{"talk", "consult"}, {"meeting"}}'); '{{"talk", "consult"}, {"meeting"}}');
</programlisting> </programlisting>
By default, <productname>Postgres</productname> uses the "one-based" numbering By default, <productname>Postgres</productname> uses the
"one-based" numbering
convention for arrays -- that is, an array of n elements convention for arrays -- that is, an array of n elements
starts with array[1] and ends with array[n]. starts with array[1] and ends with array[n].
Now, we can run some queries on SAL_EMP. First, we Now, we can run some queries on SAL_EMP. First, we
...@@ -228,6 +234,11 @@ SELECT SAL_EMP.schedule[1:2][1:1] ...@@ -228,6 +234,11 @@ SELECT SAL_EMP.schedule[1:2][1:1]
</sect2> </sect2>
</sect1> </sect1>
<!--
We haven't had Time Travel for two or three years, so let's stop
mentioning it. - thomas 2000-04-02
<sect1> <sect1>
<title>Time Travel</title> <title>Time Travel</title>
...@@ -240,21 +251,27 @@ SELECT SAL_EMP.schedule[1:2][1:1] ...@@ -240,21 +251,27 @@ SELECT SAL_EMP.schedule[1:2][1:1]
</para> </para>
<para> <para>
New features such as triggers allow one to mimic the behavior of time travel when desired, without New features such as triggers allow one to mimic the behavior of
incurring the overhead when it is not needed (for most users, this is most of the time). time travel when desired, without
See examples in the <filename>contrib</filename> directory for more information. incurring the overhead when it is not needed (for most users, this
is most of the time).
See examples in the <filename>contrib</filename> directory for
more information.
</para> </para>
<note> <note>
<title>Time travel is deprecated</title> <title>Time travel is deprecated</title>
<para> <para>
The remaining text in this section is retained only until it can be rewritten in the context The remaining text in this section is retained only until it can
of new techniques to accomplish the same purpose. Volunteers? - thomas 1998-01-12 be rewritten in the context
of new techniques to accomplish the same purpose.
Volunteers? - thomas 1998-01-12
</para> </para>
</note> </note>
<para> <para>
<productname>Postgres</productname> supports the notion of time travel. This feature <productname>Postgres</productname> supports the notion of time
travel. This feature
allows a user to run historical queries. For allows a user to run historical queries. For
example, to find the current population of Mariposa example, to find the current population of Mariposa
city, one would query: city, one would query:
...@@ -269,7 +286,8 @@ SELECT * FROM cities WHERE name = 'Mariposa'; ...@@ -269,7 +286,8 @@ SELECT * FROM cities WHERE name = 'Mariposa';
+---------+------------+----------+ +---------+------------+----------+
</programlisting> </programlisting>
<productname>Postgres</productname> will automatically find the version of Mariposa's <productname>Postgres</productname> will automatically find the
version of Mariposa's
record valid at the current time. record valid at the current time.
One can also give a time range. For example to see the One can also give a time range. For example to see the
past and present populations of Mariposa, one would past and present populations of Mariposa, one would
...@@ -313,18 +331,22 @@ SELECT name, population ...@@ -313,18 +331,22 @@ SELECT name, population
abbreviated as ``[,].'' abbreviated as ``[,].''
</para> </para>
</sect1> </sect1>
-->
<sect1> <sect1>
<title>More Advanced Features</title> <title>More Advanced Features</title>
<para> <para>
<productname>Postgres</productname> has many features not touched upon in this <productname>Postgres</productname> has many features not touched
upon in this
tutorial introduction, which has been oriented toward newer users of tutorial introduction, which has been oriented toward newer users of
<acronym>SQL</acronym>. <acronym>SQL</acronym>.
These are discussed in more detail in both the User's and Programmer's Guides. These are discussed in more detail in both the User's and
Programmer's Guides.
</para> </para>
</sect1> </sect1>
</chapter> </chapter>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
......
doc/src/sgml/func.sgml
View file @ 30e355fc
...@@ -88,10 +88,10 @@ ...@@ -88,10 +88,10 @@
<entry>abs(-17.4)</entry> <entry>abs(-17.4)</entry>
</row> </row>
<row> <row>
<entry>sqrt(float8)</entry> <entry>degrees(float8)</entry>
<entry>float8</entry> <entry>float8</entry>
<entry>square root</entry> <entry>radians to degrees</entry>
<entry>sqrt(2.0)</entry> <entry>degrees(0.5)</entry>
</row> </row>
<row> <row>
<entry>exp(float8)</entry> <entry>exp(float8)</entry>
...@@ -111,18 +111,36 @@ ...@@ -111,18 +111,36 @@
<entry>base 10 logarithm</entry> <entry>base 10 logarithm</entry>
<entry>log(2.0)</entry> <entry>log(2.0)</entry>
</row> </row>
<row>
<entry>pi()</entry>
<entry>float8</entry>
<entry>fundamental constant</entry>
<entry>pi()</entry>
</row>
<row> <row>
<entry>pow(float8,float8)</entry> <entry>pow(float8,float8)</entry>
<entry>float8</entry> <entry>float8</entry>
<entry>raise a number to the specified exponent</entry> <entry>raise a number to the specified exponent</entry>
<entry>pow(2.0, 16.0)</entry> <entry>pow(2.0, 16.0)</entry>
</row> </row>
<row>
<entry>radians(float8)</entry>
<entry>float8</entry>
<entry>degrees to radians</entry>
<entry>radians(45.0)</entry>
</row>
<row> <row>
<entry>round(float8)</entry> <entry>round(float8)</entry>
<entry>float8</entry> <entry>float8</entry>
<entry>round to nearest integer</entry> <entry>round to nearest integer</entry>
<entry>round(42.4)</entry> <entry>round(42.4)</entry>
</row> </row>
<row>
<entry>sqrt(float8)</entry>
<entry>float8</entry>
<entry>square root</entry>
<entry>sqrt(2.0)</entry>
</row>
<row> <row>
<entry>trunc(float8)</entry> <entry>trunc(float8)</entry>
<entry>float8</entry> <entry>float8</entry>
...@@ -156,6 +174,88 @@ ...@@ -156,6 +174,88 @@
Most of the functions listed for FLOAT8 are also available for Most of the functions listed for FLOAT8 are also available for
type NUMERIC. type NUMERIC.
</para> </para>
<para>
<table tocentry="1">
<title>Transcendental Mathematical Functions</title>
<tgroup cols="4">
<thead>
<row>
<entry>Function</entry>
<entry>Returns</entry>
<entry>Description</entry>
<entry>Example</entry>
</row>
</thead>
<tbody>
<row>
<entry>acos(float8)</entry>
<entry>float8</entry>
<entry>arccosine</entry>
<entry>acos(10.0)</entry>
</row>
<row>
<entry>asin(float8)</entry>
<entry>float8</entry>
<entry>arcsine</entry>
<entry>asin(10.0)</entry>
</row>
<row>
<entry>atan(float8)</entry>
<entry>float8</entry>
<entry>arctangent</entry>
<entry>atan(10.0)</entry>
</row>
<row>
<entry>atan2(float8,float8)</entry>
<entry>float8</entry>
<entry>arctangent</entry>
<entry>atan3(10.0,20.0)</entry>
</row>
<row>
<entry>cos(float8)</entry>
<entry>float8</entry>
<entry>cosine</entry>
<entry>cos(0.4)</entry>
</row>
<row>
<entry>cot(float8)</entry>
<entry>float8</entry>
<entry>cotangent</entry>
<entry>cot(20.0)</entry>
</row>
<row>
<entry>sin(float8)</entry>
<entry>float8</entry>
<entry>sine</entry>
<entry>cos(0.4)</entry>
</row>
<row>
<entry>cos(float8)</entry>
<entry>float8</entry>
<entry>cosine</entry>
<entry>cos(0.4)</entry>
</row>
<row>
<entry>cos(float8)</entry>
<entry>float8</entry>
<entry>cosine</entry>
<entry>cos(0.4)</entry>
</row>
<row>
<entry>cos(float8)</entry>
<entry>float8</entry>
<entry>cosine</entry>
<entry>cos(0.4)</entry>
</row>
<row>
<entry>cos(float8)</entry>
<entry>float8</entry>
<entry>cosine</entry>
<entry>cos(0.4)</entry>
</row>
</sect1> </sect1>
<sect1> <sect1>
......
doc/src/sgml/install.sgml
View file @ 30e355fc
This diff is collapsed.
doc/src/sgml/intro.sgml
View file @ 30e355fc
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.10 2000/03/31 03:27:40 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.11 2000/04/07 13:30:58 thomas Exp $
--> -->
<chapter id="intro"> <chapter id="intro">
...@@ -16,7 +16,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.10 2000/03/31 03:27:40 thoma ...@@ -16,7 +16,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.10 2000/03/31 03:27:40 thoma
<productname>Postgres release 4.2</productname></ulink>. <productname>Postgres release 4.2</productname></ulink>.
The <productname>Postgres</productname> project, The <productname>Postgres</productname> project,
led by Professor Michael Stonebraker, was sponsored by the led by Professor Michael Stonebraker, was sponsored by the
Defense Advanced Research Projects Agency (<acronym>DARPA</acronym>), the Defense Advanced Research Projects Agency
(<acronym>DARPA</acronym>), the
Army Research Office (<acronym>ARO</acronym>), the National Science Army Research Office (<acronym>ARO</acronym>), the National Science
Foundation (<acronym>NSF</acronym>), and ESL, Inc. Foundation (<acronym>NSF</acronym>), and ESL, Inc.
</para> </para>
...@@ -37,7 +38,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.10 2000/03/31 03:27:40 thoma ...@@ -37,7 +38,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.10 2000/03/31 03:27:40 thoma
models in part because of its "Spartan simplicity". models in part because of its "Spartan simplicity".
However, as mentioned, this simplicity often makes the However, as mentioned, this simplicity often makes the
implementation of certain applications very difficult. implementation of certain applications very difficult.
<productname>Postgres</productname> offers substantial additional <productname>Postgres</productname> offers substantial additional
power by incorporating the following four additional power by incorporating the following four additional
basic concepts in such a way that users can easily basic concepts in such a way that users can easily
extend the system: extend the system:
...@@ -62,13 +63,16 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.10 2000/03/31 03:27:40 thoma ...@@ -62,13 +63,16 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.10 2000/03/31 03:27:40 thoma
</para> </para>
<para> <para>
These features put <productname>Postgres</productname> into the category of databases These features put <productname>Postgres</productname> into the
referred to as <firstterm>object-relational</firstterm>. Note that this is distinct category of databases referred to as
from those referred to as <firstterm>object-oriented</firstterm>, which in general <firstterm>object-relational</firstterm>. Note that this is distinct
are not as well suited to supporting the traditional relational database languages. from those referred to as <firstterm>object-oriented</firstterm>,
So, although <productname>Postgres</productname> has some object-oriented features, which in general are not as well suited to supporting the
it is firmly in the relational database world. In fact, some commercial databases traditional relational database languages.
have recently incorporated features pioneered by <productname>Postgres</productname>. So, although <productname>Postgres</productname> has some
object-oriented features, it is firmly in the relational database
world. In fact, some commercial databases have recently
incorporated features pioneered by <productname>Postgres</productname>.
</para> </para>
</sect1> </sect1>
......
doc/src/sgml/legal.sgml
View file @ 30e355fc
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/legal.sgml,v 1.7 2000/03/31 03:27:40 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/legal.sgml,v 1.8 2000/04/07 13:30:58 thomas Exp $
--> -->
<sect1 id="copyright"> <sect1 id="copyright">
...@@ -7,7 +7,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/legal.sgml,v 1.7 2000/03/31 03:27:40 thomas ...@@ -7,7 +7,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/legal.sgml,v 1.7 2000/03/31 03:27:40 thomas
<para> <para>
<productname>PostgreSQL</productname> is Copyright &copy; 1996-2000 <productname>PostgreSQL</productname> is Copyright &copy; 1996-2000
by the PostgreSQL Inc. by PostgreSQL Inc.
and is distributed under the terms of the Berkeley license. and is distributed under the terms of the Berkeley license.
</para> </para>
...@@ -35,14 +35,22 @@ $Header: /cvsroot/pgsql/doc/src/sgml/legal.sgml,v 1.7 2000/03/31 03:27:40 thomas ...@@ -35,14 +35,22 @@ $Header: /cvsroot/pgsql/doc/src/sgml/legal.sgml,v 1.7 2000/03/31 03:27:40 thomas
maintainance, support, updates, enhancements, or modifications. maintainance, support, updates, enhancements, or modifications.
</para> </para>
<!--
How to keep track of all the trademarks? I'll try the strategy used at
www.qnx.com - thomas
<para> <para>
<acronym>Unix</acronym> is a trademark of X/Open, Ltd. Sun4, SPARC, SunOS <acronym>Unix</acronym> is a trademark of X/Open, Ltd. Sun4, SPARC, SunOS
and Solaris are trademarks of Sun Microsystems, Inc. DEC, and Solaris are trademarks of Sun Microsystems, Inc. DEC,
DECstation, Alpha AXP and ULTRIX are trademarks of Digital DECstation, Alpha AXP and ULTRIX are trademarks of Compaq, formerly Digital
Equipment Corp. PA-RISC and HP-UX are trademarks of Equipment Corp. PA-RISC and HP-UX are trademarks of
Hewlett-Packard Co. OSF/1 is a trademark of the Open Hewlett-Packard Co. OSF/1 is a trademark of the Open
Software Foundation. Software Foundation.
</para> </para>
-->
<para>
All trademarks are the property of their respective owners.
</para>
</sect1> </sect1>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
......
doc/src/sgml/notation.sgml
View file @ 30e355fc
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.8 2000/03/31 03:27:41 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.9 2000/04/07 13:30:58 thomas Exp $
--> -->
<sect1 id="terminology"> <sect1 id="terminology">
...@@ -25,13 +25,15 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.8 2000/03/31 03:27:41 tho ...@@ -25,13 +25,15 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.8 2000/03/31 03:27:41 tho
binaries and database files. As the database superuser, all binaries and database files. As the database superuser, all
protection mechanisms may be bypassed and any data accessed protection mechanisms may be bypassed and any data accessed
arbitrarily. arbitrarily.
In addition, the <Productname>Postgres</Productname> superuser is allowed to execute In addition, the <Productname>Postgres</Productname> superuser is
allowed to execute
some support programs which are generally not available to all users. some support programs which are generally not available to all users.
Note that the <Productname>Postgres</Productname> superuser is Note that the <Productname>Postgres</Productname> superuser is
<emphasis>not</emphasis> <emphasis>not</emphasis>
the same as the Unix superuser (which will be referred to as <firstterm>root</firstterm>). the same as the Unix superuser (which will be referred to as
The superuser should have a non-zero user identifier (<firstterm>UID</firstterm>) <firstterm>root</firstterm>).
for security reasons. The superuser should have a non-zero user identifier
(<firstterm>UID</firstterm>) for security reasons.
</para> </para>
<para> <para>
...@@ -82,18 +84,21 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.8 2000/03/31 03:27:41 tho ...@@ -82,18 +84,21 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.8 2000/03/31 03:27:41 tho
In a command synopsis, brackets In a command synopsis, brackets
(<quote>[</quote> and <quote>]</quote>) indicate an optional phrase or keyword. (<quote>[</quote> and <quote>]</quote>) indicate an optional phrase or keyword.
Anything in braces Anything in braces
(<quote>{</quote> and <quote>}</quote>) and containing vertical bars (<quote>|</quote>) (<quote>{</quote> and <quote>}</quote>) and containing vertical bars
(<quote>|</quote>)
indicates that you must choose one. indicates that you must choose one.
</para> </para>
<para> <para>
In examples, parentheses (<quote>(</quote> and <quote>)</quote>) are used to group boolean In examples, parentheses (<quote>(</quote> and <quote>)</quote>) are
used to group boolean
expressions. <quote>|</quote> is the boolean operator OR. expressions. <quote>|</quote> is the boolean operator OR.
</para> </para>
<para> <para>
Examples will show commands executed from various accounts and programs. Examples will show commands executed from various accounts and programs.
Commands executed from the root account will be preceeded with <quote>&gt;</quote>. Commands executed from the root account will be preceeded with
<quote>&gt;</quote>.
Commands executed from the <Productname>Postgres</Productname> Commands executed from the <Productname>Postgres</Productname>
superuser account will be preceeded with <quote>%</quote>, while commands superuser account will be preceeded with <quote>%</quote>, while commands
executed from an unprivileged user's account will be preceeded with executed from an unprivileged user's account will be preceeded with
...@@ -104,8 +109,10 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.8 2000/03/31 03:27:41 tho ...@@ -104,8 +109,10 @@ $Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.8 2000/03/31 03:27:41 tho
<note> <note>
<para> <para>
At the time of writing (<Productname>Postgres</Productname> v6.5) the notation for At the time of writing (<Productname>Postgres</Productname> v7.0)
flagging commands is not universally consistant throughout the documentation set. the notation for
flagging commands is not universally consistant throughout the
documentation set.
Please report problems to Please report problems to
<ulink url="mailto:docs@postgresql.org">the Documentation Mailing List</ulink>. <ulink url="mailto:docs@postgresql.org">the Documentation Mailing List</ulink>.
</para> </para>
......
doc/src/sgml/ports.sgml
View file @ 30e355fc
...@@ -32,15 +32,15 @@ ...@@ -32,15 +32,15 @@
<row> <row>
<entry>AIX 4.3.2</entry> <entry>AIX 4.3.2</entry>
<entry>RS6000</entry> <entry>RS6000</entry>
<entry>v6.5</entry> <entry>v7.0</entry>
<entry>1999-05-26</entry> <entry>2000-04-05</entry>
<entry>(<ulink url="mailto:Andreas.Zeugswetter@telecom.at">Andreas Zeugswetter</ulink>)</entry> <entry>(<ulink url="mailto:Andreas.Zeugswetter@telecom.at">Andreas Zeugswetter</ulink>)</entry>
</row> </row>
<row> <row>
<entry>BSDI</entry> <entry>BSDI 4.01</entry>
<entry>x86</entry> <entry>x86</entry>
<entry>v6.5</entry> <entry>v7.0</entry>
<entry>1999-05-25</entry> <entry>2000-04-04</entry>
<entry>(<ulink url="mailto:maillist@candle.pha.pa.us">Bruce Momjian</ulink></entry> <entry>(<ulink url="mailto:maillist@candle.pha.pa.us">Bruce Momjian</ulink></entry>
</row> </row>
<row> <row>
...@@ -60,12 +60,11 @@ ...@@ -60,12 +60,11 @@
(<ulink url="mailto:pjlobo@euitt.upm.es">Pedro J. Lobo</ulink>)</entry> (<ulink url="mailto:pjlobo@euitt.upm.es">Pedro J. Lobo</ulink>)</entry>
</row> </row>
<row> <row>
<entry>FreeBSD 2.2.x-4.0</entry> <entry>FreeBSD 4.0</entry>
<entry>x86</entry> <entry>x86</entry>
<entry>v6.5</entry> <entry>v7.0</entry>
<entry>1999-05-25</entry> <entry>2000-04-04</entry>
<entry>(<ulink url="mailto:t-ishii@sra.co.jp">Tatsuo Ishii</ulink>, <entry>(<ulink url="mailto:scrappy@hub.org">Marc Fournier</ulink>)</entry>
<ulink url="mailto:scrappy@hub.org">Marc Fournier</ulink>)</entry>
</row> </row>
<row> <row>
<entry>HPUX</entry> <entry>HPUX</entry>
...@@ -136,17 +135,17 @@ ...@@ -136,17 +135,17 @@
(<ulink url="mailto:t-ishii@sra.co.jp">Tatsuo Ishii</ulink>)</entry> (<ulink url="mailto:t-ishii@sra.co.jp">Tatsuo Ishii</ulink>)</entry>
</row> </row>
<row> <row>
<entry>Linux 2.0.x</entry> <entry>Linux 2.2.5</entry>
<entry>Sparc</entry> <entry>Sparc</entry>
<entry>v6.4</entry> <entry>v7.0</entry>
<entry>1998-10-25</entry> <entry>2000-04-02</entry>
<entry>(<ulink url="mailto:szybist@boxhill.com">Tom Szybist</ulink>)</entry> <entry>(<ulink url="mailto:szybist@boxhill.com">Tom Szybist</ulink>)</entry>
</row> </row>
<row> <row>
<entry>LinuxPPC R4 2.2.1/libc5</entry> <entry>LinuxPPC R4</entry>
<entry>PPC603e</entry> <entry>PPC603e</entry>
<entry>v7.0</entry> <entry>v7.0</entry>
<entry>2000-03-26</entry> <entry>2000-04-04</entry>
<entry>Powerbook 2400c <entry>Powerbook 2400c
(<ulink url="mailto:t-ishii@sra.co.jp">Tatsuo Ishii</ulink>)</entry> (<ulink url="mailto:t-ishii@sra.co.jp">Tatsuo Ishii</ulink>)</entry>
</row> </row>
...@@ -250,20 +249,20 @@ ...@@ -250,20 +249,20 @@
(<ulink url="mailto:ridderbusch.pad@sni.de">Frank Ridderbusch</ulink>)</entry> (<ulink url="mailto:ridderbusch.pad@sni.de">Frank Ridderbusch</ulink>)</entry>
</row> </row>
<row> <row>
<entry>Windows</entry> <entry>Windows/Win32</entry>
<entry>x86</entry> <entry>x86</entry>
<entry>v6.4</entry> <entry>v7.0</entry>
<entry>1999-01-06</entry> <entry>2000-04-02</entry>
<entry>Client-side libraries or ODBC/JDBC. No server yet. <entry>Client-side libraries or ODBC/JDBC. No server-side.
(<ulink url="mha@sollentuna.net">Magnus Hagander</ulink></entry> (<ulink url="mha@sollentuna.net">Magnus Hagander</ulink></entry>
</row> </row>
<row> <row>
<entry>Windows NT</entry> <entry>WinNT/Cygwin</entry>
<entry>x86</entry> <entry>x86</entry>
<entry>v6.5</entry> <entry>v7.0</entry>
<entry>1999-05-26</entry> <entry>2000-03-30</entry>
<entry>Working with the Cygwin library. <entry>Working with the Cygwin library.
(<ulink url="mailto:Dan.Horak@email.cz">Daniel Horak</ulink>) </entry> (<ulink url="mailto:horak@sit.plzen-city.cz">Daniel Horak</ulink>) </entry>
</row> </row>
</tbody> </tbody>
</tgroup> </tgroup>
...@@ -273,8 +272,9 @@ ...@@ -273,8 +272,9 @@
<note> <note>
<para> <para>
For <productname>Windows NT</productname>, For <productname>Windows NT</productname>,
the server-side port of <productname>Postgres</productname> has recently been the server-side port of <productname>Postgres</productname> uses
accomplished. The Cygnus library is required to compile it. the RedHat/Cygnus <productname>Cygwin</productname> library and
toolset.
</para> </para>
</note> </note>
</sect1> </sect1>
...@@ -289,7 +289,8 @@ ...@@ -289,7 +289,8 @@
</para> </para>
<para> <para>
At the time of publication, the following platforms have been tested: At the time of publication, the following platforms have not been
tested for v7.0:
<table tocentry="1"> <table tocentry="1">
<title>Obsolete Platforms</title> <title>Obsolete Platforms</title>
......
doc/src/sgml/query.sgml
View file @ 30e355fc
This diff is collapsed.
doc/src/sgml/sql.sgml
View file @ 30e355fc
This diff is collapsed.
doc/src/sgml/start.sgml
View file @ 30e355fc
This diff is collapsed.
doc/src/sgml/y2k.sgml
View file @ 30e355fc
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/y2k.sgml,v 1.5 2000/03/31 03:27:42 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/y2k.sgml,v 1.6 2000/04/07 13:30:58 thomas Exp $
--> -->
<sect1 id="y2k"> <sect1 id="y2k">
...@@ -11,7 +11,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/y2k.sgml,v 1.5 2000/03/31 03:27:42 th ...@@ -11,7 +11,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/y2k.sgml,v 1.5 2000/03/31 03:27:42 th
<para> <para>
Written by Written by
<ulink url="mailto:lockhart@alumni.caltech.edu">Thomas Lockhart</ulink> <ulink url="mailto:lockhart@alumni.caltech.edu">Thomas Lockhart</ulink>
on 1998-10-22. on 1998-10-22. Updated 2000-03-31.
</para> </para>
</note> </note>
...@@ -25,7 +25,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/y2k.sgml,v 1.5 2000/03/31 03:27:42 th ...@@ -25,7 +25,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/y2k.sgml,v 1.5 2000/03/31 03:27:42 th
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
The author of this statement, a volunteer on the <productname>Postgres</productname> The author of this statement, a volunteer on the
<productname>Postgres</productname>
support team since November, 1996, is not aware of support team since November, 1996, is not aware of
any problems in the <productname>Postgres</productname> code base related any problems in the <productname>Postgres</productname> code base related
to time transitions around Jan 1, 2000 (Y2K). to time transitions around Jan 1, 2000 (Y2K).
......
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