diff options
Diffstat (limited to 'doc/src/sgml/ref')
31 files changed, 177 insertions, 274 deletions
diff --git a/doc/src/sgml/ref/abort.sgml b/doc/src/sgml/ref/abort.sgml index 062e6603322..017d4d7036e 100644 --- a/doc/src/sgml/ref/abort.sgml +++ b/doc/src/sgml/ref/abort.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/abort.sgml,v 1.6 2000/03/26 18:32:27 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/abort.sgml,v 1.7 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -129,7 +129,7 @@ ABORT WORK; SQL92 </title> <para> - This command is a <productname>PostgreSQL</productname> extension present + This command is a <productname>Postgres</productname> extension present for historical reasons. <command>ROLLBACK</command> is the <acronym>SQL92</acronym> equivalent command. </para> diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index 54d06e5ce55..ca302cf7987 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.10 2000/01/29 16:58:27 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.11 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -247,7 +247,7 @@ ALTER TABLE distributors RENAME TO suppliers; <para> SQL92 specifies some additional capabilities for <command>ALTER TABLE</command> - statement which are not yet directly supported by <productname>PostgreSQL</productname>: + statement which are not yet directly supported by <productname>Postgres</productname>: <variablelist> <varlistentry> @@ -308,8 +308,8 @@ DROP TABLE temp; </para> <para> - The clauses to rename columns and tables are <productname>PostgreSQL</productname> - extensions. SQL92 does not provide for them. + The clauses to rename columns and tables are <productname>Postgres</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 f3ce32bb16f..d97648e0521 100644 --- a/doc/src/sgml/ref/alter_user.sgml +++ b/doc/src/sgml/ref/alter_user.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.10 2000/01/14 22:11:32 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.11 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -138,7 +138,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>PostgreSQL</productname> account. Only a database superuser + <productname>Postgres</productname> account. Only a database superuser can change privileges and password expiration with this command. Ordinary users can only change their own password. </para> diff --git a/doc/src/sgml/ref/begin.sgml b/doc/src/sgml/ref/begin.sgml index 1ee645c7711..8f7eae33c5f 100644 --- a/doc/src/sgml/ref/begin.sgml +++ b/doc/src/sgml/ref/begin.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/begin.sgml,v 1.10 2000/01/29 16:58:27 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/begin.sgml,v 1.11 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -95,7 +95,7 @@ NOTICE: BEGIN: already a transaction in progress </title> <para> - By default, <productname>PostgreSQL</productname> executes transactions + By default, <productname>Postgres</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>PostgreSQL</productname> + <productname>Postgres</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>PostgreSQL</productname> + If the transaction is committed, <productname>Postgres</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>PostgreSQL</productname> language extension. + is a <productname>Postgres</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/create_database.sgml b/doc/src/sgml/ref/create_database.sgml index c8de74eee51..00dae61b2b3 100644 --- a/doc/src/sgml/ref/create_database.sgml +++ b/doc/src/sgml/ref/create_database.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.12 2000/03/26 18:32:27 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.13 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -157,7 +157,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> [ WITH LOCATIO </title> <para> <command>CREATE DATABASE</command> creates a new - <productname>PostgreSQL</productname> database. + <productname>Postgres</productname> database. The creator becomes the owner of the new database. </para> diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml index 3333171319b..708d0745eec 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.12 2000/03/26 18:32:27 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.13 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -20,26 +20,24 @@ Postgres documentation </refnamediv> <refsynopsisdiv> <refsynopsisdivinfo> - <date>1999-10-02</date> + <date>2000-03-25</date> </refsynopsisdivinfo> <synopsis> CREATE FUNCTION <replaceable class="parameter">name</replaceable> ( [ <replaceable class="parameter">ftype</replaceable> [, ...] ] ) RETURNS <replaceable class="parameter">rtype</replaceable> - [ WITH ( <replaceable class="parameter">attribute</replaceable> [, ...] ) ] AS <replaceable class="parameter">definition</replaceable> LANGUAGE '<replaceable class="parameter">langname</replaceable>' - - + [ WITH ( <replaceable class="parameter">attribute</replaceable> [, ...] ) ] CREATE FUNCTION <replaceable class="parameter">name</replaceable> ( [ <replaceable class="parameter">ftype</replaceable> [, ...] ] ) RETURNS <replaceable class="parameter">rtype</replaceable> - [ WITH ( <replaceable class="parameter">attribute</replaceable> [, ...] ) ] AS <replaceable class="parameter">obj_file</replaceable> , <replaceable class="parameter">link_symbol</replaceable> LANGUAGE 'C' + [ WITH ( <replaceable class="parameter">attribute</replaceable> [, ...] ) ] </synopsis> <refsect2 id="R2-SQL-CREATEFUNCTION-1"> <refsect2info> - <date>1998-09-09</date> + <date>2000-03-25</date> </refsect2info> <title> Inputs @@ -143,7 +141,7 @@ CREATE FUNCTION <replaceable class="parameter">name</replaceable> ( [ <replaceab <refsect2 id="R2-SQL-CREATEFUNCTION-2"> <refsect2info> - <date>1998-09-09</date> + <date>2000-03-25</date> </refsect2info> <title> Outputs @@ -168,7 +166,7 @@ CREATE <refsect1 id="R1-SQL-CREATEFUNCTION-1"> <refsect1info> - <date>1998-09-09</date> + <date>2000-03-25</date> </refsect1info> <title> Description @@ -177,28 +175,29 @@ CREATE <command>CREATE FUNCTION</command> allows a <productname>Postgres</productname> user to register a function - with a database. Subsequently, this user is treated as the + with a database. Subsequently, this user is considered the owner of the function. </para> <refsect2 id="R2-SQL-CREATEFUNCTION-3"> <refsect2info> - <date>1998-09-09</date> + <date>2000-03-25</date> </refsect2info> <title> Notes </title> + <para> - Refer to the chapter in - the <citetitle>PostgreSQL Programmer's Guide</citetitle> - on extending + Refer to the chapter in the + <citetitle>PostgreSQL Programmer's Guide</citetitle> + on the topic of extending <productname>Postgres</productname> via functions for further information on writing external functions. </para> <para> Use <command>DROP FUNCTION</command> - to drop user-defined functions. + to remove user-defined functions. </para> <para> @@ -207,7 +206,17 @@ CREATE so long as they have distinct argument types. This facility must be used with caution for <literal>internal</literal> and C-language functions, however. - </para> + </para> + + <para> + The full <acronym>SQL92</acronym> type syntax is allowed for + input arguments and return value. However, some details of the + type specification (e.g. the precision field for + <type>numeric</type> types) are the responsibility of the + underlying function implementation and are silently swallowed + (e.g. not recognized or + enforced) by the <command>CREATE FUNCTION</command> command. + </para> <para> Two <literal>internal</literal> @@ -242,18 +251,18 @@ CREATE <para> To create a simple SQL function: -<programlisting> + <programlisting> CREATE FUNCTION one() RETURNS int4 AS 'SELECT 1 AS RESULT' LANGUAGE 'sql'; SELECT one() AS answer; -<computeroutput> + <computeroutput> answer -------- 1 -</computeroutput> -</programlisting> + </computeroutput> + </programlisting> </para> <para> @@ -317,7 +326,7 @@ Point * complex_to_point (Complex *z) <refsect2 id="R2-SQL-CREATEFUNCTION-4"> <refsect2info> - <date>1998-04-15</date> + <date>2000-03-25</date> </refsect2info> <title> SQL92 @@ -331,7 +340,7 @@ Point * complex_to_point (Complex *z) <refsect2 id="R2-SQL-CREATEFUNCTION-5"> <refsect2info> - <date>1998-09-09</date> + <date>2000-03-25</date> </refsect2info> <title> SQL/PSM @@ -364,7 +373,7 @@ CREATE FUNCTION <replaceable class="parameter">name</replaceable> <!-- Keep this comment at the end of the file Local variables: -mode: sgml +mode:sgml sgml-omittag:nil sgml-shorttag:t sgml-minimize-attributes:nil @@ -374,7 +383,7 @@ sgml-indent-data:t sgml-parent-document:nil sgml-default-dtd-file:"../reference.ced" sgml-exposed-tags:nil -sgml-local-catalogs:"/usr/lib/sgml/catalog" +sgml-local-catalogs:("/usr/lib/sgml/catalog") sgml-local-ecat-files:nil End: --> diff --git a/doc/src/sgml/ref/create_group.sgml b/doc/src/sgml/ref/create_group.sgml index 52023723016..a512d2ff12a 100644 --- a/doc/src/sgml/ref/create_group.sgml +++ b/doc/src/sgml/ref/create_group.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_group.sgml,v 1.1 2000/01/14 22:11:32 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_group.sgml,v 1.2 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -53,7 +53,7 @@ CREATE GROUP <replaceable class="PARAMETER">name</replaceable> <listitem> <para> The <literal>SYSID</literal> clause can be used to choose - the <productname>PostgreSQL</productname> group id of the new + the <productname>Postgres</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_operator.sgml b/doc/src/sgml/ref/create_operator.sgml index 36d791d2a79..c9208222245 100644 --- a/doc/src/sgml/ref/create_operator.sgml +++ b/doc/src/sgml/ref/create_operator.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.12 2000/03/18 18:03:12 tgl Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.13 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -20,7 +20,7 @@ Postgres documentation </refnamediv> <refsynopsisdiv> <refsynopsisdivinfo> - <date>1999-07-20</date> + <date>2000-03-25</date> </refsynopsisdivinfo> <synopsis> CREATE OPERATOR <replaceable>name</replaceable> ( PROCEDURE = <replaceable class="parameter">func_name</replaceable> @@ -32,7 +32,7 @@ CREATE OPERATOR <replaceable>name</replaceable> ( PROCEDURE = <replaceable class <refsect2 id="R2-SQL-CREATEOPERATOR-1"> <refsect2info> - <date>1999-04-14</date> + <date>2000-03-25</date> </refsect2info> <title> Inputs @@ -138,7 +138,7 @@ CREATE OPERATOR <replaceable>name</replaceable> ( PROCEDURE = <replaceable class <refsect2 id="R2-SQL-CREATEOPERATOR-2"> <refsect2info> - <date>1999-04-14</date> + <date>2000-03-25</date> </refsect2info> <title> Outputs @@ -162,7 +162,7 @@ CREATE <refsect1 id="R1-SQL-CREATEOPERATOR-1"> <refsect1info> - <date>1999-04-14</date> + <date>2000-03-25</date> </refsect1info> <title> Description @@ -248,13 +248,13 @@ CREATE Hence, the query optimizer could freely convert: <programlisting> -"0,0,1,1"::box >>> MYBOXES.description +box '((0,0),(1,1))' >>> MYBOXES.description </programlisting> to <programlisting> -MYBOXES.description <<< "0,0,1,1"::box +MYBOXES.description <<< box '((0,0),(1,1))' </programlisting> </para> <para> @@ -269,11 +269,11 @@ MYBOXES.description <<< "0,0,1,1"::box equal, !==. The negator link allows the query optimizer to simplify <programlisting> -NOT MYBOXES.description === "0,0,1,1"::box +NOT MYBOXES.description === box '((0,0),(1,1))' </programlisting> to <programlisting> -MYBOXES.description !== "0,0,1,1"::box +MYBOXES.description !== box '((0,0),(1,1))' </programlisting> </para> <para> @@ -331,7 +331,7 @@ MYBOXES.description !== "0,0,1,1"::box The RESTRICT and JOIN options assist the query optimizer in estimating result sizes. If a clause of the form: <programlisting> -MYBOXES.description <<< "0,0,1,1"::box +MYBOXES.description <<< box '((0,0),(1,1))' </programlisting> is present in the qualification, then <productname>Postgres</productname> may have to @@ -342,7 +342,7 @@ MYBOXES.description <<< "0,0,1,1"::box <command>CREATE FUNCTION</command>) which accepts arguments of the correct data types and returns a floating point number. The query optimizer simply calls this function, passing the - parameter "0,0,1,1" and multiplies the result by the relation + parameter <literal>((0,0),(1,1))</literal> and multiplies the result by the relation size to get the expected number of instances. </para> <para> @@ -356,11 +356,11 @@ MYBOXES.description <<< "0,0,1,1"::box <para> The difference between the function <programlisting> -my_procedure_1 (MYBOXES.description, "0,0,1,1"::box) +my_procedure_1 (MYBOXES.description, box '((0,0),(1,1))') </programlisting> and the operator <programlisting> -MYBOXES.description === "0,0,1,1"::box +MYBOXES.description === box '((0,0),(1,1))' </programlisting> is that <productname>Postgres</productname> attempts to optimize operators and can @@ -373,7 +373,7 @@ MYBOXES.description === "0,0,1,1"::box <refsect2 id="R2-SQL-CREATEOPERATOR-3"> <refsect2info> - <date>1999-04-14</date> + <date>2000-03-25</date> </refsect2info> <title> Notes @@ -418,7 +418,7 @@ CREATE OPERATOR === ( <refsect2 id="R2-SQL-CREATEOPERATOR-4"> <refsect2info> - <date>1999-04-14</date> + <date>2000-03-25</date> </refsect2info> <title> SQL92 diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 9a25bc1b5ee..5d85c3b157f 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.17 1999/07/22 15:09:08 thomas Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.18 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -20,7 +20,7 @@ Postgres documentation </refnamediv> <refsynopsisdiv> <refsynopsisdivinfo> - <date>1999-07-20</date> + <date>2000-03-25</date> </refsynopsisdivinfo> <synopsis> CREATE [ TEMPORARY | TEMP ] TABLE <replaceable class="PARAMETER">table</replaceable> ( @@ -35,9 +35,6 @@ CREATE [ TEMPORARY | TEMP ] TABLE <replaceable class="PARAMETER">table</replacea </synopsis> <refsect2 id="R2-SQL-CREATETABLE-1"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Inputs </title> @@ -158,9 +155,6 @@ CREATE [ TEMPORARY | TEMP ] TABLE <replaceable class="PARAMETER">table</replacea </refsect2> <refsect2 id="R2-SQL-CREATETABLE-2"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Outputs </title> @@ -212,9 +206,6 @@ ERROR: DEFAULT: type mismatched </refsynopsisdiv> <refsect1 id="R1-SQL-CREATETABLE-1"> - <refsect1info> - <date>1998-09-11</date> - </refsect1info> <title> Description </title> @@ -272,9 +263,6 @@ ERROR: DEFAULT: type mismatched </refsect1> <refsect1 id="R1-SQL-DEFAULTCLAUSE-1"> - <refsect1info> - <date>1998-09-11</date> - </refsect1info> <title id="R1-SQL-DEFAULTCLAUSE-1-TITLE"> DEFAULT Clause </title> @@ -284,9 +272,6 @@ DEFAULT <replaceable class="PARAMETER">value</replaceable> </synopsis> </para> <refsect2 id="R2-SQL-DEFAULTCLAUSE-1"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Inputs </title> @@ -323,9 +308,6 @@ DEFAULT <replaceable class="PARAMETER">value</replaceable> </refsect2> <refsect2 id="R2-SQL-DEFAULTCLAUSE-2"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Outputs </title> @@ -335,9 +317,6 @@ DEFAULT <replaceable class="PARAMETER">value</replaceable> </refsect2> <refsect2 id="R2-SQL-DEFAULTCLAUSE-3"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Description </title> @@ -415,7 +394,7 @@ DEFAULT <replaceable class="PARAMETER">value</replaceable> </para> <para> - In the current release (v6.5), <productname>Postgres</productname> + In the current release (v7.0), <productname>Postgres</productname> evaluates all default expressions at the time the table is defined. Hence, functions which are "non-cacheable" such as <function>CURRENT_TIMESTAMP</function> may not produce the desired @@ -431,9 +410,6 @@ DEFAULT <replaceable class="PARAMETER">value</replaceable> </para> </refsect2> <refsect2 id="R2-SQL-DEFAULTCLAUSE-4"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Usage </title> @@ -467,9 +443,6 @@ CREATE TABLE distributors ( </refsect1> <refsect1 id="R1-SQL-COLUMNCONSTRAINT-1"> - <refsect1info> - <date>1998-09-11</date> - </refsect1info> <title id="R1-SQL-COLUMNCONSTRAINT-1-TITLE"> Column CONSTRAINT Clause </title> @@ -482,9 +455,6 @@ CREATE TABLE distributors ( </para> <refsect2 id="R2-SQL-COLUMNCONSTRAINT-1"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Inputs </title> @@ -561,9 +531,6 @@ CREATE TABLE distributors ( </refsect2> <refsect2 id="R2-SQL-COLUMNCONSTRAINT-2"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Description </title> @@ -601,21 +568,19 @@ CREATE TABLE distributors ( <member>UNIQUE</member> <member>CHECK</member> <member>NOT NULL</member> - </simplelist></para> + </simplelist> + </para> + <note> <para> - <productname>Postgres</productname> does not yet - (at release 6.5) support - REFERENCES integrity constraints. The parser - accepts the REFERENCES syntax but ignores the clause. + <productname>Postgres</productname> now + (new for v7.0) supports + REFERENCES integrity constraints. </para> </note> </refsect2> <refsect2 id="R2-SQL-NOTNULL-1"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> NOT NULL Constraint </title> @@ -630,9 +595,6 @@ CREATE TABLE distributors ( </para> <refsect3 id="R3-SQL-NOTNULL-1"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> Outputs </title> @@ -663,9 +625,6 @@ ERROR: ExecAppend: Fail to add null value in not null attribute "<replaceable c </refsect3> <refsect3 id="R3-SQL-NOTNULL-2"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> Description </title> @@ -674,9 +633,6 @@ ERROR: ExecAppend: Fail to add null value in not null attribute "<replaceable c </refsect3> <refsect3 id="R3-SQL-NOTNULL-3"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> Usage </title> @@ -697,9 +653,6 @@ CREATE TABLE distributors ( </refsect2> <refsect2 id="R2-SQL-UNIQUECLAUSE-1"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> UNIQUE Constraint </title> @@ -813,9 +766,6 @@ CREATE TABLE distributors ( </refsect2> <refsect2 id="R2-SQL-CHECK-1"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> The CHECK Constraint </title> @@ -849,9 +799,6 @@ CREATE TABLE distributors ( </refsect3> <refsect3 id="R3-SQL-CHECK-2"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> Outputs </title> @@ -900,9 +847,6 @@ ERROR: ExecAppend: rejected due to CHECK constraint "<replaceable class="parame </refsect2> <refsect2 id="R2-SQL-PRIMARYKEY-1"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> PRIMARY KEY Constraint </title> @@ -958,9 +902,6 @@ ERROR: Cannot insert a duplicate key into a unique index. </refsect3> <refsect3 id="R3-SQL-PRIMARYKEY-3"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> Notes </title> @@ -982,9 +923,6 @@ ERROR: Cannot insert a duplicate key into a unique index. </refsect1> <refsect1 id="R1-SQL-TABLECONSTRAINT-1"> - <refsect1info> - <date>1998-09-11</date> - </refsect1info> <title> Table CONSTRAINT Clause </title> @@ -995,9 +933,6 @@ ERROR: Cannot insert a duplicate key into a unique index. </synopsis> </para> <refsect2 id="R2-SQL-TABLECONSTRAINT-1"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Inputs </title> @@ -1035,9 +970,6 @@ ERROR: Cannot insert a duplicate key into a unique index. </refsect2> <refsect2 id="R2-SQL-TABLECONSTRAINT-2"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Outputs </title> @@ -1049,9 +981,6 @@ ERROR: Cannot insert a duplicate key into a unique index. </refsect2> <refsect2 id="R2-SQL-TABLECONSTRAINT-3"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Description </title> @@ -1067,22 +996,17 @@ ERROR: Cannot insert a duplicate key into a unique index. <member>FOREIGN KEY</member> </simplelist> </para> + <note> <para> - <productname>Postgres</productname> does not yet - (as of version 6.5) support FOREIGN KEY - integrity constraints. The parser understands the FOREIGN KEY syntax, - but only prints a notice and otherwise ignores the clause. - Foreign keys may be partially emulated by triggers (See the CREATE TRIGGER - statement). + <productname>Postgres</productname> now + supports FOREIGN KEY + integrity constraints (new for release 7.0). </para> </note> </refsect2> <refsect2 id="R2-SQL-UNIQUECLAUSE-4"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> UNIQUE Constraint </title> @@ -1174,9 +1098,6 @@ CREATE TABLE distributors ( </refsect2> <refsect2 id="R2-SQL-PRIMARYKEY-4"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> PRIMARY KEY Constraint </title> @@ -1375,9 +1296,6 @@ CREATE TABLE distributors ( </para> <refsect2 id="R2-SQL-CREATETABLE-3"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> Notes </title> @@ -1395,9 +1313,6 @@ CREATE TABLE distributors ( </title> <refsect2 id="R2-SQL-CREATETABLE-4"> - <refsect2info> - <date>1998-09-11</date> - </refsect2info> <title> SQL92 </title> @@ -1436,9 +1351,6 @@ CREATE TEMPORARY TABLE actors ( </para> <refsect3 id="R3-SQL-UNIQUECLAUSE-1"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> UNIQUE clause </title> @@ -1467,9 +1379,6 @@ CREATE TEMPORARY TABLE actors ( </refsect3> <refsect3 id="R3-SQL-NULL-1"> - <refsect3info> - <date>1998-12-24</date> - </refsect3info> <title> NULL clause </title> @@ -1485,9 +1394,6 @@ CREATE TEMPORARY TABLE actors ( </refsect3> <refsect3 id="R3-SQL-NOTNULL-4"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> NOT NULL clause </title> @@ -1510,9 +1416,6 @@ the column. Not our problem... - Thomas 1998-08-16 <REFSECT3 ID="R3-SQL-DEFAULTCLAUSE-1"> - <REFSECT3INFO> - <DATE>1998-09-11</DATE> - </REFSECT3INFO> <TITLE> DEFAULT clause </TITLE> @@ -1530,9 +1433,6 @@ the column. Not our problem... --> <refsect3 id="R3-SQL-CONSTRAINT-3"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> CONSTRAINT clause </title> @@ -1647,9 +1547,6 @@ CREATE ASSERTION name CHECK ( condition ) <refsect3 id="R3-SQL-CHECK-4"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> CHECK clause </title> @@ -1709,9 +1606,6 @@ ALTER DOMAIN cities </refsect3> <refsect3 id="R3-SQL-PRIMARYKEY-1"> - <refsect3info> - <date>1998-09-11</date> - </refsect3info> <title> PRIMARY KEY clause </title> diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml index da116628cc0..e1364752e67 100644 --- a/doc/src/sgml/ref/create_trigger.sgml +++ b/doc/src/sgml/ref/create_trigger.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.8 1999/07/22 15:09:08 thomas Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.9 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -20,7 +20,7 @@ Postgres documentation </refnamediv> <refsynopsisdiv> <refsynopsisdivinfo> - <date>1999-07-20</date> + <date>2000-03-25</date> </refsynopsisdivinfo> <synopsis> CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTER } { <replaceable class="PARAMETER">event</replaceable> [OR ...] } @@ -152,7 +152,7 @@ CREATE Only the relation owner may create a trigger on this relation. </para> <para> - As of the current release (v6.4), STATEMENT triggers are not implemented. + As of the current release (v7.0), STATEMENT triggers are not implemented. </para> <para> Refer to <command>DROP TRIGGER</command> for information on how to @@ -217,11 +217,6 @@ CREATE TABLE distributors ( ); </programlisting> </para> - - <para> - However, foreign keys are not yet implemented (as of version 6.5) in - <productname>Postgres</productname>. - </para> </refsect2> </refsect1> </refentry> diff --git a/doc/src/sgml/ref/create_type.sgml b/doc/src/sgml/ref/create_type.sgml index 07c2617bf0b..2bdcacba5d0 100644 --- a/doc/src/sgml/ref/create_type.sgml +++ b/doc/src/sgml/ref/create_type.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.11 1999/08/06 13:50:30 thomas Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.12 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -289,8 +289,8 @@ CREATE A "regular" Postgres type can only be 8192 bytes in length. If you need a larger type you must create a Large Object type. The interface for these types is discussed - at length in - <citetitle>The PostgreSQL Programmer's Guide</citetitle>. + at length in the + <citetitle>PostgreSQL Programmer's Guide</citetitle>. The length of all large object types is always VARIABLE. </para> </refsect2> diff --git a/doc/src/sgml/ref/create_user.sgml b/doc/src/sgml/ref/create_user.sgml index 6994837751d..ba389aebe76 100644 --- a/doc/src/sgml/ref/create_user.sgml +++ b/doc/src/sgml/ref/create_user.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_user.sgml,v 1.13 2000/01/14 22:11:32 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_user.sgml,v 1.14 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -56,7 +56,7 @@ CREATE USER <replaceable class="PARAMETER">username</replaceable> <listitem> <para> The <literal>SYSID</literal> clause can be used to choose - the <productname>PostgreSQL</productname> user id of the user + the <productname>Postgres</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. @@ -164,7 +164,7 @@ CREATE USER <replaceable class="PARAMETER">username</replaceable> </title> <para> CREATE USER will add a new user to an instance of - <productname>PostgreSQL</productname>. Refer to the adminstrator's + <productname>Postgres</productname>. Refer to the adminstrator's guide for information about managing users and authentication. You must be a database superuser to use this command. </para> @@ -173,7 +173,7 @@ CREATE USER <replaceable class="PARAMETER">username</replaceable> to change a user's password and privileges, and <xref linkend="SQL-DROPUSER" endterm="SQL-DROPUSER-title"> to remove a user. Use <command>ALTER GROUP</command> to add or remove the user from other groups. - <productname>PostgreSQL</productname> + <productname>Postgres</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 aa25b0746db..95fdece785c 100644 --- a/doc/src/sgml/ref/create_view.sgml +++ b/doc/src/sgml/ref/create_view.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_view.sgml,v 1.8 2000/03/26 18:32:27 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_view.sgml,v 1.9 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -20,15 +20,15 @@ Postgres documentation </refnamediv> <refsynopsisdiv> <refsynopsisdivinfo> - <date>1999-07-20</date> + <date>2000-03-25</date> </refsynopsisdivinfo> <synopsis> CREATE VIEW <replaceable class="PARAMETER">view</replaceable> AS SELECT <replaceable class="PARAMETER">query</replaceable> </synopsis> <refsect2 id="R2-SQL-CREATEVIEW-1"> - <refsect2info> - <date>1998-09-21</date> + <refsect2info> + <date>2000-03-25</date> </refsect2info> <title> Inputs @@ -62,7 +62,7 @@ CREATE VIEW <replaceable class="PARAMETER">view</replaceable> AS SELECT <replace <refsect2 id="R2-SQL-CREATEVIEW-2"> <refsect2info> - <date>1998-09-21</date> + <date>2000-03-25</date> </refsect2info> <title> Outputs @@ -97,13 +97,15 @@ NOTICE create: attribute named "<replaceable class="parameter">column</replaceab <para> The view will be created having a column with an unknown type if you do not specify it. For example, the following command gives - an error: + a warning: <programlisting> CREATE VIEW vista AS SELECT 'Hello World' </programlisting> + whereas this command does not: + <programlisting> -CREATE VIEW vista AS SELECT 'Hello World'::text +CREATE VIEW vista AS SELECT text 'Hello World' </programlisting> </para> </listitem> @@ -115,7 +117,7 @@ CREATE VIEW vista AS SELECT 'Hello World'::text <refsect1 id="R1-SQL-CREATEVIEW-1"> <refsect1info> - <date>1998-09-21</date> + <date>2000-03-25</date> </refsect1info> <title> Description @@ -129,7 +131,7 @@ CREATE VIEW vista AS SELECT 'Hello World'::text <refsect2 id="R2-SQL-CREATEVIEW-3"> <refsect2info> - <date>1998-09-21</date> + <date>2000-03-25</date> </refsect2info> <title> Notes @@ -176,7 +178,7 @@ SELECT * FROM kinds; <refsect2 id="R2-SQL-CREATEVIEW-5"> <refsect2info> - <date>1998-09-21</date> + <date>2000-03-25</date> </refsect2info> <title> SQL92 diff --git a/doc/src/sgml/ref/createdb.sgml b/doc/src/sgml/ref/createdb.sgml index 15b9c14bde6..0bdddc01444 100644 --- a/doc/src/sgml/ref/createdb.sgml +++ b/doc/src/sgml/ref/createdb.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.9 2000/02/10 20:08:55 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.10 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -15,7 +15,7 @@ Postgres documentation <application>createdb</application> </refname> <refpurpose> - Create a new <productname>PostgreSQL</productname> database + Create a new <productname>Postgres</productname> database </refpurpose> </refnamediv> <refsynopsisdiv> @@ -120,7 +120,7 @@ createdb [ <replaceable class="parameter">options</replaceable> ] <replaceable c <listitem> <para> Specifies the name of the database to be created. The name must be - unique among all <productname>PostgreSQL</productname> databases in this installation. + unique among all <productname>Postgres</productname> databases in this installation. The default is to create a database with the same name as the current system user. </para> @@ -196,7 +196,7 @@ createdb [ <replaceable class="parameter">options</replaceable> ] <replaceable c Description </title> <para> - <application>createdb</application> creates a new <productname>PostgreSQL</productname> + <application>createdb</application> creates a new <productname>Postgres</productname> database. The user who executes this command becomes the database owner. </para> @@ -204,7 +204,7 @@ createdb [ <replaceable class="parameter">options</replaceable> ] <replaceable c <application>createdb</application> is a shell script wrapper around the <acronym>SQL</acronym> command <xref linkend="SQL-CREATEDATABASE" endterm="SQL-CREATEDATABASE-title"> via - the <productname>PostgreSQL</productname> interactive terminal + the <productname>Postgres</productname> interactive terminal <xref linkend="APP-PSQL" endterm="APP-PSQL-title">. Thus, there is nothing special about creating databases via this or other methods. This means that the <application>psql</application> must be found by the script and that diff --git a/doc/src/sgml/ref/createlang.sgml b/doc/src/sgml/ref/createlang.sgml index 71de0268840..3cdd4c67317 100644 --- a/doc/src/sgml/ref/createlang.sgml +++ b/doc/src/sgml/ref/createlang.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/createlang.sgml,v 1.4 2000/01/19 20:08:22 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/createlang.sgml,v 1.5 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -15,7 +15,7 @@ Postgres documentation <application>createlang</application> </refname> <refpurpose> - Add a new programming language to a <productname>PostgreSQL</productname> database + Add a new programming language to a <productname>Postgres</productname> database </refpurpose> </refnamediv> <refsynopsisdiv> @@ -145,7 +145,7 @@ createlang [ <replaceable class="parameter">connection options</replaceable> ] - <para> <application>createlang</application> is a utility for adding a new - programming language to a <productname>PostgreSQL</productname> database. + programming language to a <productname>Postgres</productname> database. <application>createlang</application> currently accepts two languages, <literal>plsql</literal> and <literal>pltcl</literal>. </para> diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/createuser.sgml index cf8ff8dfee2..bcecbe1fa86 100644 --- a/doc/src/sgml/ref/createuser.sgml +++ b/doc/src/sgml/ref/createuser.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.8 2000/01/12 19:36:34 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.9 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -15,7 +15,7 @@ Postgres documentation <application>createuser</application> </refname> <refpurpose> - Create a new <productname>PostgreSQL</productname> user + Create a new <productname>Postgres</productname> user </refpurpose> </refnamediv> <refsynopsisdiv> @@ -139,8 +139,8 @@ createuser [ <replaceable class="parameter">options</replaceable> ] [ <replaceab <term><replaceable class="parameter">username</replaceable></term> <listitem> <para> - Specifies the name of the <productname>PostgreSQL</productname> user to be created. - This name must be unique among all <productname>PostgreSQL</productname> users. + Specifies the name of the <productname>Postgres</productname> user to be created. + This name must be unique among all <productname>Postgres</productname> users. </para> </listitem> </varlistentry> @@ -203,7 +203,7 @@ createuser [ <replaceable class="parameter">options</replaceable> ] [ <replaceab </title> <para> <application>createuser</application> creates a - new <productname>PostgreSQL</productname> user. + new <productname>Postgres</productname> user. Only users with <literal>usesuper</literal> set in the <literal>pg_shadow</literal> class can create new <productname>Postgres</productname> users. @@ -213,7 +213,7 @@ createuser [ <replaceable class="parameter">options</replaceable> ] [ <replaceab <application>createuser</application> is a shell script wrapper around the <acronym>SQL</acronym> command <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title"> via - the <productname>PostgreSQL</productname> interactive terminal + the <productname>Postgres</productname> interactive terminal <xref linkend="APP-PSQL" endterm="APP-PSQL-title">. Thus, there is nothing special about creating users via this or other methods. This means that the <application>psql</application> must be found by the script and that diff --git a/doc/src/sgml/ref/drop_user.sgml b/doc/src/sgml/ref/drop_user.sgml index b2a96e0090f..e5502d9eaed 100644 --- a/doc/src/sgml/ref/drop_user.sgml +++ b/doc/src/sgml/ref/drop_user.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_user.sgml,v 1.10 2000/01/14 22:11:32 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_user.sgml,v 1.11 2000/03/27 17:14:42 thomas Exp $ Postgres documentation --> @@ -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>PostgreSQL</productname> + <productname>Postgres</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/dropdb.sgml b/doc/src/sgml/ref/dropdb.sgml index c695e9c9e4b..b699f0b8476 100644 --- a/doc/src/sgml/ref/dropdb.sgml +++ b/doc/src/sgml/ref/dropdb.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.2 1999/12/07 22:41:41 momjian Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.3 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -15,7 +15,7 @@ Postgres documentation <application>dropdb</application> </refname> <refpurpose> - Remove an existing <productname>PostgreSQL</productname> database + Remove an existing <productname>Postgres</productname> database </refpurpose> </refnamediv> <refsynopsisdiv> @@ -109,7 +109,7 @@ dropdb [ <replaceable class="parameter">options</replaceable> ] <replaceable cla <listitem> <para> Specifies the name of the database to be removed. The database - must be one of the existing <productname>PostgreSQL</productname> databases + must be one of the existing <productname>Postgres</productname> databases in this installation. </para> </listitem> @@ -165,7 +165,7 @@ dropdb [ <replaceable class="parameter">options</replaceable> ] <replaceable cla </title> <para> <application>dropdb</application> destroys an existing - <productname>PostgreSQL</productname> database. + <productname>Postgres</productname> database. The user who executes this command must be a database superuser or the owner of the database. </para> @@ -174,7 +174,7 @@ dropdb [ <replaceable class="parameter">options</replaceable> ] <replaceable cla <application>dropdb</application> is a shell script wrapper around the <acronym>SQL</acronym> command <xref linkend="SQL-DROPDATABASE" endterm="SQL-DROPDATABASE-title"> via - the <productname>PostgreSQL</productname> interactive terminal + the <productname>Postgres</productname> interactive terminal <xref linkend="APP-PSQL" endterm="APP-PSQL-title">. Thus, there is nothing special about dropping databases via this or other methods. This means that the <application>psql</application> must be found by the script and that diff --git a/doc/src/sgml/ref/droplang.sgml b/doc/src/sgml/ref/droplang.sgml index 65b2cea8bd4..a2ec00019d1 100644 --- a/doc/src/sgml/ref/droplang.sgml +++ b/doc/src/sgml/ref/droplang.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/droplang.sgml,v 1.2 2000/01/19 20:08:22 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/droplang.sgml,v 1.3 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -15,7 +15,7 @@ Postgres documentation <application>droplang</application> </refname> <refpurpose> - Remove a programming language from a <productname>PostgreSQL</productname> database + Remove a programming language from a <productname>Postgres</productname> database </refpurpose> </refnamediv> <refsynopsisdiv> @@ -146,7 +146,7 @@ droplang [ <replaceable class="parameter">connection options</replaceable> ] --l <para> <application>droplang</application> is a utility for removing an existing programming language from a - <productname>PostgreSQL</productname> database. + <productname>Postgres</productname> database. <application>droplang</application> currently accepts two languages, <literal>plsql</literal> and <literal>pltcl</literal>. </para> diff --git a/doc/src/sgml/ref/dropuser.sgml b/doc/src/sgml/ref/dropuser.sgml index 398bde28e1c..889fd5b9a3c 100644 --- a/doc/src/sgml/ref/dropuser.sgml +++ b/doc/src/sgml/ref/dropuser.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.3 2000/01/12 19:36:34 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.4 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -90,7 +90,7 @@ dropuser [ <replaceable class="parameter">options</replaceable> ] [ <replaceable <term><replaceable class="parameter">username</replaceable></term> <listitem> <para> - Specifies the name of the <productname>PostgreSQL</productname> user to be removed. + Specifies the name of the <productname>Postgres</productname> user to be removed. This name must exist in the <productname>Postgres</productname> installation. You will be prompted for a name if none is specified on the command line. </para> @@ -153,18 +153,18 @@ dropuser [ <replaceable class="parameter">options</replaceable> ] [ <replaceable </title> <para> <application>dropuser</application> removes an existing - <productname>PostgreSQL</productname> user + <productname>Postgres</productname> user <emphasis>and</emphasis> the databases which that user owned. Only users with <literal>usesuper</literal> set in the <literal>pg_shadow</literal> class can destroy - <productname>PostgreSQL</productname> users. + <productname>Postgres</productname> users. </para> <para> <application>dropuser</application> is a shell script wrapper around the <acronym>SQL</acronym> command <xref linkend="SQL-DROPUSER" endterm="SQL-DROPUSER-title"> via - the <productname>PostgreSQL</productname> interactive terminal + the <productname>Postgres</productname> interactive terminal <xref linkend="APP-PSQL" endterm="APP-PSQL-title">. Thus, there is nothing special about removing users via this or other methods. This means that the <application>psql</application> must be found by the script and that diff --git a/doc/src/sgml/ref/end.sgml b/doc/src/sgml/ref/end.sgml index 5292b97e978..10f9f54f13a 100644 --- a/doc/src/sgml/ref/end.sgml +++ b/doc/src/sgml/ref/end.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.2 2000/01/29 16:58:27 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.3 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -94,8 +94,8 @@ NOTICE: COMMIT: no transaction in progress </title> <para> - <command>END</command> is a <productname>PostgreSQL</productname> - synonym for + <command>END</command> is a <productname>Postgres</productname> + extension, and is a synonym for the SQL92-compatible <xref linkend="sql-commit-title" endterm="sql-commit-title">. </para> diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index 19e7674b4fb..48040c98243 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/initdb.sgml,v 1.9 2000/01/20 21:50:54 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/initdb.sgml,v 1.10 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -15,7 +15,7 @@ Postgres documentation <application>initdb</application> </refname> <refpurpose> - Create a new <productname>PostgreSQL</productname> database installation + Create a new <productname>Postgres</productname> database installation </refpurpose> </refnamediv> <refsynopsisdiv> @@ -129,7 +129,7 @@ initdb [ --pgdata|-D <replaceable class="parameter">dbdir</replaceable> ] database in an existing database system, and don't touch anything else. This is useful when you need to upgrade your <literal>template1</literal> database using <application>initdb</application> - from a newer release of <productname>PostgreSQL</productname>, + from a newer release of <productname>Postgres</productname>, or when your <literal>template1</literal> database has become corrupted by some system problem. Normally the contents of <literal>template1</literal> @@ -199,7 +199,7 @@ initdb [ --pgdata|-D <replaceable class="parameter">dbdir</replaceable> ] </title> <para> <application>initdb</application> creates a new - <productname>PostgreSQL</productname> database system. + <productname>Postgres</productname> database system. A database system is a collection of databases that are all administered by the same Unix user and managed by a single postmaster. diff --git a/doc/src/sgml/ref/initlocation.sgml b/doc/src/sgml/ref/initlocation.sgml index e5228e8138b..fa86a4041e6 100644 --- a/doc/src/sgml/ref/initlocation.sgml +++ b/doc/src/sgml/ref/initlocation.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/initlocation.sgml,v 1.6 2000/03/26 18:32:27 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/initlocation.sgml,v 1.7 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -15,7 +15,7 @@ Postgres documentation <application>initlocation</application> </refname> <refpurpose> - Create a secondary <productname>PostgreSQL</productname> database storage area + Create a secondary <productname>Postgres</productname> database storage area </refpurpose> </refnamediv> <refsynopsisdiv> @@ -72,7 +72,7 @@ initlocation <replaceable class="parameter">directory</replaceable> </title> <para> <application>initlocation</application> - creates a new <productname>PostgreSQL</productname> secondary database storage area. + creates a new <productname>Postgres</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 933a04f26a1..27dedecd60d 100644 --- a/doc/src/sgml/ref/insert.sgml +++ b/doc/src/sgml/ref/insert.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/insert.sgml,v 1.6 1999/07/22 15:09:12 thomas Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/insert.sgml,v 1.7 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -193,8 +193,8 @@ INSERT INTO films SELECT * FROM tmp; </para> <para> - Insert into arrays (refer to - <citetitle>The PostgreSQL User's Guide</citetitle> for further + Insert into arrays (refer to the + <citetitle>PostgreSQL User's Guide</citetitle> for further information about arrays): <programlisting> diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index b6a0f0ea7e3..f659f2009f7 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.14 2000/01/24 19:34:13 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.15 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -99,7 +99,8 @@ pg_dump [ -h <replaceable class="parameter">host</replaceable> ] [ -p <replaceab Suppress double quotes around identifiers unless absolutely necessary. This may cause trouble loading this dumped data if there are reserved words used for identifiers. - This was the default behavior in pre-v6.4 <application>pg_dump</application>. + This was the default behavior for + <application>pg_dump</application> prior to v6.4. </para> </listitem> </varlistentry> diff --git a/doc/src/sgml/ref/pg_upgrade.sgml b/doc/src/sgml/ref/pg_upgrade.sgml index 7bb5167d82b..948e76bad2c 100644 --- a/doc/src/sgml/ref/pg_upgrade.sgml +++ b/doc/src/sgml/ref/pg_upgrade.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.8 1999/09/28 15:59:10 momjian Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.9 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -38,7 +38,7 @@ pg_upgrade [ -f <replaceable class="parameter">filename</replaceable> ] <replace <para> <application>pg_upgrade</application> is a utility for upgrading from a previous - PostgreSQL release without reloading all the data. + Postgres release without reloading all the data. Not all <productname>Postgres</productname> release transitions can be handled this way. Check the release notes for details on your installation. </para> diff --git a/doc/src/sgml/ref/pgadmin-ref.sgml b/doc/src/sgml/ref/pgadmin-ref.sgml index 988054f36b5..1f7dcbd135c 100644 --- a/doc/src/sgml/ref/pgadmin-ref.sgml +++ b/doc/src/sgml/ref/pgadmin-ref.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgadmin-ref.sgml,v 1.5 2000/02/02 16:19:54 thomas Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgadmin-ref.sgml,v 1.6 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -41,7 +41,7 @@ pgadmin [ <replaceable class="parameter">datasourcename</replaceable> [ <replace <term><replaceable class="PARAMETER">datasourcename</replaceable></term> <listitem> <para> - The name of an existing PostgreSQL ODBC System or User Data + The name of an existing <productname>Postgres</productname> ODBC System or User Data Source. </para> </listitem> diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index 96f9e64644d..3fd0259c44c 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.6 1999/08/06 13:50:31 thomas Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.7 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -190,7 +190,7 @@ postgres [ -B <replaceable class="parameter">nBuffers</replaceable> ] [ -C ] [ - Dates are accepted by the backend in a wide variety of formats, and for input dates this switch mostly affects the interpretation for ambiguous cases. - See <citetitle>The PostgreSQL User's Guide</citetitle> + See the <citetitle>PostgreSQL User's Guide</citetitle> for more information. </para> </listitem> diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 700257e519b..1a65ddaeee9 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.29 2000/03/21 01:52:12 momjian Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.30 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -16,7 +16,7 @@ Postgres documentation <application>psql</application> </refname> <refpurpose> - <productname>PostgreSQL</productname> interactive terminal + <productname>Postgres</productname> interactive terminal </refpurpose> </refnamediv> @@ -36,8 +36,8 @@ Postgres documentation <para> <application>psql</application> is a terminal-based front-end to - <productname>PostgreSQL</productname>. It enables you to type in queries - interactively, issue them to <productname>PostgreSQL</productname>, and see + <productname>Postgres</productname>. It enables you to type in queries + interactively, issue them to <productname>Postgres</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 @@ -63,7 +63,7 @@ Postgres documentation <title>Connecting To A Database</title> <para> - <application>psql</application> is a regular <productname>PostgreSQL</productname> + <application>psql</application> is a regular <productname>Postgres</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 @@ -316,7 +316,7 @@ testdb=> <term><literal>\copyright</literal></term> <listitem> <para> - Shows the copyright and distribution terms of <application>PostgreSQL</application>. + Shows the copyright and distribution terms of <application>Postgres</application>. </para> </listitem> </varlistentry> @@ -387,7 +387,7 @@ testdb=> <note> <para> - <productname>PostgreSQL</productname> stores the object descriptions in the + <productname>Postgres</productname> stores the object descriptions in the pg_description system table. </para> </note> @@ -637,7 +637,7 @@ Tue Oct 26 21:40:57 CEST 1999 <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>PostgreSQL</productname> + for the databases as well. If your <productname>Postgres</productname> installation was compiled with multibyte encoding support, the encoding scheme of each database is shown as well. @@ -677,7 +677,7 @@ Tue Oct 26 21:40:57 CEST 1999 <listitem> <para> - Stores the file into a <productname>PostgreSQL</productname> <quote>large object</quote>. + Stores the file into a <productname>Postgres</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> @@ -709,7 +709,7 @@ lo_import 152801 <term><literal>\lo_list</literal></term> <listitem> <para> - Shows a list of all <productname>PostgreSQL</productname> <quote>large + Shows a list of all <productname>Postgres</productname> <quote>large objects</quote> currently stored in the database along with their owners. </para> </listitem> @@ -1674,7 +1674,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>PostgreSQL</productname> + is first shown. This way you can study the <productname>Postgres</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. @@ -1770,7 +1770,7 @@ bar <term><envar>LO_TRANSACTION</envar></term> <listitem> <para> - If you use the <productname>PostgreSQL</productname> large object + If you use the <productname>Postgres</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 @@ -1939,7 +1939,7 @@ testdb=> <userinput>\set content `sed -e "s/'/\\\\\\'/g" < my_file.txt`</userinp 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>PostgreSQL</productname> extensions, + array slices and type casts are <productname>Postgres</productname> extensions, hence the conflict.) </para> @@ -2111,7 +2111,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>PostgreSQL</productname>'s + does not seem to use it, you must make sure that <productname>Postgres</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) @@ -2145,7 +2145,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>PostgreSQL</productname>, you might wish to read the Tutorial that + <productname>Postgres</productname>, you might wish to read the Tutorial that is included in the distribution. </para> </note> diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml index 2aa6b8369b3..ab379f72f6a 100644 --- a/doc/src/sgml/ref/select.sgml +++ b/doc/src/sgml/ref/select.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.27 2000/03/26 18:32:27 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.28 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -419,13 +419,15 @@ SELECT title, date_prod + 1 AS newlen FROM films ORDER BY newlen; </programlisting></para> <para> - From release 6.4 of PostgreSQL, it is also possible to ORDER BY - arbitrary expressions, including fields that do not appear in the + It is also possible to ORDER BY + arbitrary expressions (an extension to SQL92), + including fields that do not appear in the SELECT result list. - Thus the following statement is now legal: + Thus the following statement is legal: <programlisting> SELECT name FROM distributors ORDER BY code; </programlisting> + Note that if an ORDER BY item is a simple name that matches both a result column name and an input column name, ORDER BY will interpret it as the result column name. This is the opposite of the choice that @@ -581,7 +583,7 @@ SELECT name FROM distributors ORDER BY code; </para> <para> - As of PostgreSQL 7.0, the + As of <productname>Postgres</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 give for LIMIT and OFFSET. Thus, using diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml index a7308070155..1b4a1eed29c 100644 --- a/doc/src/sgml/ref/vacuumdb.sgml +++ b/doc/src/sgml/ref/vacuumdb.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.7 1999/12/18 08:34:49 momjian Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.8 2000/03/27 17:14:43 thomas Exp $ Postgres documentation --> @@ -15,7 +15,7 @@ Postgres documentation <application>vacuumdb</application> </refname> <refpurpose> - Clean and analyze a <productname>PostgreSQL</productname> database + Clean and analyze a <productname>Postgres</productname> database </refpurpose> </refnamediv> <refsynopsisdiv> @@ -210,7 +210,7 @@ vacuumdb [ <replaceable class="parameter">connection options</replaceable> ] [ - <para> <application>vacuumdb</application> is a utility for cleaning a - <productname>PostgreSQL</productname> database. + <productname>Postgres</productname> database. <application>vacuumdb</application> will also generate internal statistics used by the <productname>Postgres</productname> query optimizer. </para> @@ -219,7 +219,7 @@ vacuumdb [ <replaceable class="parameter">connection options</replaceable> ] [ - <application>vacuumdb</application> is a shell script wrapper around the backend command <xref linkend="SQL-VACUUM" endterm="SQL-VACUUM-title"> via - the <productname>PostgreSQL</productname> interactive terminal + the <productname>Postgres</productname> interactive terminal <xref linkend="APP-PSQL" endterm="APP-PSQL-title">. There is no effective difference between vacuuming databases via this or other methods. <application>psql</application> must be found by the script and |