diff options
| author | Thomas G. Lockhart | 2001-12-08 03:24:40 +0000 |
|---|---|---|
| committer | Thomas G. Lockhart | 2001-12-08 03:24:40 +0000 |
| commit | 03a321d2143cd1168d10960cada9d688c5140520 (patch) | |
| tree | d3f74d5cb79cb163ccef02e64f0d1e30f5c28221 | |
| parent | 68cb184b562b3713ccc3be1cc21fbd3122493b32 (diff) | |
Use PostgreSQL consistantly throughout docs. Before, usage was split evenly
between Postgres and PostgreSQL.
91 files changed, 360 insertions, 340 deletions
diff --git a/doc/src/sgml/ref/abort.sgml b/doc/src/sgml/ref/abort.sgml index 49cd37d277..1172653942 100644 --- a/doc/src/sgml/ref/abort.sgml +++ b/doc/src/sgml/ref/abort.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/abort.sgml,v 1.8 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/abort.sgml,v 1.9 2001/12/08 03:24:33 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-ABORT"> @@ -129,7 +129,7 @@ ABORT WORK; SQL92 </title> <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> equivalent command. </para> diff --git a/doc/src/sgml/ref/allfiles.sgml b/doc/src/sgml/ref/allfiles.sgml index aea2171cdf..b7d3fe2a01 100644 --- a/doc/src/sgml/ref/allfiles.sgml +++ b/doc/src/sgml/ref/allfiles.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/allfiles.sgml,v 1.30 2001/05/08 21:06:42 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/allfiles.sgml,v 1.31 2001/12/08 03:24:33 thomas Exp $ +PostgreSQL documentation Complete list of usable sgml source files in this directory. --> diff --git a/doc/src/sgml/ref/alter_group.sgml b/doc/src/sgml/ref/alter_group.sgml index c2072f8f15..c96a7f79ba 100644 --- a/doc/src/sgml/ref/alter_group.sgml +++ b/doc/src/sgml/ref/alter_group.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_group.sgml,v 1.6 2001/09/12 01:55:25 ishii Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_group.sgml,v 1.7 2001/12/08 03:24:33 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-ALTERGROUP"> diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index 7fabba4fb9..6b1b427fae 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.33 2001/11/22 03:42:32 momjian Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.34 2001/12/08 03:24:33 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-ALTERTABLE"> @@ -313,7 +313,7 @@ ALTER TABLE distributors ADD CONSTRAINT dist_id_zipcode_key UNIQUE (dist_id, zip <para> 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> <varlistentry> @@ -345,7 +345,7 @@ DROP TABLE temp; <para> The clauses to rename tables, columns, indexes, and sequences are - <productname>Postgres</productname> extensions from SQL92. + <productname>PostgreSQL</productname> extensions from SQL92. </para> </refsect2> diff --git a/doc/src/sgml/ref/alter_user.sgml b/doc/src/sgml/ref/alter_user.sgml index e7f650f388..8119057876 100644 --- a/doc/src/sgml/ref/alter_user.sgml +++ b/doc/src/sgml/ref/alter_user.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.17 2001/09/21 20:31:45 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.18 2001/12/08 03:24:33 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-ALTERUSER"> @@ -155,7 +155,7 @@ ERROR: ALTER USER: user "username" does not exist </title> <para> <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. </para> <para> diff --git a/doc/src/sgml/ref/analyze.sgml b/doc/src/sgml/ref/analyze.sgml index dba4c1befa..89628d0b04 100644 --- a/doc/src/sgml/ref/analyze.sgml +++ b/doc/src/sgml/ref/analyze.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.4 2001/11/18 22:17:30 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.5 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-ANALYZE"> @@ -99,7 +99,7 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ (<rep </title> <para> <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 query planner uses the statistics to help determine the most efficient execution plans for queries. diff --git a/doc/src/sgml/ref/begin.sgml b/doc/src/sgml/ref/begin.sgml index b2b9a88d6b..15c1dbdf07 100644 --- a/doc/src/sgml/ref/begin.sgml +++ b/doc/src/sgml/ref/begin.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/begin.sgml,v 1.14 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/begin.sgml,v 1.15 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-BEGIN"> @@ -95,7 +95,7 @@ NOTICE: BEGIN: already a transaction in progress </title> <para> - By default, <productname>Postgres</productname> executes transactions + By default, <productname>PostgreSQL</productname> executes transactions in <firstterm>unchained mode</firstterm> (also known as <quote>autocommit</quote> in other database systems). @@ -116,7 +116,7 @@ NOTICE: BEGIN: already a transaction in progress <para> The default transaction isolation level in - <productname>Postgres</productname> + <productname>PostgreSQL</productname> is READ COMMITTED, where queries inside the transaction see only changes committed before query execution. So, you have to use <command>SET TRANSACTION ISOLATION LEVEL SERIALIZABLE</command> @@ -128,7 +128,7 @@ NOTICE: BEGIN: already a transaction in progress </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 them are done. Transactions have the standard <acronym>ACID</acronym> (atomic, consistent, isolatable, and durable) property. @@ -185,7 +185,7 @@ BEGIN WORK; <para> <command>BEGIN</command> - is a <productname>Postgres</productname> language extension. + is a <productname>PostgreSQL</productname> language extension. There is no explicit <command>BEGIN</command> command in <acronym>SQL92</acronym>; transaction initiation is always implicit and it terminates either diff --git a/doc/src/sgml/ref/close.sgml b/doc/src/sgml/ref/close.sgml index e56e803130..718209ff3f 100644 --- a/doc/src/sgml/ref/close.sgml +++ b/doc/src/sgml/ref/close.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/close.sgml,v 1.8 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/close.sgml,v 1.9 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CLOSE"> @@ -112,7 +112,7 @@ NOTICE PerformPortalClose: portal "<replaceable class="PARAMETER">cursor</replac Notes </title> <para> - <productname>Postgres</productname> does not have + <productname>PostgreSQL</productname> does not have an explicit <command>OPEN</command> cursor statement; a cursor is considered open when it is declared. Use the <command>DECLARE</command> statement to declare a cursor. diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src/sgml/ref/cluster.sgml index 72dc803367..82c4d3bcf2 100644 --- a/doc/src/sgml/ref/cluster.sgml +++ b/doc/src/sgml/ref/cluster.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.12 2001/10/31 04:49:43 momjian Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.13 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CLUSTER"> @@ -114,7 +114,7 @@ ERROR: Relation <replaceable class="PARAMETER">table</replaceable> does not exis Description </title> <para> - <command>CLUSTER</command> instructs <productname>Postgres</productname> + <command>CLUSTER</command> instructs <productname>PostgreSQL</productname> to cluster the table specified by <replaceable class="parameter">table</replaceable> approximately based on the index specified by @@ -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 in index order, and if the heap table is unordered, the 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. </para> @@ -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> </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 unordered data. You then drop the old table, use <command>ALTER TABLE...RENAME</command> diff --git a/doc/src/sgml/ref/comment.sgml b/doc/src/sgml/ref/comment.sgml index dc913d4906..af4a3f6588 100644 --- a/doc/src/sgml/ref/comment.sgml +++ b/doc/src/sgml/ref/comment.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/comment.sgml,v 1.10 2001/10/03 20:54:20 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/comment.sgml,v 1.11 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-COMMENT"> diff --git a/doc/src/sgml/ref/commit.sgml b/doc/src/sgml/ref/commit.sgml index 301fcd0101..e8a956f693 100644 --- a/doc/src/sgml/ref/commit.sgml +++ b/doc/src/sgml/ref/commit.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/commit.sgml,v 1.11 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/commit.sgml,v 1.12 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-COMMIT"> diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index df607d500f..7a49f4cd77 100644 --- a/doc/src/sgml/ref/copy.sgml +++ b/doc/src/sgml/ref/copy.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.25 2001/12/04 21:19:57 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.26 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-COPY"> @@ -172,7 +172,7 @@ ERROR: <replaceable>reason</replaceable> </title> <para> <command>COPY</command> moves data between - <productname>Postgres</productname> tables and + <productname>PostgreSQL</productname> tables and standard file-system files. <command>COPY TO</command> copies the entire contents of a table to @@ -182,7 +182,7 @@ ERROR: <replaceable>reason</replaceable> <para> <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. The file must be accessible to the backend and the name must be specified from the viewpoint of the backend. @@ -262,7 +262,8 @@ ERROR: <replaceable>reason</replaceable> directly by the backend, not by the client application. Therefore, they must reside on or be accessible to the database server machine, 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 superusers, since it allows writing on any file that the backend has privileges to write on. @@ -343,7 +344,7 @@ ERROR: <replaceable>reason</replaceable> as the column delimiter, backslash that delimiter character to include it in data.) A literal newline character is 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 characters ("\") to double-backslashes ("\\") to ensure that they are loaded properly. @@ -357,7 +358,8 @@ ERROR: <replaceable>reason</replaceable> <title>Binary Format</title> <para> 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. </para> diff --git a/doc/src/sgml/ref/create_aggregate.sgml b/doc/src/sgml/ref/create_aggregate.sgml index fc8f064f7a..8c5e3f7f48 100644 --- a/doc/src/sgml/ref/create_aggregate.sgml +++ b/doc/src/sgml/ref/create_aggregate.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.15 2001/09/13 15:55:24 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.16 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATEAGGREGATE"> @@ -157,7 +157,7 @@ CREATE </title> <para> <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 for base types such as <function>min(integer)</function> and <function>avg(double precision)</function> are already provided in the base @@ -185,7 +185,7 @@ CREATE </programlisting> </para> <para> - <productname>Postgres</productname> creates a temporary variable + <productname>PostgreSQL</productname> creates a temporary variable of data type <replaceable class="PARAMETER">stype</replaceable> to hold the current internal state of the aggregate. At each input data item, @@ -284,7 +284,7 @@ CREATE </title> <para> <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. </para> </refsect2> diff --git a/doc/src/sgml/ref/create_constraint.sgml b/doc/src/sgml/ref/create_constraint.sgml index 3ffefe4cbd..0a72f1fa44 100644 --- a/doc/src/sgml/ref/create_constraint.sgml +++ b/doc/src/sgml/ref/create_constraint.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v 1.3 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v 1.4 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATECONSTRAINT"> diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml index 77fa3fe1c3..1c20644502 100644 --- a/doc/src/sgml/ref/create_database.sgml +++ b/doc/src/sgml/ref/create_database.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.21 2001/11/18 00:38:00 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.22 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATEDATABASE"> @@ -170,7 +170,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> </title> <para> <command>CREATE DATABASE</command> creates a new - <productname>Postgres</productname> database. + <productname>PostgreSQL</productname> database. The creator becomes the owner of the new database. </para> @@ -201,7 +201,8 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> <replaceable class="parameter">name</replaceable>. In particular, by writing <literal>TEMPLATE = template0</>, you can create a virgin 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 <literal>template1</>. </para> @@ -226,7 +227,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> Notes </title> <para> - <command>CREATE DATABASE</command> is a <productname>Postgres</productname> + <command>CREATE DATABASE</command> is a <productname>PostgreSQL</productname> language extension. </para> <para> @@ -250,7 +251,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> comment from Olly; response from Thomas... <comment> 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? </comment> Hmm. This isn't an issue since the upgrade would do @@ -287,7 +288,14 @@ comment from Olly; response from Thomas... <programlisting> <prompt>$</prompt> <userinput>mkdir 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> <computeroutput> diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml index 5a4c49cb63..df643cd8e8 100644 --- a/doc/src/sgml/ref/create_function.sgml +++ b/doc/src/sgml/ref/create_function.sgml @@ -1,5 +1,5 @@ <!-- -$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"> @@ -200,7 +200,7 @@ CREATE [ OR REPLACE ] FUNCTION <replaceable class="parameter">name</replaceable> Refer to the chapter in the <citetitle>PostgreSQL Programmer's Guide</citetitle> on the topic of extending - <productname>Postgres</productname> via functions + <productname>PostgreSQL</productname> via functions for further information on writing external functions. </para> @@ -215,7 +215,7 @@ CREATE [ OR REPLACE ] FUNCTION <replaceable class="parameter">name</replaceable> </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 so long as they have distinct argument types. This facility must be used with caution for internal and C-language functions, however. diff --git a/doc/src/sgml/ref/create_group.sgml b/doc/src/sgml/ref/create_group.sgml index 6556997022..1a91013353 100644 --- a/doc/src/sgml/ref/create_group.sgml +++ b/doc/src/sgml/ref/create_group.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_group.sgml,v 1.5 2001/09/14 07:59:31 ishii Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_group.sgml,v 1.6 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATEGROUP"> @@ -55,7 +55,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be: <listitem> <para> 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. </para> <para> diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index e76d87de90..58392864cd 100644 --- a/doc/src/sgml/ref/create_index.sgml +++ b/doc/src/sgml/ref/create_index.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.24 2001/09/14 08:05:55 ishii Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.25 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATEINDEX"> @@ -78,7 +78,7 @@ CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable> <para> The name of the access method to be used for 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> <varlistentry> @@ -236,7 +236,7 @@ ERROR: Cannot create index: 'index_name' already exists. </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 Lehman-Yao high-concurrency btrees. The rtree access method implements standard rtrees using Guttman's quadratic split algorithm. @@ -292,7 +292,7 @@ ERROR: Cannot create index: 'index_name' already exists. </title> <para> - The <productname>Postgres</productname> + The <productname>PostgreSQL</productname> query optimizer will consider using a btree index whenever an indexed attribute is involved in a comparison using one of: @@ -306,7 +306,7 @@ ERROR: Cannot create index: 'index_name' already exists. </para> <para> - The <productname>Postgres</productname> + The <productname>PostgreSQL</productname> query optimizer will consider using an rtree index whenever an indexed attribute is involved in a comparison using one of: @@ -322,7 +322,7 @@ ERROR: Cannot create index: 'index_name' already exists. </para> <para> - The <productname>Postgres</productname> + The <productname>PostgreSQL</productname> query optimizer will consider using a hash index whenever an indexed attribute is involved in a comparison using the <literal>=</literal> operator. @@ -331,7 +331,8 @@ ERROR: Cannot create index: 'index_name' already exists. <para> Currently, only the btree and gist access methods support multi-column 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. </para> @@ -428,7 +429,7 @@ SELECT * FROM points SQL92 </title> <para> - CREATE INDEX is a <productname>Postgres</productname> language extension. + CREATE INDEX is a <productname>PostgreSQL</productname> language extension. </para> <para> There is no <command>CREATE INDEX</command> command in SQL92. diff --git a/doc/src/sgml/ref/create_language.sgml b/doc/src/sgml/ref/create_language.sgml index 922e5275ca..3d2b71198f 100644 --- a/doc/src/sgml/ref/create_language.sgml +++ b/doc/src/sgml/ref/create_language.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_language.sgml,v 1.19 2001/11/18 20:35:02 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_language.sgml,v 1.20 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATELANGUAGE"> diff --git a/doc/src/sgml/ref/create_operator.sgml b/doc/src/sgml/ref/create_operator.sgml index 40c9799772..11debc3d3a 100644 --- a/doc/src/sgml/ref/create_operator.sgml +++ b/doc/src/sgml/ref/create_operator.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.21 2001/09/13 15:55:24 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.22 2001/12/08 03:24:34 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATEOPERATOR"> @@ -205,7 +205,7 @@ CREATE </literallayout> For example, <literal>@-</literal> is an allowed operator name, 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. </para> </listitem> @@ -218,7 +218,7 @@ CREATE For example, if you have defined a left-unary operator named <literal>@</literal>, you cannot write <literal>X*@Y</literal>; you must write <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. </para> </note> @@ -242,7 +242,7 @@ CREATE </para> <para> 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. For example, the operator area-less-than, <<<, would probably have a commutator @@ -280,7 +280,7 @@ MYBOXES.description !== box '((0,0), (1,1))' </para> <para> 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 does not yet have a commutator itself, then the commutator's entry is updated to have the newly created operator as its @@ -290,17 +290,18 @@ MYBOXES.description !== box '((0,0), (1,1))' operator should be defined without a commutator or negator (as appropriate). When the second operator is defined, 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.) </para> <para> The HASHES, SORT1, and SORT2 options are present to support the 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 variables separated by an operator that returns a boolean) by iterative substitution [WONG76]. - In addition, <productname>Postgres</productname> + In addition, <productname>PostgreSQL</productname> can use a hash-join algorithm along the lines of [SHAP86]; however, it must know whether this strategy is applicable. The current hash-join algorithm @@ -321,7 +322,7 @@ MYBOXES.description !== box '((0,0), (1,1))' </para> <para> 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 them and will require additional specification when an operator is defined. Fortunately, the research community @@ -336,7 +337,7 @@ MYBOXES.description !== box '((0,0), (1,1))' MYBOXES.description <<< box '((0,0), (1,1))' </programlisting> 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 satisfy the clause. The function <replaceable class="parameter">res_proc</replaceable> @@ -364,7 +365,7 @@ my_procedure_1 (MYBOXES.description, box '((0,0), (1,1))') <programlisting> MYBOXES.description === box '((0,0), (1,1))' </programlisting> - is that <productname>Postgres</productname> + is that <productname>PostgreSQL</productname> attempts to optimize operators and can decide to use an index to restrict the search space when operators are involved. However, there is no attempt to @@ -428,7 +429,7 @@ CREATE OPERATOR === ( <para> <command>CREATE OPERATOR</command> - is a <productname>Postgres</productname> extension. + is a <productname>PostgreSQL</productname> extension. There is no <command>CREATE OPERATOR</command> statement in <acronym>SQL92</acronym>. </para> diff --git a/doc/src/sgml/ref/create_rule.sgml b/doc/src/sgml/ref/create_rule.sgml index ee17fbdded..0890faa9ce 100644 --- a/doc/src/sgml/ref/create_rule.sgml +++ b/doc/src/sgml/ref/create_rule.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_rule.sgml,v 1.29 2001/11/06 23:54:32 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_rule.sgml,v 1.30 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATERULE"> @@ -148,7 +148,7 @@ CREATE </title> <para> - The <productname>Postgres</productname> + The <productname>PostgreSQL</productname> <firstterm>rule system</firstterm> allows one to define an alternate action to be performed on inserts, updates, or deletions from database tables. Rules are used to @@ -255,8 +255,8 @@ CREATE It is very important to take care to avoid circular rules. For example, though each of the following two rule definitions are accepted by - <productname>Postgres</productname>, the - select command will cause <productname>Postgres</productname> to + <productname>PostgreSQL</productname>, the + select command will cause <productname>PostgreSQL</productname> to report an error because the query cycled too many times: <programlisting> @@ -272,7 +272,7 @@ CREATE RULE "_RETtoyemp" AS </programlisting> 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: <programlisting> @@ -310,7 +310,7 @@ UPDATE mytable SET name = 'foo' WHERE id = 42; </title> <para> - <command>CREATE RULE</command> statement is a <productname>Postgres</productname> + <command>CREATE RULE</command> statement is a <productname>PostgreSQL</productname> language extension. There is no <command>CREATE RULE</command> statement in <acronym>SQL92</acronym>. </para> diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml index f2e343660d..e528658d0d 100644 --- a/doc/src/sgml/ref/create_sequence.sgml +++ b/doc/src/sgml/ref/create_sequence.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.22 2001/11/28 15:33:48 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.23 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATESEQUENCE"> @@ -362,7 +362,7 @@ END; </title> <para> - <command>CREATE SEQUENCE</command> is a <productname>Postgres</productname> + <command>CREATE SEQUENCE</command> is a <productname>PostgreSQL</productname> language extension. There is no <command>CREATE SEQUENCE</command> statement in <acronym>SQL92</acronym>. diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index e583c188dd..ec264dbb11 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.49 2001/11/18 20:35:02 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.50 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATETABLE"> @@ -186,7 +186,8 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is: </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 is, if we create table <literal>foo</literal> inheriting from <literal>bar</literal>, then functions that accept the tuple diff --git a/doc/src/sgml/ref/create_table_as.sgml b/doc/src/sgml/ref/create_table_as.sgml index 8ebc19c2a7..b18e9cdccf 100644 --- a/doc/src/sgml/ref/create_table_as.sgml +++ b/doc/src/sgml/ref/create_table_as.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.8 2001/10/22 18:14:47 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.9 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATETABLEAS"> diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml index ff587643a9..846bc5cf87 100644 --- a/doc/src/sgml/ref/create_trigger.sgml +++ b/doc/src/sgml/ref/create_trigger.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.20 2001/11/30 01:22:47 momjian Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.21 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATETRIGGER"> diff --git a/doc/src/sgml/ref/create_type.sgml b/doc/src/sgml/ref/create_type.sgml index 0ae5a560b4..916163c1dd 100644 --- a/doc/src/sgml/ref/create_type.sgml +++ b/doc/src/sgml/ref/create_type.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.24 2001/11/03 21:42:47 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.25 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATETYPE"> diff --git a/doc/src/sgml/ref/create_user.sgml b/doc/src/sgml/ref/create_user.sgml index 34e210c70e..cc23cce03b 100644 --- a/doc/src/sgml/ref/create_user.sgml +++ b/doc/src/sgml/ref/create_user.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_user.sgml,v 1.21 2001/09/21 20:31:45 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_user.sgml,v 1.22 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATEUSER"> @@ -59,7 +59,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be: <listitem> <para> 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 match the <acronym>UNIX</acronym> user ids, but some people choose to keep the numbers the same. @@ -193,7 +193,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be: </title> <para> <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. You must be a database superuser to use this command. </para> @@ -203,7 +203,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be: endterm="SQL-DROPUSER-title"> to remove a user. Use <xref linkend="SQL-ALTERGROUP" endterm="SQL-ALTERGROUP-title"> to add or remove the user from other groups. - <productname>Postgres</productname> + <productname>PostgreSQL</productname> comes with a script <xref linkend="APP-CREATEUSER" endterm="APP-CREATEUSER-title"> which has the same functionality as this command (in fact, it calls this command) diff --git a/doc/src/sgml/ref/create_view.sgml b/doc/src/sgml/ref/create_view.sgml index cc533e1824..c0d60f3e92 100644 --- a/doc/src/sgml/ref/create_view.sgml +++ b/doc/src/sgml/ref/create_view.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_view.sgml,v 1.13 2001/11/06 23:54:32 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_view.sgml,v 1.14 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-CREATEVIEW"> diff --git a/doc/src/sgml/ref/createdb.sgml b/doc/src/sgml/ref/createdb.sgml index 57c244b271..6b14b26837 100644 --- a/doc/src/sgml/ref/createdb.sgml +++ b/doc/src/sgml/ref/createdb.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.22 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.23 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-CREATEDB"> diff --git a/doc/src/sgml/ref/createlang.sgml b/doc/src/sgml/ref/createlang.sgml index 4d267f75d1..3c9f84d183 100644 --- a/doc/src/sgml/ref/createlang.sgml +++ b/doc/src/sgml/ref/createlang.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/createlang.sgml,v 1.20 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/createlang.sgml,v 1.21 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-CREATELANG"> diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/createuser.sgml index 8efa8c3937..9dcb7a1bb9 100644 --- a/doc/src/sgml/ref/createuser.sgml +++ b/doc/src/sgml/ref/createuser.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.21 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.22 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-CREATEUSER"> diff --git a/doc/src/sgml/ref/current_time.sgml b/doc/src/sgml/ref/current_time.sgml index 617b3dba91..773a34f5ce 100644 --- a/doc/src/sgml/ref/current_time.sgml +++ b/doc/src/sgml/ref/current_time.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_time.sgml,v 1.4 1999/07/22 15:09:09 thomas Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_time.sgml,v 1.5 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <REFENTRY ID="SQL-CURRENT-TIME"> diff --git a/doc/src/sgml/ref/current_timestamp.sgml b/doc/src/sgml/ref/current_timestamp.sgml index 2343821802..2be1b05a56 100644 --- a/doc/src/sgml/ref/current_timestamp.sgml +++ b/doc/src/sgml/ref/current_timestamp.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_timestamp.sgml,v 1.4 1999/07/22 15:09:09 thomas Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_timestamp.sgml,v 1.5 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <REFENTRY ID="SQL-CURRENT-TIMESTAMP"> diff --git a/doc/src/sgml/ref/current_user.sgml b/doc/src/sgml/ref/current_user.sgml index 62a44986b3..8fa3ebc48a 100644 --- a/doc/src/sgml/ref/current_user.sgml +++ b/doc/src/sgml/ref/current_user.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_user.sgml,v 1.4 1999/07/22 15:09:09 thomas Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_user.sgml,v 1.5 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <REFENTRY ID="SQL-CURRENT-USER"> diff --git a/doc/src/sgml/ref/declare.sgml b/doc/src/sgml/ref/declare.sgml index e3b7b1d4a3..692656af9c 100644 --- a/doc/src/sgml/ref/declare.sgml +++ b/doc/src/sgml/ref/declare.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.14 2001/09/13 15:55:24 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.15 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DECLARE"> @@ -62,7 +62,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS <acronym>SQL92</acronym> keyword indicating that data retrieved from the cursor should be unaffected by updates from other processes or cursors. 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. </para> </listitem> @@ -74,7 +74,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS <para> <acronym>SQL92</acronym> keyword indicating that data may be retrieved 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> </listitem> </varlistentry> @@ -97,7 +97,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS <para> <acronym>SQL92</acronym> keyword indicating that the cursor will be used 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> </listitem> </varlistentry> @@ -108,7 +108,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS <para> <acronym>SQL92</acronym> keyword indicating that the cursor will be used 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. </para> </listitem> @@ -120,7 +120,7 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS <para> Column(s) to be updated. 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. </para> </listitem> @@ -196,7 +196,7 @@ ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks <para> 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 data is stored natively in binary format, the system must 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 <para> String representation is architecture-neutral whereas binary 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>. Therefore, if your client machine and server machine use different 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 <para> In <acronym>SQL92</acronym> cursors are only available in 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> statement; a cursor is considered to be open when it is declared. 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 involving DECLARE and OPEN statements. </para> @@ -302,12 +302,12 @@ DECLARE liahona CURSOR </title> <para> <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. <acronym>SQL92</acronym> allows embedded or modular cursors to update database information. - All <productname>Postgres</productname> cursors are read only. - The BINARY keyword is a <productname>Postgres</productname> extension. + All <productname>PostgreSQL</productname> cursors are read only. + The BINARY keyword is a <productname>PostgreSQL</productname> extension. </para> </refsect2> </refsect1> diff --git a/doc/src/sgml/ref/delete.sgml b/doc/src/sgml/ref/delete.sgml index 3597db386b..ac5c699cf8 100644 --- a/doc/src/sgml/ref/delete.sgml +++ b/doc/src/sgml/ref/delete.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/delete.sgml,v 1.14 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/delete.sgml,v 1.15 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DELETE"> @@ -110,7 +110,7 @@ DELETE <replaceable class="parameter">count</replaceable> <tip> <para> <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. </para> </tip> @@ -187,7 +187,7 @@ DELETE FROM <replaceable class="parameter">table</replaceable> WHERE where <replaceable class="parameter">cursor</replaceable> identifies an open cursor. - Interactive cursors in <productname>Postgres</productname> are read-only. + Interactive cursors in <productname>PostgreSQL</productname> are read-only. </para> </refsect2> </refsect1> diff --git a/doc/src/sgml/ref/drop_aggregate.sgml b/doc/src/sgml/ref/drop_aggregate.sgml index 937d6ac494..d60c9cb8f4 100644 --- a/doc/src/sgml/ref/drop_aggregate.sgml +++ b/doc/src/sgml/ref/drop_aggregate.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_aggregate.sgml,v 1.13 2001/10/03 20:54:20 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_aggregate.sgml,v 1.14 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPAGGREGATE"> @@ -153,7 +153,7 @@ DROP AGGREGATE myavg(int4); <para> There is no <command>DROP AGGREGATE</command> statement in <acronym>SQL92</acronym>; the statement is a - <productname>Postgres</productname> + <productname>PostgreSQL</productname> language extension. </para> </refsect2> diff --git a/doc/src/sgml/ref/drop_database.sgml b/doc/src/sgml/ref/drop_database.sgml index 07d596c626..f68349a05a 100644 --- a/doc/src/sgml/ref/drop_database.sgml +++ b/doc/src/sgml/ref/drop_database.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_database.sgml,v 1.13 2001/11/18 00:38:00 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_database.sgml,v 1.14 2001/12/08 03:24:35 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPDATABASE"> @@ -148,7 +148,7 @@ DROP DATABASE <replaceable class="PARAMETER">name</replaceable> <para> <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>. </para> </refsect2> diff --git a/doc/src/sgml/ref/drop_function.sgml b/doc/src/sgml/ref/drop_function.sgml index 6e92205eef..34de6e7305 100644 --- a/doc/src/sgml/ref/drop_function.sgml +++ b/doc/src/sgml/ref/drop_function.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_function.sgml,v 1.15 2001/11/19 03:58:25 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_function.sgml,v 1.16 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPFUNCTION"> diff --git a/doc/src/sgml/ref/drop_group.sgml b/doc/src/sgml/ref/drop_group.sgml index e39ff0e187..16f7496bdd 100644 --- a/doc/src/sgml/ref/drop_group.sgml +++ b/doc/src/sgml/ref/drop_group.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_group.sgml,v 1.2 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_group.sgml,v 1.3 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPGROUP"> diff --git a/doc/src/sgml/ref/drop_index.sgml b/doc/src/sgml/ref/drop_index.sgml index 0fdce31e0f..210753b49a 100644 --- a/doc/src/sgml/ref/drop_index.sgml +++ b/doc/src/sgml/ref/drop_index.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_index.sgml,v 1.11 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_index.sgml,v 1.12 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPINDEX"> @@ -103,7 +103,7 @@ ERROR: index "<replaceable class="PARAMETER">index_name</replaceable>" does not Notes </title> <para> - <command>DROP INDEX</command> is a <productname>Postgres</productname> + <command>DROP INDEX</command> is a <productname>PostgreSQL</productname> language extension. </para> <para> diff --git a/doc/src/sgml/ref/drop_language.sgml b/doc/src/sgml/ref/drop_language.sgml index 2f85007af8..26668d5995 100644 --- a/doc/src/sgml/ref/drop_language.sgml +++ b/doc/src/sgml/ref/drop_language.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_language.sgml,v 1.12 2001/10/26 21:17:03 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_language.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPLANGUAGE"> @@ -105,7 +105,7 @@ ERROR: Language "<replaceable class="parameter">name</replaceable>" doesn't exis </title> <para> The <command>DROP PROCEDURAL LANGUAGE</command> statement is - a <productname>Postgres</productname> language extension. + a <productname>PostgreSQL</productname> language extension. </para> <para> Refer to diff --git a/doc/src/sgml/ref/drop_operator.sgml b/doc/src/sgml/ref/drop_operator.sgml index 23e39f434b..715e2e4d81 100644 --- a/doc/src/sgml/ref/drop_operator.sgml +++ b/doc/src/sgml/ref/drop_operator.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_operator.sgml,v 1.11 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_operator.sgml,v 1.12 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPOPERATOR"> @@ -149,7 +149,7 @@ ERROR: RemoveOperator: right unary operator '<replaceable class="PARAMETER">oper </title> <para> The <command>DROP OPERATOR</command> statement is a - <productname>Postgres</productname> + <productname>PostgreSQL</productname> language extension. </para> <para> diff --git a/doc/src/sgml/ref/drop_rule.sgml b/doc/src/sgml/ref/drop_rule.sgml index 6063c114ab..452ff48a18 100644 --- a/doc/src/sgml/ref/drop_rule.sgml +++ b/doc/src/sgml/ref/drop_rule.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_rule.sgml,v 1.10 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_rule.sgml,v 1.11 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPRULE"> @@ -90,8 +90,8 @@ ERROR: Rule or view "<replaceable class="parameter">name</replaceable>" not fou </title> <para> <command>DROP RULE</command> drops a rule from the specified - <productname>Postgres</productname> rule - system. <productname>Postgres</productname> + <productname>PostgreSQL</productname> rule + system. <productname>PostgreSQL</productname> will immediately cease enforcing it and will purge its definition from the system catalogs. </para> @@ -105,7 +105,7 @@ ERROR: Rule or view "<replaceable class="parameter">name</replaceable>" not fou </title> <para> The <command>DROP RULE</command> statement is a - <productname>Postgres</productname> + <productname>PostgreSQL</productname> language extension. </para> diff --git a/doc/src/sgml/ref/drop_sequence.sgml b/doc/src/sgml/ref/drop_sequence.sgml index 5782fdc6a2..70bb2034b8 100644 --- a/doc/src/sgml/ref/drop_sequence.sgml +++ b/doc/src/sgml/ref/drop_sequence.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_sequence.sgml,v 1.10 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_sequence.sgml,v 1.11 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPSEQUENCE"> @@ -105,7 +105,7 @@ ERROR: sequence "<replaceable class="parameter">name</replaceable>" does not exi </title> <para> The <command>DROP SEQUENCE</command> statement is a - <productname>Postgres</productname> + <productname>PostgreSQL</productname> language extension. </para> <para> diff --git a/doc/src/sgml/ref/drop_table.sgml b/doc/src/sgml/ref/drop_table.sgml index 0899c5a7d4..a462fff51a 100644 --- a/doc/src/sgml/ref/drop_table.sgml +++ b/doc/src/sgml/ref/drop_table.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_table.sgml,v 1.11 2001/09/03 12:57:49 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_table.sgml,v 1.12 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPTABLE"> diff --git a/doc/src/sgml/ref/drop_trigger.sgml b/doc/src/sgml/ref/drop_trigger.sgml index f1bfdadf61..3811e2dcc2 100644 --- a/doc/src/sgml/ref/drop_trigger.sgml +++ b/doc/src/sgml/ref/drop_trigger.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_trigger.sgml,v 1.8 2001/09/13 18:17:44 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_trigger.sgml,v 1.9 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPTRIGGER"> diff --git a/doc/src/sgml/ref/drop_type.sgml b/doc/src/sgml/ref/drop_type.sgml index 8bf9a8f382..997607b1ae 100644 --- a/doc/src/sgml/ref/drop_type.sgml +++ b/doc/src/sgml/ref/drop_type.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.12 2001/11/03 21:42:47 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPTYPE"> diff --git a/doc/src/sgml/ref/drop_user.sgml b/doc/src/sgml/ref/drop_user.sgml index 9c7cc4c58c..2a20e55eed 100644 --- a/doc/src/sgml/ref/drop_user.sgml +++ b/doc/src/sgml/ref/drop_user.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_user.sgml,v 1.12 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_user.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPUSER"> @@ -109,7 +109,7 @@ DROP USER: user "<replaceable class="parameter">name</replaceable>" owns databas Use <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title"> to add new users, and <xref linkend="SQL-ALTERUSER" endterm="SQL-ALTERUSER-title"> to change a user's properties. - <productname>Postgres</productname> + <productname>PostgreSQL</productname> comes with a script <xref linkend="APP-DROPUSER" endterm="APP-DROPUSER-title"> which has the same functionality as this command (in fact, it calls this command) diff --git a/doc/src/sgml/ref/drop_view.sgml b/doc/src/sgml/ref/drop_view.sgml index 918da7c5e0..394147e699 100644 --- a/doc/src/sgml/ref/drop_view.sgml +++ b/doc/src/sgml/ref/drop_view.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_view.sgml,v 1.10 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_view.sgml,v 1.11 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-DROPVIEW"> @@ -184,7 +184,7 @@ DROP VIEW <replaceable class="parameter">view</replaceable> { RESTRICT | CASCADE </title> <para> At present, to remove a referenced view from a - <productname>Postgres</productname> database, + <productname>PostgreSQL</productname> database, you must drop it explicitly. </para> </refsect3> diff --git a/doc/src/sgml/ref/dropdb.sgml b/doc/src/sgml/ref/dropdb.sgml index c9df28445b..79750a900b 100644 --- a/doc/src/sgml/ref/dropdb.sgml +++ b/doc/src/sgml/ref/dropdb.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.12 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.13 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-DROPDB"> diff --git a/doc/src/sgml/ref/droplang.sgml b/doc/src/sgml/ref/droplang.sgml index 3fe3dc8ad6..27cea628fe 100644 --- a/doc/src/sgml/ref/droplang.sgml +++ b/doc/src/sgml/ref/droplang.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/droplang.sgml,v 1.14 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/droplang.sgml,v 1.15 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-DROPLANG"> diff --git a/doc/src/sgml/ref/dropuser.sgml b/doc/src/sgml/ref/dropuser.sgml index 217040403d..07d77691ea 100644 --- a/doc/src/sgml/ref/dropuser.sgml +++ b/doc/src/sgml/ref/dropuser.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.14 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.15 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-DROPUSER"> diff --git a/doc/src/sgml/ref/ecpg-ref.sgml b/doc/src/sgml/ref/ecpg-ref.sgml index a9d2706178..71a277d032 100644 --- a/doc/src/sgml/ref/ecpg-ref.sgml +++ b/doc/src/sgml/ref/ecpg-ref.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.13 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.14 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-ECPG"> diff --git a/doc/src/sgml/ref/end.sgml b/doc/src/sgml/ref/end.sgml index 9f3bd5db29..119ce8235f 100644 --- a/doc/src/sgml/ref/end.sgml +++ b/doc/src/sgml/ref/end.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.5 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.6 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-END"> @@ -94,7 +94,7 @@ NOTICE: COMMIT: no transaction in progress </title> <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 <xref linkend="sql-commit" endterm="sql-commit-title">. </para> diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml index b24863529b..5a4e2771ec 100644 --- a/doc/src/sgml/ref/explain.sgml +++ b/doc/src/sgml/ref/explain.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/explain.sgml,v 1.13 2001/09/18 01:59:05 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/explain.sgml,v 1.14 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-EXPLAIN"> @@ -82,7 +82,7 @@ NOTICE: QUERY PLAN: </computeroutput></term> <listitem> <para> - Explicit query plan from the <productname>Postgres</productname> backend. + Explicit query plan from the <productname>PostgreSQL</productname> backend. </para> </listitem> </varlistentry> @@ -110,7 +110,8 @@ EXPLAIN </title> <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 the table(s) referenced by the query will be scanned---by plain sequential scan, index scan, etc.---and if multiple tables are @@ -143,7 +144,8 @@ EXPLAIN <para> 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). - Usually this option is only useful for debugging Postgres. + Usually this option is only useful for debugging + <application>PostgreSQL</application>. </para> <caution> @@ -172,7 +174,7 @@ ROLLBACK; </title> <para> 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 <citetitle>Programmer's Guide</citetitle> for more information. </para> @@ -236,7 +238,8 @@ Aggregate (cost=0.42..0.42 rows=1 width=4) <para> 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> </refsect1> diff --git a/doc/src/sgml/ref/fetch.sgml b/doc/src/sgml/ref/fetch.sgml index e3e5f77b5a..85f8fbb00a 100644 --- a/doc/src/sgml/ref/fetch.sgml +++ b/doc/src/sgml/ref/fetch.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.16 2001/09/13 15:55:24 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.17 2001/12/08 03:24:36 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-FETCH"> @@ -175,7 +175,7 @@ NOTICE: FETCH/ABSOLUTE not supported, using RELATIVE </computeroutput></term> <listitem> <para> - <productname>Postgres</productname> does not support absolute + <productname>PostgreSQL</productname> does not support absolute positioning of cursors. </para> </listitem> @@ -195,10 +195,10 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>. </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 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 and returns this error message. </para> @@ -250,7 +250,7 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>. <para> 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 in the second form of the command. See below for details on compatibility issues. @@ -258,7 +258,7 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>. <para> Updating data in a cursor is not supported by - <productname>Postgres</productname>, + <productname>PostgreSQL</productname>, because mapping cursor updates back to base tables is not generally possible, as is also the case with VIEW updates. Consequently, @@ -346,7 +346,7 @@ COMMIT WORK; <para> <note> <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 against the embedded form of cursors defined in <acronym>SQL92</acronym>. </para> @@ -369,7 +369,7 @@ FETCH ABSOLUTE <replaceable class="PARAMETER">#</replaceable> <listitem> <para> 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. </para> </listitem> diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml index a4ff54b579..98072ee8e0 100644 --- a/doc/src/sgml/ref/grant.sgml +++ b/doc/src/sgml/ref/grant.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.16 2001/11/19 19:03:56 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.17 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-GRANT"> @@ -155,7 +155,7 @@ GRANT { { SELECT | INSERT | UPDATE | DELETE | RULE | REFERENCES | TRIGGER } [,.. <title>Notes</title> <para> - Currently, to grant privileges in <productname>Postgres</productname> + Currently, to grant privileges in <productname>PostgreSQL</productname> to only a few columns, you must create a view having the desired columns and then grant privileges to that view. diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index a52a63e53b..3bbe44aeee 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/initdb.sgml,v 1.18 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/initdb.sgml,v 1.19 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-INITDB"> diff --git a/doc/src/sgml/ref/initlocation.sgml b/doc/src/sgml/ref/initlocation.sgml index de7e46a635..7ccb76ed19 100644 --- a/doc/src/sgml/ref/initlocation.sgml +++ b/doc/src/sgml/ref/initlocation.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/initlocation.sgml,v 1.13 2001/09/13 15:55:24 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/initlocation.sgml,v 1.14 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-INITLOCATION"> @@ -30,7 +30,7 @@ Postgres documentation <title>Description</title> <para> <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"> 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, diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml index aad43dd010..7788d91cf2 100644 --- a/doc/src/sgml/ref/insert.sgml +++ b/doc/src/sgml/ref/insert.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/insert.sgml,v 1.15 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/insert.sgml,v 1.16 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-INSERT"> @@ -135,7 +135,7 @@ INSERT 0 <replaceable>#</replaceable> <para> Each column not present in the target list will be inserted 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. </para> diff --git a/doc/src/sgml/ref/ipcclean.sgml b/doc/src/sgml/ref/ipcclean.sgml index 7c4fc5647e..17b10b72aa 100644 --- a/doc/src/sgml/ref/ipcclean.sgml +++ b/doc/src/sgml/ref/ipcclean.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/ipcclean.sgml,v 1.5 2001/09/04 00:22:34 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/ipcclean.sgml,v 1.6 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-IPCCLEAN"> diff --git a/doc/src/sgml/ref/listen.sgml b/doc/src/sgml/ref/listen.sgml index 4497f1d67a..dfa6ecbaf9 100644 --- a/doc/src/sgml/ref/listen.sgml +++ b/doc/src/sgml/ref/listen.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/listen.sgml,v 1.10 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/listen.sgml,v 1.11 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-LISTEN"> @@ -93,7 +93,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER"> <para> <command>LISTEN</command> registers the current - <productname>Postgres</productname> backend as a + <productname>PostgreSQL</productname> backend as a listener on the notify condition <replaceable class="PARAMETER">name</replaceable>. </para> @@ -116,7 +116,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER"> <para> 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 <command>LISTEN</command> as an ordinary SQL command, and then must 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"> </para> <para> In some previous releases of - <productname>Postgres</productname>, + <productname>PostgreSQL</productname>, <replaceable class="PARAMETER">name</replaceable> 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. diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index c8afdd2643..055977f745 100644 --- a/doc/src/sgml/ref/lock.sgml +++ b/doc/src/sgml/ref/lock.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.28 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.29 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-LOCK"> @@ -257,7 +257,7 @@ ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist. <para> <command>LOCK TABLE</command> controls concurrent access to a table 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> provides for cases when you might need more restrictive locking. </para> @@ -379,7 +379,7 @@ ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist. <note> <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. </para> </note> @@ -399,13 +399,13 @@ ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist. </title> <para> - <command>LOCK</command> is a <productname>Postgres</productname> + <command>LOCK</command> is a <productname>PostgreSQL</productname> language extension. </para> <para> 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 present in <productname>Oracle</productname>. </para> diff --git a/doc/src/sgml/ref/move.sgml b/doc/src/sgml/ref/move.sgml index 23dec1f677..78dfb0da58 100644 --- a/doc/src/sgml/ref/move.sgml +++ b/doc/src/sgml/ref/move.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/move.sgml,v 1.11 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/move.sgml,v 1.12 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-MOVE"> @@ -57,7 +57,7 @@ MOVE [ <replaceable class="PARAMETER">direction</replaceable> ] [ <replaceable c </title> <para> - <command>MOVE</command> is a <productname>Postgres</productname> + <command>MOVE</command> is a <productname>PostgreSQL</productname> language extension. </para> diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml index 067f3732a5..ee2f2bf9b7 100644 --- a/doc/src/sgml/ref/notify.sgml +++ b/doc/src/sgml/ref/notify.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.15 2001/09/13 15:55:24 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.16 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-NOTIFY"> @@ -112,7 +112,7 @@ NOTIFY <para> <command>NOTIFY</command> provides a simple form of signal or 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 pass additional data (beyond a mere condition name) from notifier to listener(s). @@ -158,13 +158,13 @@ NOTIFY notify event, just like all the other listening frontends. Depending on the application logic, this could result in useless work---for example, 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 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 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. - <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 your own notifies.) </para> @@ -186,13 +186,13 @@ NOTIFY </para> <para> In some previous releases of - <productname>Postgres</productname>, + <productname>PostgreSQL</productname>, <replaceable class="PARAMETER">name</replaceable> 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. </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 backend. So it was not possible to distinguish one's own notifies from other clients' notifies in those earlier releases. diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml index 8bcb64e007..63b57fc11d 100644 --- a/doc/src/sgml/ref/pg_ctl-ref.sgml +++ b/doc/src/sgml/ref/pg_ctl-ref.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.11 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.12 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="app-pg-ctl"> diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index dff18523e0..9aadae36e0 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.40 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.41 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-PGDUMP"> @@ -670,9 +670,9 @@ connectDBStart() -- connect() failed: No such file or directory <para> 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 - <application>PostgreSQL 7.1</application>. + <application>PostgreSQL</application> release <literal>7.1</literal>. </para> </refsect1> diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index 9039b36318..21b6e035f6 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.26 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.27 2001/12/08 03:24:37 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-PG-DUMPALL"> diff --git a/doc/src/sgml/ref/pg_passwd.sgml b/doc/src/sgml/ref/pg_passwd.sgml index 0b7aba901f..13125b08e2 100644 --- a/doc/src/sgml/ref/pg_passwd.sgml +++ b/doc/src/sgml/ref/pg_passwd.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_passwd.sgml,v 1.9 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_passwd.sgml,v 1.10 2001/12/08 03:24:38 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-PG-PASSWD"> diff --git a/doc/src/sgml/ref/pg_upgrade.sgml b/doc/src/sgml/ref/pg_upgrade.sgml index 7128604a9c..2b9406958c 100644 --- a/doc/src/sgml/ref/pg_upgrade.sgml +++ b/doc/src/sgml/ref/pg_upgrade.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.12 2000/12/25 23:15:26 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.13 2001/12/08 03:24:38 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-PG-UPGRADE"> @@ -39,13 +39,13 @@ pg_upgrade [ -f <replaceable class="parameter">filename</replaceable> ] <replace <para> <application>pg_upgrade</application> is a utility for upgrading from a previous - Postgres release without reloading all the data. - Not all <productname>Postgres</productname> release transitions can be + <productname>PostgreSQL</productname> release without reloading all the data. + Not all <productname>PostgreSQL</productname> release transitions can be handled this way. Check the release notes for details on your installation. </para> <procedure> - <title>Upgrading <productname>Postgres</productname> with pg_upgrade</title> + <title>Upgrading <productname>PostgreSQL</productname> with pg_upgrade</title> <step performance="required"> <para> diff --git a/doc/src/sgml/ref/pgaccess-ref.sgml b/doc/src/sgml/ref/pgaccess-ref.sgml index c2f42527c5..29215683fa 100644 --- a/doc/src/sgml/ref/pgaccess-ref.sgml +++ b/doc/src/sgml/ref/pgaccess-ref.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgaccess-ref.sgml,v 1.12 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgaccess-ref.sgml,v 1.13 2001/12/08 03:24:38 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-PGACCESS"> diff --git a/doc/src/sgml/ref/pgtclsh.sgml b/doc/src/sgml/ref/pgtclsh.sgml index 39767128a2..5494dd7783 100644 --- a/doc/src/sgml/ref/pgtclsh.sgml +++ b/doc/src/sgml/ref/pgtclsh.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtclsh.sgml,v 1.3 2001/03/06 17:43:56 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtclsh.sgml,v 1.4 2001/12/08 03:24:38 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-PGTCLSH"> @@ -38,7 +38,7 @@ Postgres documentation <para> <command>pgtclsh</command> is a <application>Tcl</application> shell interface extended with - <productname>Postgres</productname> database access functions. + <productname>PostgreSQL</productname> database access functions. (Essentially, it is <command>tclsh</command> with <filename>libpgtcl</filename> loaded.) Like with the regular <application>Tcl</application> shell, the first command line @@ -50,7 +50,7 @@ Postgres documentation <para> A <application>Tcl</application> shell with <application>Tk</application> and - <productname>Postgres</productname> functions is available as <xref + <productname>PostgreSQL</productname> functions is available as <xref linkend="app-pgtksh">. </para> </refsect1> diff --git a/doc/src/sgml/ref/pgtksh.sgml b/doc/src/sgml/ref/pgtksh.sgml index a985642705..81d1de9291 100644 --- a/doc/src/sgml/ref/pgtksh.sgml +++ b/doc/src/sgml/ref/pgtksh.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtksh.sgml,v 1.3 2001/03/06 17:43:56 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtksh.sgml,v 1.4 2001/12/08 03:24:38 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-PGTKSH"> @@ -37,7 +37,7 @@ Postgres documentation <para> <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 <command>wish</command> with <filename>libpgtcl</filename> loaded.) Like with <command>wish</command>, the regular @@ -50,7 +50,7 @@ Postgres documentation <para> 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">. </para> </refsect1> diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index 48ff1cb007..33e9b46237 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.22 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.23 2001/12/08 03:24:38 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-POSTGRES"> diff --git a/doc/src/sgml/ref/postmaster.sgml b/doc/src/sgml/ref/postmaster.sgml index 6399d3558e..a693164825 100644 --- a/doc/src/sgml/ref/postmaster.sgml +++ b/doc/src/sgml/ref/postmaster.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.25 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.26 2001/12/08 03:24:38 thomas Exp $ +PostgreSQL documentation --> <refentry id="app-postmaster"> diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 55c71a39b1..230e11013b 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.60 2001/09/13 15:55:24 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.61 2001/12/08 03:24:38 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-PSQL"> @@ -37,8 +37,8 @@ Postgres documentation <para> <application>psql</application> is a terminal-based front-end to - <productname>Postgres</productname>. It enables you to type in queries - interactively, issue them to <productname>Postgres</productname>, and see + <productname>PostgreSQL</productname>. It enables you to type in queries + interactively, issue them to <productname>PostgreSQL</productname>, and see the query results. Alternatively, input can be from a file. In addition, it provides a number of meta-commands and various shell-like features to facilitate writing scripts and automating a wide @@ -64,7 +64,7 @@ Postgres documentation <title>Connecting To A Database</title> <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 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 @@ -334,7 +334,7 @@ testdb=> <term><literal>\copyright</literal></term> <listitem> <para> - Shows the copyright and distribution terms of <application>Postgres</application>. + Shows the copyright and distribution terms of <application>PostgreSQL</application>. </para> </listitem> </varlistentry> @@ -406,7 +406,7 @@ testdb=> <note> <para> - <productname>Postgres</productname> stores the object descriptions in the + <productname>PostgreSQL</productname> stores the object descriptions in the pg_description system table. </para> </note> @@ -662,7 +662,7 @@ pipe (<literal>|</literal>). See also <command>\pset</command> for a generic way <para> List all the databases in the server as well as their owners. Append a <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 compiled with multibyte encoding support, the encoding scheme of each database is shown as well. @@ -702,7 +702,7 @@ pipe (<literal>|</literal>). See also <command>\pset</command> for a generic way <listitem> <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: <programlisting> foo=> <userinput>\lo_import '/home/peter/pictures/photo.xcf' 'a picture of me'</userinput> @@ -734,7 +734,7 @@ lo_import 152801 <term><literal>\lo_list</literal></term> <listitem> <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 comments provided for them. </para> @@ -1718,7 +1718,7 @@ bar <listitem> <para> 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 variable to the value <quote>noexec</quote>, the queries are just shown but are not actually sent to the backend and executed. @@ -1814,7 +1814,7 @@ bar <term><envar>LO_TRANSACTION</envar></term> <listitem> <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, all the operations must be contained in a transaction block. (See the 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` '\' 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 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.) </para> @@ -2168,7 +2168,7 @@ $endif <para> 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> needs to find both the library <filename>libreadline.a</filename> (or a shared library equivalent) @@ -2202,7 +2202,7 @@ $ ./configure --with-includes=/opt/gnu/include --with-libs=/opt/gnu/lib ... <para> This section only shows a few examples specific to <application>psql</application>. 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. </para> </note> diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml index 67ba9a6011..bb443f8d46 100644 --- a/doc/src/sgml/ref/reindex.sgml +++ b/doc/src/sgml/ref/reindex.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.7 2001/11/25 01:11:36 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.8 2001/12/08 03:24:38 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-REINDEX"> @@ -147,7 +147,8 @@ REINDEX (Indeed, in this sort of scenario you may find that backends are crashing immediately at startup, due to reliance on the corrupted 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 modifications and prevent use of system indexes, respectively). Then issue <command>REINDEX INDEX</>, <command>REINDEX TABLE</>, or diff --git a/doc/src/sgml/ref/reset.sgml b/doc/src/sgml/ref/reset.sgml index 59228cc819..69c1f861ee 100644 --- a/doc/src/sgml/ref/reset.sgml +++ b/doc/src/sgml/ref/reset.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/reset.sgml,v 1.12 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/reset.sgml,v 1.13 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-RESET"> @@ -92,7 +92,7 @@ RESET GEQO; <title>Compatibility</title> <para> - <command>RESET</command> is a <productname>Postgres</productname> extension. + <command>RESET</command> is a <productname>PostgreSQL</productname> extension. </para> </refsect1> </refentry> diff --git a/doc/src/sgml/ref/revoke.sgml b/doc/src/sgml/ref/revoke.sgml index 7c00c36115..6a858c5b3d 100644 --- a/doc/src/sgml/ref/revoke.sgml +++ b/doc/src/sgml/ref/revoke.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/revoke.sgml,v 1.18 2001/11/19 19:03:56 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/revoke.sgml,v 1.19 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-REVOKE"> diff --git a/doc/src/sgml/ref/rollback.sgml b/doc/src/sgml/ref/rollback.sgml index 527ea84749..2ba6eecc9c 100644 --- a/doc/src/sgml/ref/rollback.sgml +++ b/doc/src/sgml/ref/rollback.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/rollback.sgml,v 1.9 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/rollback.sgml,v 1.10 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-ROLLBACK"> diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml index 3d45eff040..ed080d3534 100644 --- a/doc/src/sgml/ref/select.sgml +++ b/doc/src/sgml/ref/select.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.50 2001/10/31 04:50:52 momjian Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.51 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-SELECT"> @@ -365,7 +365,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be: from sub-tables (inheritance children) of the table. <command>ONLY</command> will 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 by appending <command>*</command> to the table name. This old behaviour is available via the command @@ -776,7 +776,7 @@ SELECT name FROM distributors ORDER BY code; </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, so you are very likely to get different plans (yielding different row orders) depending on what you use for LIMIT and OFFSET. Thus, using @@ -942,7 +942,7 @@ SELECT actors.name </title> <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 was retained from the original PostQuel query language. It has a straightforward use to compute the results of simple constant @@ -983,7 +983,7 @@ rather than the unconstrained join SELECT distributors.* FROM distributors d, distributors distributors; </programlisting> 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 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</> is just noise and can be 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 parsing ambiguities in this context. <literal>AS</literal> is optional in FROM items, however.</para> @@ -1025,10 +1025,10 @@ contains an explicit FROM clause. 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. - <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 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 always be taken as input-column names, not as result-column names. </para> @@ -1052,7 +1052,7 @@ contains an explicit FROM clause. <para> The CORRESPONDING BY clause is not supported by - <productname>Postgres</productname>. + <productname>PostgreSQL</productname>. </para> </refsect3> diff --git a/doc/src/sgml/ref/select_into.sgml b/doc/src/sgml/ref/select_into.sgml index 99c44024c8..8c8b6fc448 100644 --- a/doc/src/sgml/ref/select_into.sgml +++ b/doc/src/sgml/ref/select_into.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/select_into.sgml,v 1.14 2001/10/23 16:42:36 momjian Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/select_into.sgml,v 1.15 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-SELECTINTO"> @@ -148,7 +148,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be: SQL92 uses <command>SELECT ... INTO</command> to represent selecting 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. - 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 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 diff --git a/doc/src/sgml/ref/set.sgml b/doc/src/sgml/ref/set.sgml index 2b3e41a1c9..871a7a403a 100644 --- a/doc/src/sgml/ref/set.sgml +++ b/doc/src/sgml/ref/set.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.53 2001/09/03 12:57:50 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.54 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-SET"> @@ -65,7 +65,7 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL <para> This option is only available if - <productname>Postgres</productname> is build with multibyte + <productname>PostgreSQL</productname> is build with multibyte support. </para> </listitem> @@ -106,10 +106,10 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL </varlistentry> <varlistentry> - <term>Postgres</term> + <term>PostgreSQL</term> <listitem> <para> - Use traditional <productname>Postgres</productname> format. + Use traditional <productname>PostgreSQL</productname> format. </para> </listitem> </varlistentry> @@ -127,7 +127,7 @@ SET TIME ZONE { '<replaceable class="PARAMETER">timezone</replaceable>' | LOCAL <para> 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. <variablelist> @@ -225,7 +225,7 @@ SELECT setseed(<replaceable>value</replaceable>); <para> This option is only available if - <productname>Postgres</productname> was built with multibyte + <productname>PostgreSQL</productname> was built with multibyte support. </para> </listitem> @@ -357,9 +357,10 @@ SELECT setseed(<replaceable>value</replaceable>); <refsect1> <title>Examples</title> <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> -SET DATESTYLE TO Postgres,European; +SET DATESTYLE TO PostgreSQL,European; </screen> Set the time zone for Berkeley, California, using double quotes to @@ -402,7 +403,7 @@ SELECT CURRENT_TIMESTAMP AS today; attempts to mimic <acronym>SQL92</acronym>. However, SQL allows only numeric time zone offsets. All other parameter settings as well as the first syntax shown above are a - <productname>Postgres</productname> extension. + <productname>PostgreSQL</productname> extension. </para> </refsect2> </refsect1> diff --git a/doc/src/sgml/ref/set_transaction.sgml b/doc/src/sgml/ref/set_transaction.sgml index 50af1e9b06..45bed28955 100644 --- a/doc/src/sgml/ref/set_transaction.sgml +++ b/doc/src/sgml/ref/set_transaction.sgml @@ -1,4 +1,4 @@ -<!-- $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"> <docinfo> <date>2000-11-24</date> @@ -98,8 +98,9 @@ SET default_transaction_isolation = '<replaceable>value</replaceable>' <para> SERIALIZABLE is the default level in <acronym>SQL</acronym>. - Postgres does not provide the isolation levels <option>READ - UNCOMMITTED</option> and <option>REPEATABLE READ</option>. Because + <productname>PostgreSQL</productname> does not provide the + isolation levels <option>READ UNCOMMITTED</option> + and <option>REPEATABLE READ</option>. Because of multi-version concurrency control, the serializable level is not truly serializable. See the <citetitle>User's Guide</citetitle> for details. @@ -109,7 +110,8 @@ SET default_transaction_isolation = '<replaceable>value</replaceable>' In <acronym>SQL</acronym> there are two other transaction characteristics that can be set with these commands: whether the 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> </refsect2> </refsect1> diff --git a/doc/src/sgml/ref/show.sgml b/doc/src/sgml/ref/show.sgml index 93e4bb4aff..a5e0d7735a 100644 --- a/doc/src/sgml/ref/show.sgml +++ b/doc/src/sgml/ref/show.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/show.sgml,v 1.14 2001/09/14 08:47:00 ishii Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/show.sgml,v 1.15 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-SHOW"> @@ -120,7 +120,7 @@ NOTICE: geqo is on <para> The <command>SHOW</command> command is a - <productname>Postgres</productname> extension. + <productname>PostgreSQL</productname> extension. </para> </refsect1> </refentry> diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml index 6d413fd7ad..31ffd050c7 100644 --- a/doc/src/sgml/ref/truncate.sgml +++ b/doc/src/sgml/ref/truncate.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.4 2001/11/18 21:14:20 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.5 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-TRUNCATE"> diff --git a/doc/src/sgml/ref/unlisten.sgml b/doc/src/sgml/ref/unlisten.sgml index 6d23fc76b6..df0c4e1f94 100644 --- a/doc/src/sgml/ref/unlisten.sgml +++ b/doc/src/sgml/ref/unlisten.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.16 2001/09/13 15:55:24 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.17 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-UNLISTEN"> @@ -93,7 +93,7 @@ UNLISTEN { <replaceable class="PARAMETER">notifyname</replaceable> | * } <command>UNLISTEN</command> is used to remove an existing <command>NOTIFY</command> registration. 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>. The special condition wildcard <literal>*</literal> cancels all listener registrations for the current session. diff --git a/doc/src/sgml/ref/update.sgml b/doc/src/sgml/ref/update.sgml index 7649042885..baf13a6ac8 100644 --- a/doc/src/sgml/ref/update.sgml +++ b/doc/src/sgml/ref/update.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.17 2001/09/13 15:55:24 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.18 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-UPDATE"> @@ -64,7 +64,7 @@ UPDATE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> SET <replacea <term><replaceable class="PARAMETER">fromlist</replaceable></term> <listitem> <para> - A <productname>Postgres</productname> + A <productname>PostgreSQL</productname> non-standard extension to allow columns from other tables to appear in the WHERE condition. </para> diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml index 35394662f9..d103873589 100644 --- a/doc/src/sgml/ref/vacuum.sgml +++ b/doc/src/sgml/ref/vacuum.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.21 2001/11/18 22:17:30 tgl Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.22 2001/12/08 03:24:39 thomas Exp $ +PostgreSQL documentation --> <refentry id="SQL-VACUUM"> @@ -163,7 +163,7 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28; </title> <para> <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 their table; they remain present until a <command>VACUUM</command> is done. Therefore it's necessary to do <command>VACUUM</command> @@ -226,7 +226,7 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28; ANALYZE</command> command for the affected table. This will update the system catalogs with 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. </para> diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml index 487401b1e1..57420d6f51 100644 --- a/doc/src/sgml/ref/vacuumdb.sgml +++ b/doc/src/sgml/ref/vacuumdb.sgml @@ -1,6 +1,6 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.19 2001/11/28 20:49:10 petere Exp $ -Postgres documentation +$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.20 2001/12/08 03:24:40 thomas Exp $ +PostgreSQL documentation --> <refentry id="APP-VACUUMDB"> |