Commit 03a321d2 authored by Thomas G. Lockhart's avatar Thomas G. Lockhart

Use PostgreSQL consistantly throughout docs. Before, usage was split evenly

 between Postgres and PostgreSQL.
parent 68cb184b
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/abort.sgml,v 1.8 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/abort.sgml,v 1.9 2001/12/08 03:24:33 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-ABORT"> <refentry id="SQL-ABORT">
...@@ -129,7 +129,7 @@ ABORT WORK; ...@@ -129,7 +129,7 @@ ABORT WORK;
SQL92 SQL92
</title> </title>
<para> <para>
This command is a <productname>Postgres</productname> extension present This command is a <productname>PostgreSQL</productname> extension present
for historical reasons. <command>ROLLBACK</command> is the <acronym>SQL92</acronym> for historical reasons. <command>ROLLBACK</command> is the <acronym>SQL92</acronym>
equivalent command. equivalent command.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/allfiles.sgml,v 1.30 2001/05/08 21:06:42 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/allfiles.sgml,v 1.31 2001/12/08 03:24:33 thomas Exp $
Postgres documentation PostgreSQL documentation
Complete list of usable sgml source files in this directory. Complete list of usable sgml source files in this directory.
--> -->
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_group.sgml,v 1.6 2001/09/12 01:55:25 ishii Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_group.sgml,v 1.7 2001/12/08 03:24:33 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-ALTERGROUP"> <refentry id="SQL-ALTERGROUP">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.33 2001/11/22 03:42:32 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.34 2001/12/08 03:24:33 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-ALTERTABLE"> <refentry id="SQL-ALTERTABLE">
...@@ -313,7 +313,7 @@ ALTER TABLE distributors ADD CONSTRAINT dist_id_zipcode_key UNIQUE (dist_id, zip ...@@ -313,7 +313,7 @@ ALTER TABLE distributors ADD CONSTRAINT dist_id_zipcode_key UNIQUE (dist_id, zip
<para> <para>
SQL92 specifies some additional capabilities for <command>ALTER TABLE</command> SQL92 specifies some additional capabilities for <command>ALTER TABLE</command>
statement which are not yet directly supported by <productname>Postgres</productname>: statement which are not yet directly supported by <productname>PostgreSQL</productname>:
<variablelist> <variablelist>
<varlistentry> <varlistentry>
...@@ -345,7 +345,7 @@ DROP TABLE temp; ...@@ -345,7 +345,7 @@ DROP TABLE temp;
<para> <para>
The clauses to rename tables, columns, indexes, and sequences are The clauses to rename tables, columns, indexes, and sequences are
<productname>Postgres</productname> extensions from SQL92. <productname>PostgreSQL</productname> extensions from SQL92.
</para> </para>
</refsect2> </refsect2>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.17 2001/09/21 20:31:45 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.18 2001/12/08 03:24:33 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-ALTERUSER"> <refentry id="SQL-ALTERUSER">
...@@ -155,7 +155,7 @@ ERROR: ALTER USER: user "username" does not exist ...@@ -155,7 +155,7 @@ ERROR: ALTER USER: user "username" does not exist
</title> </title>
<para> <para>
<command>ALTER USER</command> is used to change the attributes of a user's <command>ALTER USER</command> is used to change the attributes of a user's
<productname>Postgres</productname> account. Attributes not mentioned <productname>PostgreSQL</productname> account. Attributes not mentioned
in the command retain their previous settings. in the command retain their previous settings.
</para> </para>
<para> <para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.4 2001/11/18 22:17:30 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.5 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-ANALYZE"> <refentry id="SQL-ANALYZE">
...@@ -99,7 +99,7 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ (<rep ...@@ -99,7 +99,7 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ (<rep
</title> </title>
<para> <para>
<command>ANALYZE</command> collects statistics about the contents of <command>ANALYZE</command> collects statistics about the contents of
<productname>Postgres</productname> tables, and stores the results in <productname>PostgreSQL</productname> tables, and stores the results in
the system table <literal>pg_statistic</literal>. Subsequently, the system table <literal>pg_statistic</literal>. Subsequently,
the query planner uses the statistics to help determine the most efficient the query planner uses the statistics to help determine the most efficient
execution plans for queries. execution plans for queries.
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/begin.sgml,v 1.14 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/begin.sgml,v 1.15 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-BEGIN"> <refentry id="SQL-BEGIN">
...@@ -95,7 +95,7 @@ NOTICE: BEGIN: already a transaction in progress ...@@ -95,7 +95,7 @@ NOTICE: BEGIN: already a transaction in progress
</title> </title>
<para> <para>
By default, <productname>Postgres</productname> executes transactions By default, <productname>PostgreSQL</productname> executes transactions
in <firstterm>unchained mode</firstterm> in <firstterm>unchained mode</firstterm>
(also known as <quote>autocommit</quote> in other database (also known as <quote>autocommit</quote> in other database
systems). systems).
...@@ -116,7 +116,7 @@ NOTICE: BEGIN: already a transaction in progress ...@@ -116,7 +116,7 @@ NOTICE: BEGIN: already a transaction in progress
<para> <para>
The default transaction isolation level in The default transaction isolation level in
<productname>Postgres</productname> <productname>PostgreSQL</productname>
is READ COMMITTED, where queries inside the transaction see only changes is READ COMMITTED, where queries inside the transaction see only changes
committed before query execution. So, you have to use committed before query execution. So, you have to use
<command>SET TRANSACTION ISOLATION LEVEL SERIALIZABLE</command> <command>SET TRANSACTION ISOLATION LEVEL SERIALIZABLE</command>
...@@ -128,7 +128,7 @@ NOTICE: BEGIN: already a transaction in progress ...@@ -128,7 +128,7 @@ NOTICE: BEGIN: already a transaction in progress
</para> </para>
<para> <para>
If the transaction is committed, <productname>Postgres</productname> If the transaction is committed, <productname>PostgreSQL</productname>
will ensure either that all updates are done or else that none of will ensure either that all updates are done or else that none of
them are done. Transactions have the standard <acronym>ACID</acronym> them are done. Transactions have the standard <acronym>ACID</acronym>
(atomic, consistent, isolatable, and durable) property. (atomic, consistent, isolatable, and durable) property.
...@@ -185,7 +185,7 @@ BEGIN WORK; ...@@ -185,7 +185,7 @@ BEGIN WORK;
<para> <para>
<command>BEGIN</command> <command>BEGIN</command>
is a <productname>Postgres</productname> language extension. is a <productname>PostgreSQL</productname> language extension.
There is no explicit <command>BEGIN</command> There is no explicit <command>BEGIN</command>
command in <acronym>SQL92</acronym>; command in <acronym>SQL92</acronym>;
transaction initiation is always implicit and it terminates either transaction initiation is always implicit and it terminates either
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/close.sgml,v 1.8 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/close.sgml,v 1.9 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CLOSE"> <refentry id="SQL-CLOSE">
...@@ -112,7 +112,7 @@ NOTICE PerformPortalClose: portal "<replaceable class="PARAMETER">cursor</replac ...@@ -112,7 +112,7 @@ NOTICE PerformPortalClose: portal "<replaceable class="PARAMETER">cursor</replac
Notes Notes
</title> </title>
<para> <para>
<productname>Postgres</productname> does not have <productname>PostgreSQL</productname> does not have
an explicit <command>OPEN</command> cursor statement; an explicit <command>OPEN</command> cursor statement;
a cursor is considered open when it is declared. a cursor is considered open when it is declared.
Use the <command>DECLARE</command> statement to declare a cursor. Use the <command>DECLARE</command> statement to declare a cursor.
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.12 2001/10/31 04:49:43 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.13 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CLUSTER"> <refentry id="SQL-CLUSTER">
...@@ -114,7 +114,7 @@ ERROR: Relation <replaceable class="PARAMETER">table</replaceable> does not exis ...@@ -114,7 +114,7 @@ ERROR: Relation <replaceable class="PARAMETER">table</replaceable> does not exis
Description Description
</title> </title>
<para> <para>
<command>CLUSTER</command> instructs <productname>Postgres</productname> <command>CLUSTER</command> instructs <productname>PostgreSQL</productname>
to cluster the table specified to cluster the table specified
by <replaceable class="parameter">table</replaceable> approximately by <replaceable class="parameter">table</replaceable> approximately
based on the index specified by based on the index specified by
...@@ -174,7 +174,7 @@ ERROR: Relation <replaceable class="PARAMETER">table</replaceable> does not exis ...@@ -174,7 +174,7 @@ ERROR: Relation <replaceable class="PARAMETER">table</replaceable> does not exis
on large tables because the rows are fetched from the heap on large tables because the rows are fetched from the heap
in index order, and if the heap table is unordered, the in index order, and if the heap table is unordered, the
entries are on random pages, so there is one disk page entries are on random pages, so there is one disk page
retrieved for every row moved. <productname>Postgres</productname> has a cache, retrieved for every row moved. <productname>PostgreSQL</productname> has a cache,
but the majority of a big table will not fit in the cache. but the majority of a big table will not fit in the cache.
</para> </para>
...@@ -186,7 +186,7 @@ SELECT <replaceable class="parameter">columnlist</replaceable> INTO TABLE <repla ...@@ -186,7 +186,7 @@ SELECT <replaceable class="parameter">columnlist</replaceable> INTO TABLE <repla
FROM <replaceable class="parameter">table</replaceable> ORDER BY <replaceable class="parameter">columnlist</replaceable> FROM <replaceable class="parameter">table</replaceable> ORDER BY <replaceable class="parameter">columnlist</replaceable>
</programlisting> </programlisting>
which uses the <productname>Postgres</productname> sorting code in which uses the <productname>PostgreSQL</productname> sorting code in
the ORDER BY clause to match the index, and which is much faster for the ORDER BY clause to match the index, and which is much faster for
unordered data. You then drop the old table, use unordered data. You then drop the old table, use
<command>ALTER TABLE...RENAME</command> <command>ALTER TABLE...RENAME</command>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/comment.sgml,v 1.10 2001/10/03 20:54:20 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/comment.sgml,v 1.11 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-COMMENT"> <refentry id="SQL-COMMENT">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/commit.sgml,v 1.11 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/commit.sgml,v 1.12 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-COMMIT"> <refentry id="SQL-COMMIT">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.25 2001/12/04 21:19:57 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.26 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-COPY"> <refentry id="SQL-COPY">
...@@ -172,7 +172,7 @@ ERROR: <replaceable>reason</replaceable> ...@@ -172,7 +172,7 @@ ERROR: <replaceable>reason</replaceable>
</title> </title>
<para> <para>
<command>COPY</command> moves data between <command>COPY</command> moves data between
<productname>Postgres</productname> tables and <productname>PostgreSQL</productname> tables and
standard file-system files. standard file-system files.
<command>COPY TO</command> copies the entire contents of a table to <command>COPY TO</command> copies the entire contents of a table to
...@@ -182,7 +182,7 @@ ERROR: <replaceable>reason</replaceable> ...@@ -182,7 +182,7 @@ ERROR: <replaceable>reason</replaceable>
<para> <para>
<command>COPY</command> with a filename instructs <command>COPY</command> with a filename instructs
the <productname>Postgres</productname> backend the <productname>PostgreSQL</productname> backend
to directly read from or write to a file. to directly read from or write to a file.
The file must be accessible to the backend and the name must be specified The file must be accessible to the backend and the name must be specified
from the viewpoint of the backend. from the viewpoint of the backend.
...@@ -262,7 +262,8 @@ ERROR: <replaceable>reason</replaceable> ...@@ -262,7 +262,8 @@ ERROR: <replaceable>reason</replaceable>
directly by the backend, not by the client application. Therefore, directly by the backend, not by the client application. Therefore,
they must reside on or be accessible to the database server machine, they must reside on or be accessible to the database server machine,
not the client. They must be accessible to and readable or writable not the client. They must be accessible to and readable or writable
by the Postgres user (the userid the backend runs as), not the client. by the <application>PostgreSQL</application> user (the userid the
backend runs as), not the client.
<command>COPY</command> naming a file is only allowed to database <command>COPY</command> naming a file is only allowed to database
superusers, since it allows writing on any file that the backend has superusers, since it allows writing on any file that the backend has
privileges to write on. privileges to write on.
...@@ -343,7 +344,7 @@ ERROR: <replaceable>reason</replaceable> ...@@ -343,7 +344,7 @@ ERROR: <replaceable>reason</replaceable>
as the column delimiter, backslash that delimiter character to include as the column delimiter, backslash that delimiter character to include
it in data.) A literal newline character is it in data.) A literal newline character is
represented as a backslash and a newline. When loading text data represented as a backslash and a newline. When loading text data
not generated by <acronym>Postgres</acronym>, not generated by <application>PostgreSQL</application>,
you will need to convert backslash you will need to convert backslash
characters ("\") to double-backslashes ("\\") to ensure that they characters ("\") to double-backslashes ("\\") to ensure that they
are loaded properly. are loaded properly.
...@@ -357,7 +358,8 @@ ERROR: <replaceable>reason</replaceable> ...@@ -357,7 +358,8 @@ ERROR: <replaceable>reason</replaceable>
<title>Binary Format</title> <title>Binary Format</title>
<para> <para>
The file format used for <command>COPY BINARY</command> changed in The file format used for <command>COPY BINARY</command> changed in
Postgres v7.1. The new format consists of a file header, zero or more <application>PostgreSQL</application> v7.1.
The new format consists of a file header, zero or more
tuples, and a file trailer. tuples, and a file trailer.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.15 2001/09/13 15:55:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.16 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATEAGGREGATE"> <refentry id="SQL-CREATEAGGREGATE">
...@@ -157,7 +157,7 @@ CREATE ...@@ -157,7 +157,7 @@ CREATE
</title> </title>
<para> <para>
<command>CREATE AGGREGATE</command> <command>CREATE AGGREGATE</command>
allows a user or programmer to extend <productname>Postgres</productname> allows a user or programmer to extend <productname>PostgreSQL</productname>
functionality by defining new aggregate functions. Some aggregate functions functionality by defining new aggregate functions. Some aggregate functions
for base types such as <function>min(integer)</function> for base types such as <function>min(integer)</function>
and <function>avg(double precision)</function> are already provided in the base and <function>avg(double precision)</function> are already provided in the base
...@@ -185,7 +185,7 @@ CREATE ...@@ -185,7 +185,7 @@ CREATE
</programlisting> </programlisting>
</para> </para>
<para> <para>
<productname>Postgres</productname> creates a temporary variable <productname>PostgreSQL</productname> creates a temporary variable
of data type <replaceable class="PARAMETER">stype</replaceable> of data type <replaceable class="PARAMETER">stype</replaceable>
to hold the current internal state of the aggregate. At each input to hold the current internal state of the aggregate. At each input
data item, data item,
...@@ -284,7 +284,7 @@ CREATE ...@@ -284,7 +284,7 @@ CREATE
</title> </title>
<para> <para>
<command>CREATE AGGREGATE</command> <command>CREATE AGGREGATE</command>
is a <productname>Postgres</productname> language extension. is a <productname>PostgreSQL</productname> language extension.
There is no <command>CREATE AGGREGATE</command> in SQL92. There is no <command>CREATE AGGREGATE</command> in SQL92.
</para> </para>
</refsect2> </refsect2>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v 1.3 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v 1.4 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATECONSTRAINT"> <refentry id="SQL-CREATECONSTRAINT">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.21 2001/11/18 00:38:00 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.22 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATEDATABASE"> <refentry id="SQL-CREATEDATABASE">
...@@ -170,7 +170,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> ...@@ -170,7 +170,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
</title> </title>
<para> <para>
<command>CREATE DATABASE</command> creates a new <command>CREATE DATABASE</command> creates a new
<productname>Postgres</productname> database. <productname>PostgreSQL</productname> database.
The creator becomes the owner of the new database. The creator becomes the owner of the new database.
</para> </para>
...@@ -201,7 +201,8 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> ...@@ -201,7 +201,8 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
<replaceable class="parameter">name</replaceable>. In particular, <replaceable class="parameter">name</replaceable>. In particular,
by writing <literal>TEMPLATE = template0</>, you can create a virgin by writing <literal>TEMPLATE = template0</>, you can create a virgin
database containing only the standard objects predefined by your database containing only the standard objects predefined by your
version of Postgres. This is useful if you wish to avoid copying version of <application>PostgreSQL</application>. This is useful
if you wish to avoid copying
any installation-local objects that may have been added to any installation-local objects that may have been added to
<literal>template1</>. <literal>template1</>.
</para> </para>
...@@ -226,7 +227,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> ...@@ -226,7 +227,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
Notes Notes
</title> </title>
<para> <para>
<command>CREATE DATABASE</command> is a <productname>Postgres</productname> <command>CREATE DATABASE</command> is a <productname>PostgreSQL</productname>
language extension. language extension.
</para> </para>
<para> <para>
...@@ -250,7 +251,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> ...@@ -250,7 +251,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
comment from Olly; response from Thomas... comment from Olly; response from Thomas...
<comment> <comment>
initlocation does not create a PG_VERSION file in the specified location. initlocation does not create a PG_VERSION file in the specified location.
How will Postgres handle the situation if it is upgraded to an How will PostgreSQL handle the situation if it is upgraded to an
incompatible database version? incompatible database version?
</comment> </comment>
Hmm. This isn't an issue since the upgrade would do Hmm. This isn't an issue since the upgrade would do
...@@ -287,7 +288,14 @@ comment from Olly; response from Thomas... ...@@ -287,7 +288,14 @@ comment from Olly; response from Thomas...
<programlisting> <programlisting>
<prompt>$</prompt> <userinput>mkdir private_db</userinput> <prompt>$</prompt> <userinput>mkdir private_db</userinput>
<prompt>$</prompt> <userinput>initlocation ~/private_db</userinput> <prompt>$</prompt> <userinput>initlocation ~/private_db</userinput>
<computeroutput>Creating Postgres database system directory /home/olly/private_db/base</computeroutput> <computeroutput>
The location will be initialized with username "olly".
This user will own all the files and must also own the server process.
Creating directory /home/olly/private_db
Creating directory /home/olly/private_db/base
initlocation is complete.
</computeroutput>
<prompt>$</prompt> <userinput>psql olly</userinput> <prompt>$</prompt> <userinput>psql olly</userinput>
<computeroutput> <computeroutput>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.29 2001/11/18 20:35:02 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.30 2001/12/08 03:24:34 thomas Exp $
--> -->
<refentry id="SQL-CREATEFUNCTION"> <refentry id="SQL-CREATEFUNCTION">
...@@ -200,7 +200,7 @@ CREATE [ OR REPLACE ] FUNCTION <replaceable class="parameter">name</replaceable> ...@@ -200,7 +200,7 @@ CREATE [ OR REPLACE ] FUNCTION <replaceable class="parameter">name</replaceable>
Refer to the chapter in the Refer to the chapter in the
<citetitle>PostgreSQL Programmer's Guide</citetitle> <citetitle>PostgreSQL Programmer's Guide</citetitle>
on the topic of extending on the topic of extending
<productname>Postgres</productname> via functions <productname>PostgreSQL</productname> via functions
for further information on writing external functions. for further information on writing external functions.
</para> </para>
...@@ -215,7 +215,7 @@ CREATE [ OR REPLACE ] FUNCTION <replaceable class="parameter">name</replaceable> ...@@ -215,7 +215,7 @@ CREATE [ OR REPLACE ] FUNCTION <replaceable class="parameter">name</replaceable>
</para> </para>
<para> <para>
<productname>Postgres</productname> allows function <firstterm>overloading</firstterm>; <productname>PostgreSQL</productname> allows function <firstterm>overloading</firstterm>;
that is, the same name can be used for several different functions that is, the same name can be used for several different functions
so long as they have distinct argument types. This facility must so long as they have distinct argument types. This facility must
be used with caution for internal and C-language functions, however. be used with caution for internal and C-language functions, however.
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_group.sgml,v 1.5 2001/09/14 07:59:31 ishii Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_group.sgml,v 1.6 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATEGROUP"> <refentry id="SQL-CREATEGROUP">
...@@ -55,7 +55,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be: ...@@ -55,7 +55,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be:
<listitem> <listitem>
<para> <para>
The <literal>SYSID</literal> clause can be used to choose The <literal>SYSID</literal> clause can be used to choose
the <productname>Postgres</productname> group id of the new the <productname>PostgreSQL</productname> group id of the new
group. It is not necessary to do so, however. group. It is not necessary to do so, however.
</para> </para>
<para> <para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.24 2001/09/14 08:05:55 ishii Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.25 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATEINDEX"> <refentry id="SQL-CREATEINDEX">
...@@ -78,7 +78,7 @@ CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable> ...@@ -78,7 +78,7 @@ CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable>
<para> <para>
The name of the access method to be used for The name of the access method to be used for
the index. The default access method is BTREE. the index. The default access method is BTREE.
Postgres provides four access methods for indexes: <application>PostgreSQL</application> provides four access methods for indexes:
<variablelist> <variablelist>
<varlistentry> <varlistentry>
...@@ -236,7 +236,7 @@ ERROR: Cannot create index: 'index_name' already exists. ...@@ -236,7 +236,7 @@ ERROR: Cannot create index: 'index_name' already exists.
</para> </para>
<para> <para>
Postgres provides btree, rtree, hash, and GiST access methods for <application>PostgreSQL</application> provides btree, rtree, hash, and GiST access methods for
indexes. The btree access method is an implementation of indexes. The btree access method is an implementation of
Lehman-Yao high-concurrency btrees. The rtree access method Lehman-Yao high-concurrency btrees. The rtree access method
implements standard rtrees using Guttman's quadratic split algorithm. implements standard rtrees using Guttman's quadratic split algorithm.
...@@ -292,7 +292,7 @@ ERROR: Cannot create index: 'index_name' already exists. ...@@ -292,7 +292,7 @@ ERROR: Cannot create index: 'index_name' already exists.
</title> </title>
<para> <para>
The <productname>Postgres</productname> The <productname>PostgreSQL</productname>
query optimizer will consider using a btree index whenever query optimizer will consider using a btree index whenever
an indexed attribute is involved in a comparison using one of: an indexed attribute is involved in a comparison using one of:
...@@ -306,7 +306,7 @@ ERROR: Cannot create index: 'index_name' already exists. ...@@ -306,7 +306,7 @@ ERROR: Cannot create index: 'index_name' already exists.
</para> </para>
<para> <para>
The <productname>Postgres</productname> The <productname>PostgreSQL</productname>
query optimizer will consider using an rtree index whenever query optimizer will consider using an rtree index whenever
an indexed attribute is involved in a comparison using one of: an indexed attribute is involved in a comparison using one of:
...@@ -322,7 +322,7 @@ ERROR: Cannot create index: 'index_name' already exists. ...@@ -322,7 +322,7 @@ ERROR: Cannot create index: 'index_name' already exists.
</para> </para>
<para> <para>
The <productname>Postgres</productname> The <productname>PostgreSQL</productname>
query optimizer will consider using a hash index whenever query optimizer will consider using a hash index whenever
an indexed attribute is involved in a comparison using an indexed attribute is involved in a comparison using
the <literal>=</literal> operator. the <literal>=</literal> operator.
...@@ -331,7 +331,8 @@ ERROR: Cannot create index: 'index_name' already exists. ...@@ -331,7 +331,8 @@ ERROR: Cannot create index: 'index_name' already exists.
<para> <para>
Currently, only the btree and gist access methods support multi-column Currently, only the btree and gist access methods support multi-column
indexes. Up to 16 keys may be specified by default (this limit indexes. Up to 16 keys may be specified by default (this limit
can be altered when building Postgres). Only btree currently supports can be altered when building
<application>PostgreSQL</application>). Only btree currently supports
unique indexes. unique indexes.
</para> </para>
...@@ -428,7 +429,7 @@ SELECT * FROM points ...@@ -428,7 +429,7 @@ SELECT * FROM points
SQL92 SQL92
</title> </title>
<para> <para>
CREATE INDEX is a <productname>Postgres</productname> language extension. CREATE INDEX is a <productname>PostgreSQL</productname> language extension.
</para> </para>
<para> <para>
There is no <command>CREATE INDEX</command> command in SQL92. There is no <command>CREATE INDEX</command> command in SQL92.
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_language.sgml,v 1.19 2001/11/18 20:35:02 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_language.sgml,v 1.20 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATELANGUAGE"> <refentry id="SQL-CREATELANGUAGE">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.21 2001/09/13 15:55:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.22 2001/12/08 03:24:34 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATEOPERATOR"> <refentry id="SQL-CREATEOPERATOR">
...@@ -205,7 +205,7 @@ CREATE ...@@ -205,7 +205,7 @@ CREATE
</literallayout> </literallayout>
For example, <literal>@-</literal> is an allowed operator name, For example, <literal>@-</literal> is an allowed operator name,
but <literal>*-</literal> is not. but <literal>*-</literal> is not.
This restriction allows <productname>Postgres</productname> to This restriction allows <productname>PostgreSQL</productname> to
parse SQL-compliant queries without requiring spaces between tokens. parse SQL-compliant queries without requiring spaces between tokens.
</para> </para>
</listitem> </listitem>
...@@ -218,7 +218,7 @@ CREATE ...@@ -218,7 +218,7 @@ CREATE
For example, if you have defined a left-unary operator named <literal>@</literal>, For example, if you have defined a left-unary operator named <literal>@</literal>,
you cannot write <literal>X*@Y</literal>; you must write you cannot write <literal>X*@Y</literal>; you must write
<literal>X* @Y</literal> to ensure that <literal>X* @Y</literal> to ensure that
<productname>Postgres</productname> reads it as two operator names <productname>PostgreSQL</productname> reads it as two operator names
not one. not one.
</para> </para>
</note> </note>
...@@ -242,7 +242,7 @@ CREATE ...@@ -242,7 +242,7 @@ CREATE
</para> </para>
<para> <para>
The commutator operator should be identified if one exists, The commutator operator should be identified if one exists,
so that <productname>Postgres</productname> can so that <productname>PostgreSQL</productname> can
reverse the order of the operands if it wishes. reverse the order of the operands if it wishes.
For example, the operator area-less-than, &lt;&lt;&lt;, For example, the operator area-less-than, &lt;&lt;&lt;,
would probably have a commutator would probably have a commutator
...@@ -280,7 +280,7 @@ MYBOXES.description !== box '((0,0), (1,1))' ...@@ -280,7 +280,7 @@ MYBOXES.description !== box '((0,0), (1,1))'
</para> </para>
<para> <para>
If a commutator operator name is supplied, If a commutator operator name is supplied,
<productname>Postgres</productname> <productname>PostgreSQL</productname>
searches for it in the catalog. If it is found and it searches for it in the catalog. If it is found and it
does not yet have a commutator itself, then the commutator's does not yet have a commutator itself, then the commutator's
entry is updated to have the newly created operator as its entry is updated to have the newly created operator as its
...@@ -290,17 +290,18 @@ MYBOXES.description !== box '((0,0), (1,1))' ...@@ -290,17 +290,18 @@ MYBOXES.description !== box '((0,0), (1,1))'
operator should be defined without a commutator or negator operator should be defined without a commutator or negator
(as appropriate). When the second operator is defined, (as appropriate). When the second operator is defined,
name the first as the commutator or negator. The first name the first as the commutator or negator. The first
will be updated as a side effect. (As of Postgres 6.5, will be updated as a side effect. (As of
<application>PostgreSQL</application> <literal>6.5</literal>,
it also works to just have both operators refer to each other.) it also works to just have both operators refer to each other.)
</para> </para>
<para> <para>
The HASHES, SORT1, and SORT2 options are present to support the The HASHES, SORT1, and SORT2 options are present to support the
query optimizer in performing joins. query optimizer in performing joins.
<productname>Postgres</productname> can always <productname>PostgreSQL</productname> can always
evaluate a join (i.e., processing a clause with two tuple evaluate a join (i.e., processing a clause with two tuple
variables separated by an operator that returns a boolean) variables separated by an operator that returns a boolean)
by iterative substitution [WONG76]. by iterative substitution [WONG76].
In addition, <productname>Postgres</productname> In addition, <productname>PostgreSQL</productname>
can use a hash-join algorithm along can use a hash-join algorithm along
the lines of [SHAP86]; however, it must know whether this the lines of [SHAP86]; however, it must know whether this
strategy is applicable. The current hash-join algorithm strategy is applicable. The current hash-join algorithm
...@@ -321,7 +322,7 @@ MYBOXES.description !== box '((0,0), (1,1))' ...@@ -321,7 +322,7 @@ MYBOXES.description !== box '((0,0), (1,1))'
</para> </para>
<para> <para>
If other join strategies are found to be practical, If other join strategies are found to be practical,
<productname>Postgres</productname> <productname>PostgreSQL</productname>
will change the optimizer and run-time system to use will change the optimizer and run-time system to use
them and will require additional specification when an them and will require additional specification when an
operator is defined. Fortunately, the research community operator is defined. Fortunately, the research community
...@@ -336,7 +337,7 @@ MYBOXES.description !== box '((0,0), (1,1))' ...@@ -336,7 +337,7 @@ MYBOXES.description !== box '((0,0), (1,1))'
MYBOXES.description &lt;&lt;&lt; box '((0,0), (1,1))' MYBOXES.description &lt;&lt;&lt; box '((0,0), (1,1))'
</programlisting> </programlisting>
is present in the qualification, is present in the qualification,
then <productname>Postgres</productname> may have to then <productname>PostgreSQL</productname> may have to
estimate the fraction of the instances in MYBOXES that estimate the fraction of the instances in MYBOXES that
satisfy the clause. The function satisfy the clause. The function
<replaceable class="parameter">res_proc</replaceable> <replaceable class="parameter">res_proc</replaceable>
...@@ -364,7 +365,7 @@ my_procedure_1 (MYBOXES.description, box '((0,0), (1,1))') ...@@ -364,7 +365,7 @@ my_procedure_1 (MYBOXES.description, box '((0,0), (1,1))')
<programlisting> <programlisting>
MYBOXES.description === box '((0,0), (1,1))' MYBOXES.description === box '((0,0), (1,1))'
</programlisting> </programlisting>
is that <productname>Postgres</productname> is that <productname>PostgreSQL</productname>
attempts to optimize operators and can attempts to optimize operators and can
decide to use an index to restrict the search space when decide to use an index to restrict the search space when
operators are involved. However, there is no attempt to operators are involved. However, there is no attempt to
...@@ -428,7 +429,7 @@ CREATE OPERATOR === ( ...@@ -428,7 +429,7 @@ CREATE OPERATOR === (
<para> <para>
<command>CREATE OPERATOR</command> <command>CREATE OPERATOR</command>
is a <productname>Postgres</productname> extension. is a <productname>PostgreSQL</productname> extension.
There is no <command>CREATE OPERATOR</command> There is no <command>CREATE OPERATOR</command>
statement in <acronym>SQL92</acronym>. statement in <acronym>SQL92</acronym>.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_rule.sgml,v 1.29 2001/11/06 23:54:32 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_rule.sgml,v 1.30 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATERULE"> <refentry id="SQL-CREATERULE">
...@@ -148,7 +148,7 @@ CREATE ...@@ -148,7 +148,7 @@ CREATE
</title> </title>
<para> <para>
The <productname>Postgres</productname> The <productname>PostgreSQL</productname>
<firstterm>rule system</firstterm> allows one to define an <firstterm>rule system</firstterm> allows one to define an
alternate action to be performed on inserts, updates, or deletions alternate action to be performed on inserts, updates, or deletions
from database tables. Rules are used to from database tables. Rules are used to
...@@ -255,8 +255,8 @@ CREATE ...@@ -255,8 +255,8 @@ CREATE
It is very important to take care to avoid circular rules. It is very important to take care to avoid circular rules.
For example, though each For example, though each
of the following two rule definitions are accepted by of the following two rule definitions are accepted by
<productname>Postgres</productname>, the <productname>PostgreSQL</productname>, the
select command will cause <productname>Postgres</productname> to select command will cause <productname>PostgreSQL</productname> to
report an error because the query cycled too many times: report an error because the query cycled too many times:
<programlisting> <programlisting>
...@@ -272,7 +272,7 @@ CREATE RULE "_RETtoyemp" AS ...@@ -272,7 +272,7 @@ CREATE RULE "_RETtoyemp" AS
</programlisting> </programlisting>
This attempt to select from EMP will cause This attempt to select from EMP will cause
<productname>Postgres</productname> to issue an error <productname>PostgreSQL</productname> to issue an error
because the queries cycled too many times: because the queries cycled too many times:
<programlisting> <programlisting>
...@@ -310,7 +310,7 @@ UPDATE mytable SET name = 'foo' WHERE id = 42; ...@@ -310,7 +310,7 @@ UPDATE mytable SET name = 'foo' WHERE id = 42;
</title> </title>
<para> <para>
<command>CREATE RULE</command> statement is a <productname>Postgres</productname> <command>CREATE RULE</command> statement is a <productname>PostgreSQL</productname>
language extension. language extension.
There is no <command>CREATE RULE</command> statement in <acronym>SQL92</acronym>. There is no <command>CREATE RULE</command> statement in <acronym>SQL92</acronym>.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.22 2001/11/28 15:33:48 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.23 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATESEQUENCE"> <refentry id="SQL-CREATESEQUENCE">
...@@ -362,7 +362,7 @@ END; ...@@ -362,7 +362,7 @@ END;
</title> </title>
<para> <para>
<command>CREATE SEQUENCE</command> is a <productname>Postgres</productname> <command>CREATE SEQUENCE</command> is a <productname>PostgreSQL</productname>
language extension. language extension.
There is no <command>CREATE SEQUENCE</command> statement There is no <command>CREATE SEQUENCE</command> statement
in <acronym>SQL92</acronym>. in <acronym>SQL92</acronym>.
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.49 2001/11/18 20:35:02 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.50 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATETABLE"> <refentry id="SQL-CREATETABLE">
...@@ -186,7 +186,8 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is: ...@@ -186,7 +186,8 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
</para> </para>
<!-- <!--
<para> <para>
Postgres automatically allows the created table to inherit <application>PostgreSQL</application> automatically allows the
created table to inherit
functions on tables above it in the inheritance hierarchy; that functions on tables above it in the inheritance hierarchy; that
is, if we create table <literal>foo</literal> inheriting from is, if we create table <literal>foo</literal> inheriting from
<literal>bar</literal>, then functions that accept the tuple <literal>bar</literal>, then functions that accept the tuple
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.8 2001/10/22 18:14:47 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.9 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATETABLEAS"> <refentry id="SQL-CREATETABLEAS">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.20 2001/11/30 01:22:47 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.21 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATETRIGGER"> <refentry id="SQL-CREATETRIGGER">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.24 2001/11/03 21:42:47 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.25 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATETYPE"> <refentry id="SQL-CREATETYPE">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_user.sgml,v 1.21 2001/09/21 20:31:45 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_user.sgml,v 1.22 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATEUSER"> <refentry id="SQL-CREATEUSER">
...@@ -59,7 +59,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be: ...@@ -59,7 +59,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be:
<listitem> <listitem>
<para> <para>
The <literal>SYSID</literal> clause can be used to choose The <literal>SYSID</literal> clause can be used to choose
the <productname>Postgres</productname> user id of the user the <productname>PostgreSQL</productname> user id of the user
that is being created. It is not at all necessary that those that is being created. It is not at all necessary that those
match the <acronym>UNIX</acronym> user ids, but some people match the <acronym>UNIX</acronym> user ids, but some people
choose to keep the numbers the same. choose to keep the numbers the same.
...@@ -193,7 +193,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be: ...@@ -193,7 +193,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be:
</title> </title>
<para> <para>
<command>CREATE USER</command> will add a new user to an instance of <command>CREATE USER</command> will add a new user to an instance of
<productname>Postgres</productname>. Refer to the administrator's <productname>PostgreSQL</productname>. Refer to the administrator's
guide for information about managing users and authentication. guide for information about managing users and authentication.
You must be a database superuser to use this command. You must be a database superuser to use this command.
</para> </para>
...@@ -203,7 +203,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be: ...@@ -203,7 +203,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be:
endterm="SQL-DROPUSER-title"> to remove a user. endterm="SQL-DROPUSER-title"> to remove a user.
Use <xref linkend="SQL-ALTERGROUP" endterm="SQL-ALTERGROUP-title"> Use <xref linkend="SQL-ALTERGROUP" endterm="SQL-ALTERGROUP-title">
to add or remove the user from other groups. to add or remove the user from other groups.
<productname>Postgres</productname> <productname>PostgreSQL</productname>
comes with a script <xref linkend="APP-CREATEUSER" comes with a script <xref linkend="APP-CREATEUSER"
endterm="APP-CREATEUSER-title"> endterm="APP-CREATEUSER-title">
which has the same functionality as this command (in fact, it calls this command) which has the same functionality as this command (in fact, it calls this command)
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_view.sgml,v 1.13 2001/11/06 23:54:32 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_view.sgml,v 1.14 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-CREATEVIEW"> <refentry id="SQL-CREATEVIEW">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.22 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.23 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-CREATEDB"> <refentry id="APP-CREATEDB">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/createlang.sgml,v 1.20 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/createlang.sgml,v 1.21 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-CREATELANG"> <refentry id="APP-CREATELANG">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.21 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.22 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-CREATEUSER"> <refentry id="APP-CREATEUSER">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_time.sgml,v 1.4 1999/07/22 15:09:09 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_time.sgml,v 1.5 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<REFENTRY ID="SQL-CURRENT-TIME"> <REFENTRY ID="SQL-CURRENT-TIME">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_timestamp.sgml,v 1.4 1999/07/22 15:09:09 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_timestamp.sgml,v 1.5 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<REFENTRY ID="SQL-CURRENT-TIMESTAMP"> <REFENTRY ID="SQL-CURRENT-TIMESTAMP">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_user.sgml,v 1.4 1999/07/22 15:09:09 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_user.sgml,v 1.5 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<REFENTRY ID="SQL-CURRENT-USER"> <REFENTRY ID="SQL-CURRENT-USER">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.14 2001/09/13 15:55:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.15 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DECLARE"> <refentry id="SQL-DECLARE">
...@@ -62,7 +62,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS ...@@ -62,7 +62,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS
<acronym>SQL92</acronym> keyword indicating that data retrieved <acronym>SQL92</acronym> keyword indicating that data retrieved
from the cursor should be unaffected by updates from other processes or cursors. from the cursor should be unaffected by updates from other processes or cursors.
Since cursor operations occur within transactions Since cursor operations occur within transactions
in <productname>Postgres</productname> this is always the case. in <productname>PostgreSQL</productname> this is always the case.
This keyword has no effect. This keyword has no effect.
</para> </para>
</listitem> </listitem>
...@@ -74,7 +74,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS ...@@ -74,7 +74,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS
<para> <para>
<acronym>SQL92</acronym> keyword indicating that data may be retrieved <acronym>SQL92</acronym> keyword indicating that data may be retrieved
in multiple rows per FETCH operation. Since this is allowed at all times in multiple rows per FETCH operation. Since this is allowed at all times
by <productname>Postgres</productname> this keyword has no effect. by <productname>PostgreSQL</productname> this keyword has no effect.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -97,7 +97,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS ...@@ -97,7 +97,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS
<para> <para>
<acronym>SQL92</acronym> keyword indicating that the cursor will be used <acronym>SQL92</acronym> keyword indicating that the cursor will be used
in a read only mode. Since this is the only cursor access mode in a read only mode. Since this is the only cursor access mode
available in <productname>Postgres</productname> this keyword has no effect. available in <productname>PostgreSQL</productname> this keyword has no effect.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -108,7 +108,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS ...@@ -108,7 +108,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS
<para> <para>
<acronym>SQL92</acronym> keyword indicating that the cursor will be used <acronym>SQL92</acronym> keyword indicating that the cursor will be used
to update tables. Since cursor updates are not currently to update tables. Since cursor updates are not currently
supported in <productname>Postgres</productname> this keyword supported in <productname>PostgreSQL</productname> this keyword
provokes an informational error message. provokes an informational error message.
</para> </para>
</listitem> </listitem>
...@@ -120,7 +120,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS ...@@ -120,7 +120,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS
<para> <para>
Column(s) to be updated. Column(s) to be updated.
Since cursor updates are not currently Since cursor updates are not currently
supported in <productname>Postgres</productname> the UPDATE clause supported in <productname>PostgreSQL</productname> the UPDATE clause
provokes an informational error message. provokes an informational error message.
</para> </para>
</listitem> </listitem>
...@@ -196,7 +196,7 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks ...@@ -196,7 +196,7 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks
<para> <para>
Normal cursors return data in text format, either ASCII or another Normal cursors return data in text format, either ASCII or another
encoding scheme depending on how the <productname>Postgres</productname> encoding scheme depending on how the <productname>PostgreSQL</productname>
backend was built. Since backend was built. Since
data is stored natively in binary format, the system must data is stored natively in binary format, the system must
do a conversion to produce the text format. In addition, do a conversion to produce the text format. In addition,
...@@ -224,7 +224,7 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks ...@@ -224,7 +224,7 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks
<para> <para>
String representation is architecture-neutral whereas binary String representation is architecture-neutral whereas binary
representation can differ between different machine architectures. representation can differ between different machine architectures.
<emphasis><productname>Postgres</productname> does not resolve <emphasis><productname>PostgreSQL</productname> does not resolve
byte ordering or representation issues for binary cursors</emphasis>. byte ordering or representation issues for binary cursors</emphasis>.
Therefore, if your client machine and server machine use different Therefore, if your client machine and server machine use different
representations (e.g., <quote>big-endian</quote> versus <quote>little-endian</quote>), representations (e.g., <quote>big-endian</quote> versus <quote>little-endian</quote>),
...@@ -263,11 +263,11 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks ...@@ -263,11 +263,11 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks
<para> <para>
In <acronym>SQL92</acronym> cursors are only available in In <acronym>SQL92</acronym> cursors are only available in
embedded <acronym>SQL</acronym> (<acronym>ESQL</acronym>) applications. embedded <acronym>SQL</acronym> (<acronym>ESQL</acronym>) applications.
The <productname>Postgres</productname> backend The <productname>PostgreSQL</productname> backend
does not implement an explicit <command>OPEN cursor</command> does not implement an explicit <command>OPEN cursor</command>
statement; a cursor is considered to be open when it is declared. statement; a cursor is considered to be open when it is declared.
However, <application>ecpg</application>, the However, <application>ecpg</application>, the
embedded SQL preprocessor for <productname>Postgres</productname>, embedded SQL preprocessor for <productname>PostgreSQL</productname>,
supports the <acronym>SQL92</acronym> cursor conventions, including those supports the <acronym>SQL92</acronym> cursor conventions, including those
involving DECLARE and OPEN statements. involving DECLARE and OPEN statements.
</para> </para>
...@@ -302,12 +302,12 @@ DECLARE liahona CURSOR ...@@ -302,12 +302,12 @@ DECLARE liahona CURSOR
</title> </title>
<para> <para>
<acronym>SQL92</acronym> allows cursors only in embedded <acronym>SQL</acronym> <acronym>SQL92</acronym> allows cursors only in embedded <acronym>SQL</acronym>
and in modules. <productname>Postgres</productname> permits cursors to be used and in modules. <productname>PostgreSQL</productname> permits cursors to be used
interactively. interactively.
<acronym>SQL92</acronym> allows embedded or modular cursors to <acronym>SQL92</acronym> allows embedded or modular cursors to
update database information. update database information.
All <productname>Postgres</productname> cursors are read only. All <productname>PostgreSQL</productname> cursors are read only.
The BINARY keyword is a <productname>Postgres</productname> extension. The BINARY keyword is a <productname>PostgreSQL</productname> extension.
</para> </para>
</refsect2> </refsect2>
</refsect1> </refsect1>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/delete.sgml,v 1.14 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/delete.sgml,v 1.15 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DELETE"> <refentry id="SQL-DELETE">
...@@ -110,7 +110,7 @@ DELETE <replaceable class="parameter">count</replaceable> ...@@ -110,7 +110,7 @@ DELETE <replaceable class="parameter">count</replaceable>
<tip> <tip>
<para> <para>
<xref linkend="sql-truncate" endterm="sql-truncate-title"> is a <xref linkend="sql-truncate" endterm="sql-truncate-title"> is a
<productname>Postgres</productname> extension which provides a <productname>PostgreSQL</productname> extension which provides a
faster mechanism to remove all rows from a table. faster mechanism to remove all rows from a table.
</para> </para>
</tip> </tip>
...@@ -187,7 +187,7 @@ DELETE FROM <replaceable class="parameter">table</replaceable> WHERE ...@@ -187,7 +187,7 @@ DELETE FROM <replaceable class="parameter">table</replaceable> WHERE
where <replaceable class="parameter">cursor</replaceable> where <replaceable class="parameter">cursor</replaceable>
identifies an open cursor. identifies an open cursor.
Interactive cursors in <productname>Postgres</productname> are read-only. Interactive cursors in <productname>PostgreSQL</productname> are read-only.
</para> </para>
</refsect2> </refsect2>
</refsect1> </refsect1>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_aggregate.sgml,v 1.13 2001/10/03 20:54:20 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_aggregate.sgml,v 1.14 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPAGGREGATE"> <refentry id="SQL-DROPAGGREGATE">
...@@ -153,7 +153,7 @@ DROP AGGREGATE myavg(int4); ...@@ -153,7 +153,7 @@ DROP AGGREGATE myavg(int4);
<para> <para>
There is no <command>DROP AGGREGATE</command> statement There is no <command>DROP AGGREGATE</command> statement
in <acronym>SQL92</acronym>; the statement is a in <acronym>SQL92</acronym>; the statement is a
<productname>Postgres</productname> <productname>PostgreSQL</productname>
language extension. language extension.
</para> </para>
</refsect2> </refsect2>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_database.sgml,v 1.13 2001/11/18 00:38:00 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_database.sgml,v 1.14 2001/12/08 03:24:35 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPDATABASE"> <refentry id="SQL-DROPDATABASE">
...@@ -148,7 +148,7 @@ DROP DATABASE <replaceable class="PARAMETER">name</replaceable> ...@@ -148,7 +148,7 @@ DROP DATABASE <replaceable class="PARAMETER">name</replaceable>
<para> <para>
<command>DROP DATABASE</command> statement is a <command>DROP DATABASE</command> statement is a
<productname>Postgres</productname> language extension; <productname>PostgreSQL</productname> language extension;
there is no such command in <acronym>SQL92</acronym>. there is no such command in <acronym>SQL92</acronym>.
</para> </para>
</refsect2> </refsect2>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_function.sgml,v 1.15 2001/11/19 03:58:25 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_function.sgml,v 1.16 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPFUNCTION"> <refentry id="SQL-DROPFUNCTION">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_group.sgml,v 1.2 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_group.sgml,v 1.3 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPGROUP"> <refentry id="SQL-DROPGROUP">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_index.sgml,v 1.11 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_index.sgml,v 1.12 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPINDEX"> <refentry id="SQL-DROPINDEX">
...@@ -103,7 +103,7 @@ ERROR: index "<replaceable class="PARAMETER">index_name</replaceable>" does not ...@@ -103,7 +103,7 @@ ERROR: index "<replaceable class="PARAMETER">index_name</replaceable>" does not
Notes Notes
</title> </title>
<para> <para>
<command>DROP INDEX</command> is a <productname>Postgres</productname> <command>DROP INDEX</command> is a <productname>PostgreSQL</productname>
language extension. language extension.
</para> </para>
<para> <para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_language.sgml,v 1.12 2001/10/26 21:17:03 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_language.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPLANGUAGE"> <refentry id="SQL-DROPLANGUAGE">
...@@ -105,7 +105,7 @@ ERROR: Language "<replaceable class="parameter">name</replaceable>" doesn't exis ...@@ -105,7 +105,7 @@ ERROR: Language "<replaceable class="parameter">name</replaceable>" doesn't exis
</title> </title>
<para> <para>
The <command>DROP PROCEDURAL LANGUAGE</command> statement is The <command>DROP PROCEDURAL LANGUAGE</command> statement is
a <productname>Postgres</productname> language extension. a <productname>PostgreSQL</productname> language extension.
</para> </para>
<para> <para>
Refer to Refer to
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_operator.sgml,v 1.11 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_operator.sgml,v 1.12 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPOPERATOR"> <refentry id="SQL-DROPOPERATOR">
...@@ -149,7 +149,7 @@ ERROR: RemoveOperator: right unary operator '<replaceable class="PARAMETER">oper ...@@ -149,7 +149,7 @@ ERROR: RemoveOperator: right unary operator '<replaceable class="PARAMETER">oper
</title> </title>
<para> <para>
The <command>DROP OPERATOR</command> statement is a The <command>DROP OPERATOR</command> statement is a
<productname>Postgres</productname> <productname>PostgreSQL</productname>
language extension. language extension.
</para> </para>
<para> <para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_rule.sgml,v 1.10 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_rule.sgml,v 1.11 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPRULE"> <refentry id="SQL-DROPRULE">
...@@ -90,8 +90,8 @@ ERROR: Rule or view "<replaceable class="parameter">name</replaceable>" not fou ...@@ -90,8 +90,8 @@ ERROR: Rule or view "<replaceable class="parameter">name</replaceable>" not fou
</title> </title>
<para> <para>
<command>DROP RULE</command> drops a rule from the specified <command>DROP RULE</command> drops a rule from the specified
<productname>Postgres</productname> rule <productname>PostgreSQL</productname> rule
system. <productname>Postgres</productname> system. <productname>PostgreSQL</productname>
will immediately cease enforcing it and will immediately cease enforcing it and
will purge its definition from the system catalogs. will purge its definition from the system catalogs.
</para> </para>
...@@ -105,7 +105,7 @@ ERROR: Rule or view "<replaceable class="parameter">name</replaceable>" not fou ...@@ -105,7 +105,7 @@ ERROR: Rule or view "<replaceable class="parameter">name</replaceable>" not fou
</title> </title>
<para> <para>
The <command>DROP RULE</command> statement is a The <command>DROP RULE</command> statement is a
<productname>Postgres</productname> <productname>PostgreSQL</productname>
language extension. language extension.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_sequence.sgml,v 1.10 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_sequence.sgml,v 1.11 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPSEQUENCE"> <refentry id="SQL-DROPSEQUENCE">
...@@ -105,7 +105,7 @@ ERROR: sequence "<replaceable class="parameter">name</replaceable>" does not exi ...@@ -105,7 +105,7 @@ ERROR: sequence "<replaceable class="parameter">name</replaceable>" does not exi
</title> </title>
<para> <para>
The <command>DROP SEQUENCE</command> statement is a The <command>DROP SEQUENCE</command> statement is a
<productname>Postgres</productname> <productname>PostgreSQL</productname>
language extension. language extension.
</para> </para>
<para> <para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_table.sgml,v 1.11 2001/09/03 12:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_table.sgml,v 1.12 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPTABLE"> <refentry id="SQL-DROPTABLE">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_trigger.sgml,v 1.8 2001/09/13 18:17:44 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_trigger.sgml,v 1.9 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPTRIGGER"> <refentry id="SQL-DROPTRIGGER">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.12 2001/11/03 21:42:47 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPTYPE"> <refentry id="SQL-DROPTYPE">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_user.sgml,v 1.12 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_user.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPUSER"> <refentry id="SQL-DROPUSER">
...@@ -109,7 +109,7 @@ DROP USER: user "<replaceable class="parameter">name</replaceable>" owns databas ...@@ -109,7 +109,7 @@ DROP USER: user "<replaceable class="parameter">name</replaceable>" owns databas
Use <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title"> Use <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title">
to add new users, and <xref linkend="SQL-ALTERUSER" to add new users, and <xref linkend="SQL-ALTERUSER"
endterm="SQL-ALTERUSER-title"> to change a user's properties. endterm="SQL-ALTERUSER-title"> to change a user's properties.
<productname>Postgres</productname> <productname>PostgreSQL</productname>
comes with a script <xref linkend="APP-DROPUSER" comes with a script <xref linkend="APP-DROPUSER"
endterm="APP-DROPUSER-title"> endterm="APP-DROPUSER-title">
which has the same functionality as this command (in fact, it calls this command) which has the same functionality as this command (in fact, it calls this command)
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_view.sgml,v 1.10 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_view.sgml,v 1.11 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-DROPVIEW"> <refentry id="SQL-DROPVIEW">
...@@ -184,7 +184,7 @@ DROP VIEW <replaceable class="parameter">view</replaceable> { RESTRICT | CASCADE ...@@ -184,7 +184,7 @@ DROP VIEW <replaceable class="parameter">view</replaceable> { RESTRICT | CASCADE
</title> </title>
<para> <para>
At present, to remove a referenced view from a At present, to remove a referenced view from a
<productname>Postgres</productname> database, <productname>PostgreSQL</productname> database,
you must drop it explicitly. you must drop it explicitly.
</para> </para>
</refsect3> </refsect3>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.12 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-DROPDB"> <refentry id="APP-DROPDB">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/droplang.sgml,v 1.14 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/droplang.sgml,v 1.15 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-DROPLANG"> <refentry id="APP-DROPLANG">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.14 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.15 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-DROPUSER"> <refentry id="APP-DROPUSER">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.13 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.14 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-ECPG"> <refentry id="APP-ECPG">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.5 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.6 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-END"> <refentry id="SQL-END">
...@@ -94,7 +94,7 @@ NOTICE: COMMIT: no transaction in progress ...@@ -94,7 +94,7 @@ NOTICE: COMMIT: no transaction in progress
</title> </title>
<para> <para>
<command>END</command> is a <productname>Postgres</productname> <command>END</command> is a <productname>PostgreSQL</productname>
extension, and is a synonym for the SQL92-compatible extension, and is a synonym for the SQL92-compatible
<xref linkend="sql-commit" endterm="sql-commit-title">. <xref linkend="sql-commit" endterm="sql-commit-title">.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/explain.sgml,v 1.13 2001/09/18 01:59:05 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/explain.sgml,v 1.14 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-EXPLAIN"> <refentry id="SQL-EXPLAIN">
...@@ -82,7 +82,7 @@ NOTICE: QUERY PLAN: ...@@ -82,7 +82,7 @@ NOTICE: QUERY PLAN:
</computeroutput></term> </computeroutput></term>
<listitem> <listitem>
<para> <para>
Explicit query plan from the <productname>Postgres</productname> backend. Explicit query plan from the <productname>PostgreSQL</productname> backend.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -110,7 +110,8 @@ EXPLAIN ...@@ -110,7 +110,8 @@ EXPLAIN
</title> </title>
<para> <para>
This command displays the execution plan that the Postgres planner This command displays the execution plan that the
<application>PostgreSQL</application> planner
generates for the supplied query. The execution plan shows how generates for the supplied query. The execution plan shows how
the table(s) referenced by the query will be scanned---by plain the table(s) referenced by the query will be scanned---by plain
sequential scan, index scan, etc.---and if multiple tables are sequential scan, index scan, etc.---and if multiple tables are
...@@ -143,7 +144,8 @@ EXPLAIN ...@@ -143,7 +144,8 @@ EXPLAIN
<para> <para>
The VERBOSE option emits the full internal representation of the plan tree, The VERBOSE option emits the full internal representation of the plan tree,
rather than just a summary (and sends it to the postmaster log file, too). rather than just a summary (and sends it to the postmaster log file, too).
Usually this option is only useful for debugging Postgres. Usually this option is only useful for debugging
<application>PostgreSQL</application>.
</para> </para>
<caution> <caution>
...@@ -172,7 +174,7 @@ ROLLBACK; ...@@ -172,7 +174,7 @@ ROLLBACK;
</title> </title>
<para> <para>
There is only sparse documentation on the optimizer's use of cost There is only sparse documentation on the optimizer's use of cost
information in <productname>Postgres</productname>. information in <productname>PostgreSQL</productname>.
Refer to the <citetitle>User's Guide</citetitle> and Refer to the <citetitle>User's Guide</citetitle> and
<citetitle>Programmer's Guide</citetitle> for more information. <citetitle>Programmer's Guide</citetitle> for more information.
</para> </para>
...@@ -236,7 +238,8 @@ Aggregate (cost=0.42..0.42 rows=1 width=4) ...@@ -236,7 +238,8 @@ Aggregate (cost=0.42..0.42 rows=1 width=4)
<para> <para>
Note that the specific numbers shown, and even the selected query Note that the specific numbers shown, and even the selected query
strategy, may vary between Postgres releases due to planner improvements. strategy, may vary between <application>PostgreSQL</application>
releases due to planner improvements.
</para> </para>
</refsect1> </refsect1>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.16 2001/09/13 15:55:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.17 2001/12/08 03:24:36 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-FETCH"> <refentry id="SQL-FETCH">
...@@ -175,7 +175,7 @@ NOTICE: FETCH/ABSOLUTE not supported, using RELATIVE ...@@ -175,7 +175,7 @@ NOTICE: FETCH/ABSOLUTE not supported, using RELATIVE
</computeroutput></term> </computeroutput></term>
<listitem> <listitem>
<para> <para>
<productname>Postgres</productname> does not support absolute <productname>PostgreSQL</productname> does not support absolute
positioning of cursors. positioning of cursors.
</para> </para>
</listitem> </listitem>
...@@ -195,10 +195,10 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>. ...@@ -195,10 +195,10 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>.
</para> </para>
<para> <para>
<productname>Postgres</productname> does not currently support <productname>PostgreSQL</productname> does not currently support
this notion; in fact the value zero is reserved to indicate that this notion; in fact the value zero is reserved to indicate that
all rows should be retrieved and is equivalent to specifying the ALL keyword. all rows should be retrieved and is equivalent to specifying the ALL keyword.
If the RELATIVE keyword has been used, <productname>Postgres</productname> If the RELATIVE keyword has been used, <productname>PostgreSQL</productname>
assumes that the user intended <acronym>SQL92</acronym> behavior assumes that the user intended <acronym>SQL92</acronym> behavior
and returns this error message. and returns this error message.
</para> </para>
...@@ -250,7 +250,7 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>. ...@@ -250,7 +250,7 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>.
<para> <para>
Note that the FORWARD and BACKWARD keywords are Note that the FORWARD and BACKWARD keywords are
<productname>Postgres</productname> extensions. <productname>PostgreSQL</productname> extensions.
The <acronym>SQL92</acronym> syntax is also supported, specified The <acronym>SQL92</acronym> syntax is also supported, specified
in the second form of the command. See below for details in the second form of the command. See below for details
on compatibility issues. on compatibility issues.
...@@ -258,7 +258,7 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>. ...@@ -258,7 +258,7 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>.
<para> <para>
Updating data in a cursor is not supported by Updating data in a cursor is not supported by
<productname>Postgres</productname>, <productname>PostgreSQL</productname>,
because mapping cursor updates back to base tables is because mapping cursor updates back to base tables is
not generally possible, as is also the case with VIEW updates. not generally possible, as is also the case with VIEW updates.
Consequently, Consequently,
...@@ -346,7 +346,7 @@ COMMIT WORK; ...@@ -346,7 +346,7 @@ COMMIT WORK;
<para> <para>
<note> <note>
<para> <para>
The non-embedded use of cursors is a <productname>Postgres</productname> The non-embedded use of cursors is a <productname>PostgreSQL</productname>
extension. The syntax and usage of cursors is being compared extension. The syntax and usage of cursors is being compared
against the embedded form of cursors defined in <acronym>SQL92</acronym>. against the embedded form of cursors defined in <acronym>SQL92</acronym>.
</para> </para>
...@@ -369,7 +369,7 @@ FETCH ABSOLUTE <replaceable class="PARAMETER">#</replaceable> ...@@ -369,7 +369,7 @@ FETCH ABSOLUTE <replaceable class="PARAMETER">#</replaceable>
<listitem> <listitem>
<para> <para>
The cursor should be positioned to the specified absolute The cursor should be positioned to the specified absolute
row number. All row numbers in <productname>Postgres</productname> row number. All row numbers in <productname>PostgreSQL</productname>
are relative numbers so this capability is not supported. are relative numbers so this capability is not supported.
</para> </para>
</listitem> </listitem>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.16 2001/11/19 19:03:56 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.17 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-GRANT"> <refentry id="SQL-GRANT">
...@@ -155,7 +155,7 @@ GRANT { { SELECT | INSERT | UPDATE | DELETE | RULE | REFERENCES | TRIGGER } [,.. ...@@ -155,7 +155,7 @@ GRANT { { SELECT | INSERT | UPDATE | DELETE | RULE | REFERENCES | TRIGGER } [,..
<title>Notes</title> <title>Notes</title>
<para> <para>
Currently, to grant privileges in <productname>Postgres</productname> Currently, to grant privileges in <productname>PostgreSQL</productname>
to only a few columns, you must to only a few columns, you must
create a view having the desired columns and then grant privileges create a view having the desired columns and then grant privileges
to that view. to that view.
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/initdb.sgml,v 1.18 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/initdb.sgml,v 1.19 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-INITDB"> <refentry id="APP-INITDB">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/initlocation.sgml,v 1.13 2001/09/13 15:55:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/initlocation.sgml,v 1.14 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-INITLOCATION"> <refentry id="APP-INITLOCATION">
...@@ -30,7 +30,7 @@ Postgres documentation ...@@ -30,7 +30,7 @@ Postgres documentation
<title>Description</title> <title>Description</title>
<para> <para>
<application>initlocation</application> <application>initlocation</application>
creates a new <productname>Postgres</productname> secondary database storage area. creates a new <productname>PostgreSQL</productname> secondary database storage area.
See the discussion under <xref linkend="SQL-CREATEDATABASE" endterm="SQL-CREATEDATABASE-title"> See the discussion under <xref linkend="SQL-CREATEDATABASE" endterm="SQL-CREATEDATABASE-title">
about how to manage and use secondary storage areas. If the argument does not contain about how to manage and use secondary storage areas. If the argument does not contain
a slash and is not valid as a path, it is assumed to be an environment variable, a slash and is not valid as a path, it is assumed to be an environment variable,
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/insert.sgml,v 1.15 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/insert.sgml,v 1.16 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-INSERT"> <refentry id="SQL-INSERT">
...@@ -135,7 +135,7 @@ INSERT 0 <replaceable>#</replaceable> ...@@ -135,7 +135,7 @@ INSERT 0 <replaceable>#</replaceable>
<para> <para>
Each column not present in the target list will be inserted Each column not present in the target list will be inserted
using a default value, either a declared DEFAULT value using a default value, either a declared DEFAULT value
or NULL. <productname>Postgres</productname> will reject the new or NULL. <productname>PostgreSQL</productname> will reject the new
column if a NULL is inserted into a column declared NOT NULL. column if a NULL is inserted into a column declared NOT NULL.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/ipcclean.sgml,v 1.5 2001/09/04 00:22:34 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/ipcclean.sgml,v 1.6 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-IPCCLEAN"> <refentry id="APP-IPCCLEAN">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/listen.sgml,v 1.10 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/listen.sgml,v 1.11 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-LISTEN"> <refentry id="SQL-LISTEN">
...@@ -93,7 +93,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER"> ...@@ -93,7 +93,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER">
<para> <para>
<command>LISTEN</command> registers the current <command>LISTEN</command> registers the current
<productname>Postgres</productname> backend as a <productname>PostgreSQL</productname> backend as a
listener on the notify condition listener on the notify condition
<replaceable class="PARAMETER">name</replaceable>. <replaceable class="PARAMETER">name</replaceable>.
</para> </para>
...@@ -116,7 +116,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER"> ...@@ -116,7 +116,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER">
<para> <para>
The method a frontend application must use to detect notify events depends on The method a frontend application must use to detect notify events depends on
which <productname>Postgres</productname> application programming interface it which <productname>PostgreSQL</productname> application programming interface it
uses. With the basic libpq library, the application issues uses. With the basic libpq library, the application issues
<command>LISTEN</command> as an ordinary SQL command, and then must <command>LISTEN</command> as an ordinary SQL command, and then must
periodically call the routine <function>PQnotifies</function> to find out periodically call the routine <function>PQnotifies</function> to find out
...@@ -152,7 +152,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER"> ...@@ -152,7 +152,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER">
</para> </para>
<para> <para>
In some previous releases of In some previous releases of
<productname>Postgres</productname>, <productname>PostgreSQL</productname>,
<replaceable class="PARAMETER">name</replaceable> <replaceable class="PARAMETER">name</replaceable>
had to be enclosed in double-quotes when it did not correspond to any existing had to be enclosed in double-quotes when it did not correspond to any existing
table name, even if syntactically valid as a name. That is no longer required. table name, even if syntactically valid as a name. That is no longer required.
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.28 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.29 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-LOCK"> <refentry id="SQL-LOCK">
...@@ -257,7 +257,7 @@ ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist. ...@@ -257,7 +257,7 @@ ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist.
<para> <para>
<command>LOCK TABLE</command> controls concurrent access to a table <command>LOCK TABLE</command> controls concurrent access to a table
for the duration of a transaction. for the duration of a transaction.
<productname>Postgres</productname> always uses the least restrictive <productname>PostgreSQL</productname> always uses the least restrictive
lock mode whenever possible. <command>LOCK TABLE</command> lock mode whenever possible. <command>LOCK TABLE</command>
provides for cases when you might need more restrictive locking. provides for cases when you might need more restrictive locking.
</para> </para>
...@@ -379,7 +379,7 @@ ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist. ...@@ -379,7 +379,7 @@ ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist.
<note> <note>
<para> <para>
<productname>Postgres</productname> does detect deadlocks and will <productname>PostgreSQL</productname> does detect deadlocks and will
rollback at least one waiting transaction to resolve the deadlock. rollback at least one waiting transaction to resolve the deadlock.
</para> </para>
</note> </note>
...@@ -399,13 +399,13 @@ ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist. ...@@ -399,13 +399,13 @@ ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist.
</title> </title>
<para> <para>
<command>LOCK</command> is a <productname>Postgres</productname> <command>LOCK</command> is a <productname>PostgreSQL</productname>
language extension. language extension.
</para> </para>
<para> <para>
Except for ACCESS SHARE, ACCESS EXCLUSIVE, and SHARE UPDATE EXCLUSIVE lock Except for ACCESS SHARE, ACCESS EXCLUSIVE, and SHARE UPDATE EXCLUSIVE lock
modes, the <productname>Postgres</productname> lock modes and the modes, the <productname>PostgreSQL</productname> lock modes and the
<command>LOCK TABLE</command> syntax are compatible with those <command>LOCK TABLE</command> syntax are compatible with those
present in <productname>Oracle</productname>. present in <productname>Oracle</productname>.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/move.sgml,v 1.11 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/move.sgml,v 1.12 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-MOVE"> <refentry id="SQL-MOVE">
...@@ -57,7 +57,7 @@ MOVE [ <replaceable class="PARAMETER">direction</replaceable> ] [ <replaceable c ...@@ -57,7 +57,7 @@ MOVE [ <replaceable class="PARAMETER">direction</replaceable> ] [ <replaceable c
</title> </title>
<para> <para>
<command>MOVE</command> is a <productname>Postgres</productname> <command>MOVE</command> is a <productname>PostgreSQL</productname>
language extension. language extension.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.15 2001/09/13 15:55:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.16 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-NOTIFY"> <refentry id="SQL-NOTIFY">
...@@ -112,7 +112,7 @@ NOTIFY ...@@ -112,7 +112,7 @@ NOTIFY
<para> <para>
<command>NOTIFY</command> provides a simple form of signal or <command>NOTIFY</command> provides a simple form of signal or
IPC (interprocess communication) mechanism for a collection of processes IPC (interprocess communication) mechanism for a collection of processes
accessing the same <productname>Postgres</productname> database. accessing the same <productname>PostgreSQL</productname> database.
Higher-level mechanisms can be built by using tables in the database to Higher-level mechanisms can be built by using tables in the database to
pass additional data (beyond a mere condition name) from notifier to pass additional data (beyond a mere condition name) from notifier to
listener(s). listener(s).
...@@ -158,13 +158,13 @@ NOTIFY ...@@ -158,13 +158,13 @@ NOTIFY
notify event, just like all the other listening frontends. Depending on the notify event, just like all the other listening frontends. Depending on the
application logic, this could result in useless work---for example, application logic, this could result in useless work---for example,
re-reading a database table to find the same updates that that frontend just re-reading a database table to find the same updates that that frontend just
wrote out. In <productname>Postgres</productname> 6.4 and later, it is wrote out. In <productname>PostgreSQL</productname> 6.4 and later, it is
possible to avoid such extra work by noticing whether the notifying backend possible to avoid such extra work by noticing whether the notifying backend
process's PID (supplied in the notify event message) is the same as one's own process's PID (supplied in the notify event message) is the same as one's own
backend's PID (available from libpq). When they are the same, the notify backend's PID (available from libpq). When they are the same, the notify
event is one's own work bouncing back, and can be ignored. (Despite what was event is one's own work bouncing back, and can be ignored. (Despite what was
said in the preceding paragraph, this is a safe technique. said in the preceding paragraph, this is a safe technique.
<productname>Postgres</productname> keeps self-notifies separate from notifies <productname>PostgreSQL</productname> keeps self-notifies separate from notifies
arriving from other backends, so you cannot miss an outside notify by ignoring arriving from other backends, so you cannot miss an outside notify by ignoring
your own notifies.) your own notifies.)
</para> </para>
...@@ -186,13 +186,13 @@ NOTIFY ...@@ -186,13 +186,13 @@ NOTIFY
</para> </para>
<para> <para>
In some previous releases of In some previous releases of
<productname>Postgres</productname>, <productname>PostgreSQL</productname>,
<replaceable class="PARAMETER">name</replaceable> <replaceable class="PARAMETER">name</replaceable>
had to be enclosed in double-quotes when it did not correspond to any existing had to be enclosed in double-quotes when it did not correspond to any existing
table name, even if syntactically valid as a name. That is no longer required. table name, even if syntactically valid as a name. That is no longer required.
</para> </para>
<para> <para>
In <productname>Postgres</productname> releases prior to 6.4, the backend In <productname>PostgreSQL</productname> releases prior to 6.4, the backend
PID delivered in a notify message was always the PID of the frontend's own PID delivered in a notify message was always the PID of the frontend's own
backend. So it was not possible to distinguish one's own notifies from other backend. So it was not possible to distinguish one's own notifies from other
clients' notifies in those earlier releases. clients' notifies in those earlier releases.
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.11 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.12 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="app-pg-ctl"> <refentry id="app-pg-ctl">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.40 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.41 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-PGDUMP"> <refentry id="APP-PGDUMP">
...@@ -670,9 +670,9 @@ connectDBStart() -- connect() failed: No such file or directory ...@@ -670,9 +670,9 @@ connectDBStart() -- connect() failed: No such file or directory
<para> <para>
The <command>pg_dump</command> utility first appeared in The <command>pg_dump</command> utility first appeared in
<application>Postgres95 release 0.02</application>. The <application>Postgres95</application> release <literal>0.02</literal>. The
non-plain-text output formats were introduced in non-plain-text output formats were introduced in
<application>PostgreSQL 7.1</application>. <application>PostgreSQL</application> release <literal>7.1</literal>.
</para> </para>
</refsect1> </refsect1>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.26 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.27 2001/12/08 03:24:37 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-PG-DUMPALL"> <refentry id="APP-PG-DUMPALL">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_passwd.sgml,v 1.9 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_passwd.sgml,v 1.10 2001/12/08 03:24:38 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-PG-PASSWD"> <refentry id="APP-PG-PASSWD">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.12 2000/12/25 23:15:26 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.13 2001/12/08 03:24:38 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-PG-UPGRADE"> <refentry id="APP-PG-UPGRADE">
...@@ -39,13 +39,13 @@ pg_upgrade [ -f <replaceable class="parameter">filename</replaceable> ] <replace ...@@ -39,13 +39,13 @@ pg_upgrade [ -f <replaceable class="parameter">filename</replaceable> ] <replace
<para> <para>
<application>pg_upgrade</application> <application>pg_upgrade</application>
is a utility for upgrading from a previous is a utility for upgrading from a previous
Postgres release without reloading all the data. <productname>PostgreSQL</productname> release without reloading all the data.
Not all <productname>Postgres</productname> release transitions can be Not all <productname>PostgreSQL</productname> release transitions can be
handled this way. Check the release notes for details on your installation. handled this way. Check the release notes for details on your installation.
</para> </para>
<procedure> <procedure>
<title>Upgrading <productname>Postgres</productname> with pg_upgrade</title> <title>Upgrading <productname>PostgreSQL</productname> with pg_upgrade</title>
<step performance="required"> <step performance="required">
<para> <para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgaccess-ref.sgml,v 1.12 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgaccess-ref.sgml,v 1.13 2001/12/08 03:24:38 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-PGACCESS"> <refentry id="APP-PGACCESS">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtclsh.sgml,v 1.3 2001/03/06 17:43:56 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtclsh.sgml,v 1.4 2001/12/08 03:24:38 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-PGTCLSH"> <refentry id="APP-PGTCLSH">
...@@ -38,7 +38,7 @@ Postgres documentation ...@@ -38,7 +38,7 @@ Postgres documentation
<para> <para>
<command>pgtclsh</command> is a <application>Tcl</application> <command>pgtclsh</command> is a <application>Tcl</application>
shell interface extended with shell interface extended with
<productname>Postgres</productname> database access functions. <productname>PostgreSQL</productname> database access functions.
(Essentially, it is <command>tclsh</command> with (Essentially, it is <command>tclsh</command> with
<filename>libpgtcl</filename> loaded.) Like with the regular <filename>libpgtcl</filename> loaded.) Like with the regular
<application>Tcl</application> shell, the first command line <application>Tcl</application> shell, the first command line
...@@ -50,7 +50,7 @@ Postgres documentation ...@@ -50,7 +50,7 @@ Postgres documentation
<para> <para>
A <application>Tcl</application> shell with A <application>Tcl</application> shell with
<application>Tk</application> and <application>Tk</application> and
<productname>Postgres</productname> functions is available as <xref <productname>PostgreSQL</productname> functions is available as <xref
linkend="app-pgtksh">. linkend="app-pgtksh">.
</para> </para>
</refsect1> </refsect1>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtksh.sgml,v 1.3 2001/03/06 17:43:56 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtksh.sgml,v 1.4 2001/12/08 03:24:38 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-PGTKSH"> <refentry id="APP-PGTKSH">
...@@ -37,7 +37,7 @@ Postgres documentation ...@@ -37,7 +37,7 @@ Postgres documentation
<para> <para>
<command>pgtksh</command> is a <application>Tcl/Tk</application> <command>pgtksh</command> is a <application>Tcl/Tk</application>
shell interface extended with <productname>Postgres</productname> shell interface extended with <productname>PostgreSQL</productname>
database access functions. (Essentially, it is database access functions. (Essentially, it is
<command>wish</command> with <filename>libpgtcl</filename> loaded.) <command>wish</command> with <filename>libpgtcl</filename> loaded.)
Like with <command>wish</command>, the regular Like with <command>wish</command>, the regular
...@@ -50,7 +50,7 @@ Postgres documentation ...@@ -50,7 +50,7 @@ Postgres documentation
<para> <para>
A plain <application>Tcl</application> shell with A plain <application>Tcl</application> shell with
<productname>Postgres</productname> functions is available as <xref <productname>PostgreSQL</productname> functions is available as <xref
linkend="app-pgtclsh">. linkend="app-pgtclsh">.
</para> </para>
</refsect1> </refsect1>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.22 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.23 2001/12/08 03:24:38 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-POSTGRES"> <refentry id="APP-POSTGRES">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.25 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.26 2001/12/08 03:24:38 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="app-postmaster"> <refentry id="app-postmaster">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.60 2001/09/13 15:55:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.61 2001/12/08 03:24:38 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-PSQL"> <refentry id="APP-PSQL">
...@@ -37,8 +37,8 @@ Postgres documentation ...@@ -37,8 +37,8 @@ Postgres documentation
<para> <para>
<application>psql</application> is a terminal-based front-end to <application>psql</application> is a terminal-based front-end to
<productname>Postgres</productname>. It enables you to type in queries <productname>PostgreSQL</productname>. It enables you to type in queries
interactively, issue them to <productname>Postgres</productname>, and see interactively, issue them to <productname>PostgreSQL</productname>, and see
the query results. Alternatively, input can be from a file. the query results. Alternatively, input can be from a file.
In addition, it provides a number of meta-commands and In addition, it provides a number of meta-commands and
various shell-like features to facilitate writing scripts and automating a wide various shell-like features to facilitate writing scripts and automating a wide
...@@ -64,7 +64,7 @@ Postgres documentation ...@@ -64,7 +64,7 @@ Postgres documentation
<title>Connecting To A Database</title> <title>Connecting To A Database</title>
<para> <para>
<application>psql</application> is a regular <productname>Postgres</productname> <application>psql</application> is a regular <productname>PostgreSQL</productname>
client application. In order to connect to a database you need to know the client application. In order to connect to a database you need to know the
name of your target database, the hostname and port number of the server name of your target database, the hostname and port number of the server
and what user name you want to connect as. <application>psql</application> can be and what user name you want to connect as. <application>psql</application> can be
...@@ -334,7 +334,7 @@ testdb=> ...@@ -334,7 +334,7 @@ testdb=>
<term><literal>\copyright</literal></term> <term><literal>\copyright</literal></term>
<listitem> <listitem>
<para> <para>
Shows the copyright and distribution terms of <application>Postgres</application>. Shows the copyright and distribution terms of <application>PostgreSQL</application>.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -406,7 +406,7 @@ testdb=> ...@@ -406,7 +406,7 @@ testdb=>
<note> <note>
<para> <para>
<productname>Postgres</productname> stores the object descriptions in the <productname>PostgreSQL</productname> stores the object descriptions in the
pg_description system table. pg_description system table.
</para> </para>
</note> </note>
...@@ -662,7 +662,7 @@ pipe (<literal>|</literal>). See also <command>\pset</command> for a generic way ...@@ -662,7 +662,7 @@ pipe (<literal>|</literal>). See also <command>\pset</command> for a generic way
<para> <para>
List all the databases in the server as well as their owners. Append a List all the databases in the server as well as their owners. Append a
<quote>+</quote> to the command name to see any descriptions <quote>+</quote> to the command name to see any descriptions
for the databases as well. If your <productname>Postgres</productname> for the databases as well. If your <productname>PostgreSQL</productname>
installation was installation was
compiled with multibyte encoding support, the encoding scheme of each compiled with multibyte encoding support, the encoding scheme of each
database is shown as well. database is shown as well.
...@@ -702,7 +702,7 @@ pipe (<literal>|</literal>). See also <command>\pset</command> for a generic way ...@@ -702,7 +702,7 @@ pipe (<literal>|</literal>). See also <command>\pset</command> for a generic way
<listitem> <listitem>
<para> <para>
Stores the file into a <productname>Postgres</productname> <quote>large object</quote>. Stores the file into a <productname>PostgreSQL</productname> <quote>large object</quote>.
Optionally, it associates the given comment with the object. Example: Optionally, it associates the given comment with the object. Example:
<programlisting> <programlisting>
foo=> <userinput>\lo_import '/home/peter/pictures/photo.xcf' 'a picture of me'</userinput> foo=> <userinput>\lo_import '/home/peter/pictures/photo.xcf' 'a picture of me'</userinput>
...@@ -734,7 +734,7 @@ lo_import 152801 ...@@ -734,7 +734,7 @@ lo_import 152801
<term><literal>\lo_list</literal></term> <term><literal>\lo_list</literal></term>
<listitem> <listitem>
<para> <para>
Shows a list of all <productname>Postgres</productname> <quote>large Shows a list of all <productname>PostgreSQL</productname> <quote>large
objects</quote> currently stored in the database, along with any objects</quote> currently stored in the database, along with any
comments provided for them. comments provided for them.
</para> </para>
...@@ -1718,7 +1718,7 @@ bar ...@@ -1718,7 +1718,7 @@ bar
<listitem> <listitem>
<para> <para>
When this variable is set and a backslash command queries the database, the query When this variable is set and a backslash command queries the database, the query
is first shown. This way you can study the <productname>Postgres</productname> is first shown. This way you can study the <productname>PostgreSQL</productname>
internals and provide similar functionality in your own programs. If you set the internals and provide similar functionality in your own programs. If you set the
variable to the value <quote>noexec</quote>, the queries are just shown but are variable to the value <quote>noexec</quote>, the queries are just shown but are
not actually sent to the backend and executed. not actually sent to the backend and executed.
...@@ -1814,7 +1814,7 @@ bar ...@@ -1814,7 +1814,7 @@ bar
<term><envar>LO_TRANSACTION</envar></term> <term><envar>LO_TRANSACTION</envar></term>
<listitem> <listitem>
<para> <para>
If you use the <productname>Postgres</productname> large object If you use the <productname>PostgreSQL</productname> large object
interface to specially store data that does not fit into one tuple, interface to specially store data that does not fit into one tuple,
all the operations must be contained in a transaction block. (See the all the operations must be contained in a transaction block. (See the
documentation of the large object interface for more information.) Since documentation of the large object interface for more information.) Since
...@@ -1983,7 +1983,7 @@ testdb=> <userinput>\set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\' ...@@ -1983,7 +1983,7 @@ testdb=> <userinput>\set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\'
case you can escape a colon with a backslash to protect it from interpretation. case you can escape a colon with a backslash to protect it from interpretation.
(The colon syntax for variables is standard <acronym>SQL</acronym> for embedded (The colon syntax for variables is standard <acronym>SQL</acronym> for embedded
query languages, such as <application>ecpg</application>. The colon syntax for query languages, such as <application>ecpg</application>. The colon syntax for
array slices and type casts are <productname>Postgres</productname> extensions, array slices and type casts are <productname>PostgreSQL</productname> extensions,
hence the conflict.) hence the conflict.)
</para> </para>
...@@ -2168,7 +2168,7 @@ $endif ...@@ -2168,7 +2168,7 @@ $endif
<para> <para>
If you have the readline library installed but <application>psql</application> If you have the readline library installed but <application>psql</application>
does not seem to use it, you must make sure that <productname>Postgres</productname>'s does not seem to use it, you must make sure that <productname>PostgreSQL</productname>'s
top-level <filename>configure</filename> script finds it. <filename>configure</filename> top-level <filename>configure</filename> script finds it. <filename>configure</filename>
needs to find both the library <filename>libreadline.a</filename> needs to find both the library <filename>libreadline.a</filename>
(or a shared library equivalent) (or a shared library equivalent)
...@@ -2202,7 +2202,7 @@ $ ./configure --with-includes=/opt/gnu/include --with-libs=/opt/gnu/lib ... ...@@ -2202,7 +2202,7 @@ $ ./configure --with-includes=/opt/gnu/include --with-libs=/opt/gnu/lib ...
<para> <para>
This section only shows a few examples specific to <application>psql</application>. This section only shows a few examples specific to <application>psql</application>.
If you want to learn <acronym>SQL</acronym> or get familiar with If you want to learn <acronym>SQL</acronym> or get familiar with
<productname>Postgres</productname>, you might wish to read the Tutorial that <productname>PostgreSQL</productname>, you might wish to read the Tutorial that
is included in the distribution. is included in the distribution.
</para> </para>
</note> </note>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.7 2001/11/25 01:11:36 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.8 2001/12/08 03:24:38 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-REINDEX"> <refentry id="SQL-REINDEX">
...@@ -147,7 +147,8 @@ REINDEX ...@@ -147,7 +147,8 @@ REINDEX
(Indeed, in this sort of scenario you may find that backends are (Indeed, in this sort of scenario you may find that backends are
crashing immediately at startup, due to reliance on the corrupted crashing immediately at startup, due to reliance on the corrupted
indexes.) To recover safely, the postmaster must be shut down and a indexes.) To recover safely, the postmaster must be shut down and a
stand-alone Postgres backend must be started instead, giving it stand-alone <productname>PostgreSQL</productname> backend must be
started instead, giving it
the command-line options -O and -P (these options allow system table the command-line options -O and -P (these options allow system table
modifications and prevent use of system indexes, respectively). Then modifications and prevent use of system indexes, respectively). Then
issue <command>REINDEX INDEX</>, <command>REINDEX TABLE</>, or issue <command>REINDEX INDEX</>, <command>REINDEX TABLE</>, or
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/reset.sgml,v 1.12 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/reset.sgml,v 1.13 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-RESET"> <refentry id="SQL-RESET">
...@@ -92,7 +92,7 @@ RESET GEQO; ...@@ -92,7 +92,7 @@ RESET GEQO;
<title>Compatibility</title> <title>Compatibility</title>
<para> <para>
<command>RESET</command> is a <productname>Postgres</productname> extension. <command>RESET</command> is a <productname>PostgreSQL</productname> extension.
</para> </para>
</refsect1> </refsect1>
</refentry> </refentry>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/revoke.sgml,v 1.18 2001/11/19 19:03:56 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/revoke.sgml,v 1.19 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-REVOKE"> <refentry id="SQL-REVOKE">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/rollback.sgml,v 1.9 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/rollback.sgml,v 1.10 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-ROLLBACK"> <refentry id="SQL-ROLLBACK">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.50 2001/10/31 04:50:52 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.51 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-SELECT"> <refentry id="SQL-SELECT">
...@@ -365,7 +365,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be: ...@@ -365,7 +365,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
from sub-tables (inheritance children) of the table. from sub-tables (inheritance children) of the table.
<command>ONLY</command> will <command>ONLY</command> will
suppress rows from sub-tables of the table. Before suppress rows from sub-tables of the table. Before
<Productname>Postgres</Productname> 7.1, <Productname>PostgreSQL</Productname> 7.1,
this was the default result, and adding sub-tables was done this was the default result, and adding sub-tables was done
by appending <command>*</command> to the table name. by appending <command>*</command> to the table name.
This old behaviour is available via the command This old behaviour is available via the command
...@@ -776,7 +776,7 @@ SELECT name FROM distributors ORDER BY code; ...@@ -776,7 +776,7 @@ SELECT name FROM distributors ORDER BY code;
</para> </para>
<para> <para>
As of <productname>Postgres</productname> 7.0, the As of <productname>PostgreSQL</productname> 7.0, the
query optimizer takes LIMIT into account when generating a query plan, query optimizer takes LIMIT into account when generating a query plan,
so you are very likely to get different plans (yielding different row so you are very likely to get different plans (yielding different row
orders) depending on what you use for LIMIT and OFFSET. Thus, using orders) depending on what you use for LIMIT and OFFSET. Thus, using
...@@ -942,7 +942,7 @@ SELECT actors.name ...@@ -942,7 +942,7 @@ SELECT actors.name
</title> </title>
<para> <para>
<productname>Postgres</productname> allows one to omit <productname>PostgreSQL</productname> allows one to omit
the <command>FROM</command> clause from a query. This feature the <command>FROM</command> clause from a query. This feature
was retained from the original PostQuel query language. It has was retained from the original PostQuel query language. It has
a straightforward use to compute the results of simple constant a straightforward use to compute the results of simple constant
...@@ -983,7 +983,7 @@ rather than the unconstrained join ...@@ -983,7 +983,7 @@ rather than the unconstrained join
SELECT distributors.* FROM distributors d, distributors distributors; SELECT distributors.* FROM distributors d, distributors distributors;
</programlisting> </programlisting>
that he will actually get. To help detect this sort of mistake, that he will actually get. To help detect this sort of mistake,
<Productname>Postgres</Productname> 7.1 <Productname>PostgreSQL</Productname> 7.1
and later will warn if the implicit-FROM feature is used in a query that also and later will warn if the implicit-FROM feature is used in a query that also
contains an explicit FROM clause. contains an explicit FROM clause.
...@@ -1011,7 +1011,7 @@ contains an explicit FROM clause. ...@@ -1011,7 +1011,7 @@ contains an explicit FROM clause.
In the <acronym>SQL92</acronym> standard, the optional keyword <literal>AS</> In the <acronym>SQL92</acronym> standard, the optional keyword <literal>AS</>
is just noise and can be is just noise and can be
omitted without affecting the meaning. omitted without affecting the meaning.
The <productname>Postgres</productname> parser requires this keyword when The <productname>PostgreSQL</productname> parser requires this keyword when
renaming output columns because the type extensibility features lead to renaming output columns because the type extensibility features lead to
parsing ambiguities parsing ambiguities
in this context. <literal>AS</literal> is optional in FROM items, however.</para> in this context. <literal>AS</literal> is optional in FROM items, however.</para>
...@@ -1025,10 +1025,10 @@ contains an explicit FROM clause. ...@@ -1025,10 +1025,10 @@ contains an explicit FROM clause.
In <acronym>SQL92</acronym>, an ORDER BY clause may only use result In <acronym>SQL92</acronym>, an ORDER BY clause may only use result
column names or numbers, while a GROUP BY clause may only use input column names or numbers, while a GROUP BY clause may only use input
column names. column names.
<productname>Postgres</productname> extends each of these clauses to <productname>PostgreSQL</productname> extends each of these clauses to
allow the other choice as well (but it uses the standard's interpretation allow the other choice as well (but it uses the standard's interpretation
if there is ambiguity). if there is ambiguity).
<productname>Postgres</productname> also allows both clauses to specify <productname>PostgreSQL</productname> also allows both clauses to specify
arbitrary expressions. Note that names appearing in an expression will arbitrary expressions. Note that names appearing in an expression will
always be taken as input-column names, not as result-column names. always be taken as input-column names, not as result-column names.
</para> </para>
...@@ -1052,7 +1052,7 @@ contains an explicit FROM clause. ...@@ -1052,7 +1052,7 @@ contains an explicit FROM clause.
<para> <para>
The CORRESPONDING BY clause is not supported by The CORRESPONDING BY clause is not supported by
<productname>Postgres</productname>. <productname>PostgreSQL</productname>.
</para> </para>
</refsect3> </refsect3>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/select_into.sgml,v 1.14 2001/10/23 16:42:36 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/select_into.sgml,v 1.15 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-SELECTINTO"> <refentry id="SQL-SELECTINTO">
...@@ -148,7 +148,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be: ...@@ -148,7 +148,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
SQL92 uses <command>SELECT ... INTO</command> to represent selecting SQL92 uses <command>SELECT ... INTO</command> to represent selecting
values into scalar variables of a host program, rather than creating values into scalar variables of a host program, rather than creating
a new table. This indeed is the usage found in PL/pgSQL and ecpg. a new table. This indeed is the usage found in PL/pgSQL and ecpg.
The <productname>Postgres</productname> usage of <command>SELECT The <productname>PostgreSQL</productname> usage of <command>SELECT
INTO</command> to represent table creation is historical. It's best INTO</command> to represent table creation is historical. It's best
to use <command>CREATE TABLE AS</command> for this purpose in new code. to use <command>CREATE TABLE AS</command> for this purpose in new code.
(<command>CREATE TABLE AS</command> isn't standard either, but it's (<command>CREATE TABLE AS</command> isn't standard either, but it's
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.53 2001/09/03 12:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.54 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-SET"> <refentry id="SQL-SET">
...@@ -65,7 +65,7 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL ...@@ -65,7 +65,7 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL
<para> <para>
This option is only available if This option is only available if
<productname>Postgres</productname> is build with multibyte <productname>PostgreSQL</productname> is build with multibyte
support. support.
</para> </para>
</listitem> </listitem>
...@@ -106,10 +106,10 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL ...@@ -106,10 +106,10 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term>Postgres</term> <term>PostgreSQL</term>
<listitem> <listitem>
<para> <para>
Use traditional <productname>Postgres</productname> format. Use traditional <productname>PostgreSQL</productname> format.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -127,7 +127,7 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL ...@@ -127,7 +127,7 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL
<para> <para>
The following two options determine both a substyle of the The following two options determine both a substyle of the
<quote>SQL</quote> and <quote>Postgres</quote> output formats <quote>SQL</quote> and <quote>PostgreSQL</quote> output formats
and the preferred interpretation of ambiguous date input. and the preferred interpretation of ambiguous date input.
<variablelist> <variablelist>
...@@ -225,7 +225,7 @@ SELECT setseed(<replaceable>value</replaceable>); ...@@ -225,7 +225,7 @@ SELECT setseed(<replaceable>value</replaceable>);
<para> <para>
This option is only available if This option is only available if
<productname>Postgres</productname> was built with multibyte <productname>PostgreSQL</productname> was built with multibyte
support. support.
</para> </para>
</listitem> </listitem>
...@@ -357,9 +357,10 @@ SELECT setseed(<replaceable>value</replaceable>); ...@@ -357,9 +357,10 @@ SELECT setseed(<replaceable>value</replaceable>);
<refsect1> <refsect1>
<title>Examples</title> <title>Examples</title>
<para> <para>
Set the style of date to traditional Postgres with European conventions: Set the style of date to traditional
<productname>PostgreSQL</productname> with European conventions:
<screen> <screen>
SET DATESTYLE TO Postgres,European; SET DATESTYLE TO PostgreSQL,European;
</screen> </screen>
Set the time zone for Berkeley, California, using double quotes to Set the time zone for Berkeley, California, using double quotes to
...@@ -402,7 +403,7 @@ SELECT CURRENT_TIMESTAMP AS today; ...@@ -402,7 +403,7 @@ SELECT CURRENT_TIMESTAMP AS today;
attempts to mimic <acronym>SQL92</acronym>. However, SQL allows attempts to mimic <acronym>SQL92</acronym>. However, SQL allows
only numeric time zone offsets. All other parameter settings as only numeric time zone offsets. All other parameter settings as
well as the first syntax shown above are a well as the first syntax shown above are a
<productname>Postgres</productname> extension. <productname>PostgreSQL</productname> extension.
</para> </para>
</refsect2> </refsect2>
</refsect1> </refsect1>
......
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_transaction.sgml,v 1.6 2001/10/09 18:46:00 petere Exp $ --> <!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_transaction.sgml,v 1.7 2001/12/08 03:24:39 thomas Exp $ -->
<refentry id="SQL-SET-TRANSACTION"> <refentry id="SQL-SET-TRANSACTION">
<docinfo> <docinfo>
<date>2000-11-24</date> <date>2000-11-24</date>
...@@ -98,8 +98,9 @@ SET default_transaction_isolation = '<replaceable>value</replaceable>' ...@@ -98,8 +98,9 @@ SET default_transaction_isolation = '<replaceable>value</replaceable>'
<para> <para>
SERIALIZABLE is the default level in <acronym>SQL</acronym>. SERIALIZABLE is the default level in <acronym>SQL</acronym>.
Postgres does not provide the isolation levels <option>READ <productname>PostgreSQL</productname> does not provide the
UNCOMMITTED</option> and <option>REPEATABLE READ</option>. Because isolation levels <option>READ UNCOMMITTED</option>
and <option>REPEATABLE READ</option>. Because
of multi-version concurrency control, the serializable level is not of multi-version concurrency control, the serializable level is not
truly serializable. See the <citetitle>User's Guide</citetitle> for truly serializable. See the <citetitle>User's Guide</citetitle> for
details. details.
...@@ -109,7 +110,8 @@ SET default_transaction_isolation = '<replaceable>value</replaceable>' ...@@ -109,7 +110,8 @@ SET default_transaction_isolation = '<replaceable>value</replaceable>'
In <acronym>SQL</acronym> there are two other transaction In <acronym>SQL</acronym> there are two other transaction
characteristics that can be set with these commands: whether the characteristics that can be set with these commands: whether the
transaction is read-only and the size of the diagnostics area. transaction is read-only and the size of the diagnostics area.
Neither of these concepts are supported in Postgres. Neither of these concepts are supported in
<productname>PostgreSQL</productname>.
</para> </para>
</refsect2> </refsect2>
</refsect1> </refsect1>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/show.sgml,v 1.14 2001/09/14 08:47:00 ishii Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/show.sgml,v 1.15 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-SHOW"> <refentry id="SQL-SHOW">
...@@ -120,7 +120,7 @@ NOTICE: geqo is on ...@@ -120,7 +120,7 @@ NOTICE: geqo is on
<para> <para>
The <command>SHOW</command> command is a The <command>SHOW</command> command is a
<productname>Postgres</productname> extension. <productname>PostgreSQL</productname> extension.
</para> </para>
</refsect1> </refsect1>
</refentry> </refentry>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.4 2001/11/18 21:14:20 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.5 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-TRUNCATE"> <refentry id="SQL-TRUNCATE">
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.16 2001/09/13 15:55:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.17 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-UNLISTEN"> <refentry id="SQL-UNLISTEN">
...@@ -93,7 +93,7 @@ UNLISTEN { <replaceable class="PARAMETER">notifyname</replaceable> | * } ...@@ -93,7 +93,7 @@ UNLISTEN { <replaceable class="PARAMETER">notifyname</replaceable> | * }
<command>UNLISTEN</command> <command>UNLISTEN</command>
is used to remove an existing <command>NOTIFY</command> registration. is used to remove an existing <command>NOTIFY</command> registration.
UNLISTEN cancels any existing registration of the current UNLISTEN cancels any existing registration of the current
<productname>Postgres</productname> session as a listener on the notify <productname>PostgreSQL</productname> session as a listener on the notify
condition <replaceable class="PARAMETER">notifyname</replaceable>. condition <replaceable class="PARAMETER">notifyname</replaceable>.
The special condition wildcard <literal>*</literal> cancels all listener registrations The special condition wildcard <literal>*</literal> cancels all listener registrations
for the current session. for the current session.
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.17 2001/09/13 15:55:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.18 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-UPDATE"> <refentry id="SQL-UPDATE">
...@@ -64,7 +64,7 @@ UPDATE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> SET <replacea ...@@ -64,7 +64,7 @@ UPDATE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> SET <replacea
<term><replaceable class="PARAMETER">fromlist</replaceable></term> <term><replaceable class="PARAMETER">fromlist</replaceable></term>
<listitem> <listitem>
<para> <para>
A <productname>Postgres</productname> A <productname>PostgreSQL</productname>
non-standard extension to allow columns non-standard extension to allow columns
from other tables to appear in the WHERE condition. from other tables to appear in the WHERE condition.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.21 2001/11/18 22:17:30 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.22 2001/12/08 03:24:39 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="SQL-VACUUM"> <refentry id="SQL-VACUUM">
...@@ -163,7 +163,7 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28; ...@@ -163,7 +163,7 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
</title> </title>
<para> <para>
<command>VACUUM</command> reclaims storage occupied by deleted tuples. <command>VACUUM</command> reclaims storage occupied by deleted tuples.
In normal <productname>Postgres</productname> operation, tuples that In normal <productname>PostgreSQL</productname> operation, tuples that
are DELETEd or obsoleted by UPDATE are not physically removed from are DELETEd or obsoleted by UPDATE are not physically removed from
their table; they remain present until a <command>VACUUM</command> is their table; they remain present until a <command>VACUUM</command> is
done. Therefore it's necessary to do <command>VACUUM</command> done. Therefore it's necessary to do <command>VACUUM</command>
...@@ -226,7 +226,7 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28; ...@@ -226,7 +226,7 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
ANALYZE</command> command for the affected table. This will update the ANALYZE</command> command for the affected table. This will update the
system catalogs with system catalogs with
the results of all recent changes, and allow the the results of all recent changes, and allow the
<productname>Postgres</productname> query optimizer to make better <productname>PostgreSQL</productname> query optimizer to make better
choices in planning user queries. choices in planning user queries.
</para> </para>
......
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.19 2001/11/28 20:49:10 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.20 2001/12/08 03:24:40 thomas Exp $
Postgres documentation PostgreSQL documentation
--> -->
<refentry id="APP-VACUUMDB"> <refentry id="APP-VACUUMDB">
......
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