From 2a5b6a7c9bf40b0983e78d6027eba19b34cb90bd Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 11 Sep 2003 21:42:20 +0000 Subject: This patch fixes a few missed GUC variables that were still upper case, makes a few more small improvements to runtime.sgml, and makes some SGML conventions more consistent. Neil Conway --- doc/src/sgml/ref/copy.sgml | 8 ++++---- doc/src/sgml/ref/create_function.sgml | 4 ++-- doc/src/sgml/ref/create_index.sgml | 6 +++--- doc/src/sgml/ref/declare.sgml | 8 ++++---- doc/src/sgml/ref/end.sgml | 8 ++++---- doc/src/sgml/ref/grant.sgml | 6 +++--- doc/src/sgml/ref/load.sgml | 4 ++-- doc/src/sgml/ref/lock.sgml | 4 ++-- doc/src/sgml/ref/pg_dump.sgml | 4 ++-- doc/src/sgml/ref/pg_restore.sgml | 4 ++-- doc/src/sgml/ref/reindex.sgml | 13 +++++++------ doc/src/sgml/ref/select.sgml | 21 +++++++++++---------- doc/src/sgml/ref/set_constraints.sgml | 7 ++++--- doc/src/sgml/ref/set_session_auth.sgml | 6 +++--- doc/src/sgml/ref/set_transaction.sgml | 4 ++-- doc/src/sgml/ref/update.sgml | 5 +++-- 16 files changed, 58 insertions(+), 54 deletions(-) (limited to 'doc/src/sgml/ref') diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index 24dc567acf7..5df52ca36b7 100644 --- a/doc/src/sgml/ref/copy.sgml +++ b/doc/src/sgml/ref/copy.sgml @@ -1,5 +1,5 @@ @@ -201,7 +201,7 @@ COPY table [ ( table [ ( @@ -382,7 +382,7 @@ CREATE FUNCTION add(integer, integer) RETURNS integer A CREATE FUNCTION command is defined in SQL99. - The PostgreSQL version is similar but + The PostgreSQL version is similar but not fully compatible. The attributes are not portable, neither are the different available languages. diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index 3081f68ac85..28140997f5a 100644 --- a/doc/src/sgml/ref/create_index.sgml +++ b/doc/src/sgml/ref/create_index.sgml @@ -1,5 +1,5 @@ @@ -53,7 +53,7 @@ CREATE [ UNIQUE ] INDEX index_name - PostgreSQL provides the index methods + PostgreSQL provides the index methods B-tree, R-tree, hash, and GiST. The B-tree index method is an implementation of Lehman-Yao high-concurrency B-trees. The R-tree index method implements standard R-trees using Guttman's quadratic @@ -198,7 +198,7 @@ CREATE [ UNIQUE ] INDEX index_name Currently, only the B-tree and GiST index methods support multicolumn indexes. Up to 32 fields may be specified by default. (This limit can be altered when building - PostgreSQL.) Only B-tree currently + PostgreSQL.) Only B-tree currently supports unique indexes. diff --git a/doc/src/sgml/ref/declare.sgml b/doc/src/sgml/ref/declare.sgml index 2bd6ed82af7..1a3e3ccaffe 100644 --- a/doc/src/sgml/ref/declare.sgml +++ b/doc/src/sgml/ref/declare.sgml @@ -1,5 +1,5 @@ @@ -105,9 +105,9 @@ DECLARE cursorname [ BINARY ] [ INS Indicates that data retrieved from the cursor should be unaffected by updates to the tables underlying the cursor while - the cursor exists. In PostgreSQL, all cursors are insensitive; - this key word currently has no effect and is present for - compatibility with the SQL standard. + the cursor exists. In PostgreSQL, + all cursors are insensitive; this key word currently has no + effect and is present for compatibility with the SQL standard. diff --git a/doc/src/sgml/ref/end.sgml b/doc/src/sgml/ref/end.sgml index a56539f37b7..7772184ae83 100644 --- a/doc/src/sgml/ref/end.sgml +++ b/doc/src/sgml/ref/end.sgml @@ -1,5 +1,5 @@ @@ -30,9 +30,9 @@ END [ WORK | TRANSACTION ] END commits the current transaction. All changes made by the transaction become visible to others and are guaranteed - to be durable if a crash occurs. It is a PostgreSQL extension that - is equivalent to . + to be durable if a crash occurs. It is a + PostgreSQL extension that is equivalent + to . diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml index c0ee3055178..d0fb343bbd9 100644 --- a/doc/src/sgml/ref/grant.sgml +++ b/doc/src/sgml/ref/grant.sgml @@ -1,5 +1,5 @@ @@ -375,8 +375,8 @@ GRANT privileges The RULE privilege, and privileges on - databases, schemas, languages, and sequences are PostgreSQL - extensions. + databases, schemas, languages, and sequences are + PostgreSQL extensions. diff --git a/doc/src/sgml/ref/load.sgml b/doc/src/sgml/ref/load.sgml index c62c85f5823..aef72fe6466 100644 --- a/doc/src/sgml/ref/load.sgml +++ b/doc/src/sgml/ref/load.sgml @@ -1,5 +1,5 @@ @@ -50,7 +50,7 @@ LOAD 'filename' Compatibility - LOAD is a PostgreSQL + LOAD is a PostgreSQL extension. diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index 8c24cfb6177..efa828954d2 100644 --- a/doc/src/sgml/ref/lock.sgml +++ b/doc/src/sgml/ref/lock.sgml @@ -1,5 +1,5 @@ @@ -201,7 +201,7 @@ COMMIT WORK; There is no LOCK TABLE in the SQL standard, which instead uses SET TRANSACTION to specify - concurrency levels on transactions. PostgreSQL supports that too; + concurrency levels on transactions. PostgreSQL supports that too; see for details. diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 57eae7fcc9e..80dd35041f9 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ @@ -705,7 +705,7 @@ CREATE DATABASE foo WITH TEMPLATE template0; The pg_dump utility first appeared in Postgres95 release 0.02. The non-plain-text output formats were introduced in - PostgreSQL release 7.1. + PostgreSQL release 7.1. diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index 77d7860e4ca..1600925af84 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -1,4 +1,4 @@ - + @@ -659,7 +659,7 @@ CREATE DATABASE foo WITH TEMPLATE template0; The pg_restore utility first appeared in - PostgreSQL 7.1. + PostgreSQL 7.1. diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml index b919f2c53cf..29b96e462c3 100644 --- a/doc/src/sgml/ref/reindex.sgml +++ b/doc/src/sgml/ref/reindex.sgml @@ -1,5 +1,5 @@ @@ -46,11 +46,12 @@ REINDEX { DATABASE | TABLE | INDEX } name The index in question contains a lot of dead index pages that - are not being reclaimed. This can occur with B-tree indexes in PostgreSQL - under certain access patterns. REINDEX - provides a way to reduce the space consumption of the index by - writing a new version of the index without the dead pages. See - for more information. + are not being reclaimed. This can occur with B-tree indexes in + PostgreSQL under certain access + patterns. REINDEX provides a way to reduce + the space consumption of the index by writing a new version of + the index without the dead pages. See for more information. diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml index 9bfe0e90938..f2b4c2c37cb 100644 --- a/doc/src/sgml/ref/select.sgml +++ b/doc/src/sgml/ref/select.sgml @@ -1,5 +1,5 @@ @@ -798,10 +798,10 @@ FOR UPDATE [ OF table_name [, ...] FOR UPDATE may appear before - LIMIT for compatibility with PostgreSQL - versions before 7.3. It effectively executes after - LIMIT, however, and so that is the recommended - place to write it. + LIMIT for compatibility with + PostgreSQL versions before 7.3. It + effectively executes after LIMIT, however, and + so that is the recommended place to write it. @@ -1008,11 +1008,12 @@ SELECT d.* FROM distributors d; SELECT distributors.* FROM distributors d, distributors distributors; that he will actually get. To help detect this sort of mistake, - PostgreSQL will warn if the implicit-FROM - feature is used in a SELECT statement that also - contains an explicit FROM clause. Also, it is - possible to disable the implicit-FROM feature - by setting the ADD_MISSING_FROM parameter to false. + PostgreSQL will warn if the + implicit-FROM feature is used in a + SELECT statement that also contains an explicit + FROM clause. Also, it is possible to disable + the implicit-FROM feature by setting the + ADD_MISSING_FROM parameter to false. diff --git a/doc/src/sgml/ref/set_constraints.sgml b/doc/src/sgml/ref/set_constraints.sgml index 2a5f3ea8eac..dda66538095 100644 --- a/doc/src/sgml/ref/set_constraints.sgml +++ b/doc/src/sgml/ref/set_constraints.sgml @@ -1,4 +1,4 @@ - + SET CONSTRAINTS @@ -77,8 +77,9 @@ SET CONSTRAINTS { ALL | constraint This command complies with the behavior defined in the SQL - standard, except for the limitation that, in PostgreSQL, it only - applies to foreign-key constraints. + standard, except for the limitation that, in + PostgreSQL, it only applies to + foreign-key constraints. diff --git a/doc/src/sgml/ref/set_session_auth.sgml b/doc/src/sgml/ref/set_session_auth.sgml index 1978b0bbab5..41c88a9f952 100644 --- a/doc/src/sgml/ref/set_session_auth.sgml +++ b/doc/src/sgml/ref/set_session_auth.sgml @@ -1,4 +1,4 @@ - + SET SESSION AUTHORIZATION @@ -89,10 +89,10 @@ SELECT SESSION_USER, CURRENT_USER; The SQL standard allows some other expressions to appear in place of the literal username which are not - important in practice. PostgreSQL + important in practice. PostgreSQL allows identifier syntax ("username"), which SQL does not. SQL does not allow this command during a transaction; - PostgreSQL does not make this + PostgreSQL does not make this restriction because there is no reason to. The privileges necessary to execute this command are left implementation-defined by the standard. diff --git a/doc/src/sgml/ref/set_transaction.sgml b/doc/src/sgml/ref/set_transaction.sgml index 12ebb2f61ce..cbe41d7175f 100644 --- a/doc/src/sgml/ref/set_transaction.sgml +++ b/doc/src/sgml/ref/set_transaction.sgml @@ -1,4 +1,4 @@ - + SET TRANSACTION @@ -122,7 +122,7 @@ SET default_transaction_isolation = 'value' Both commands are defined in the SQL standard. SERIALIZABLE is the default transaction - isolation level in the standard; in PostgreSQL the default is + isolation level in the standard; in PostgreSQL the default is ordinarily READ COMMITTED, but you can change it as described above. PostgreSQL does not provide the isolation levels READ UNCOMMITTED diff --git a/doc/src/sgml/ref/update.sgml b/doc/src/sgml/ref/update.sgml index 160eb5ea18e..01917b362df 100644 --- a/doc/src/sgml/ref/update.sgml +++ b/doc/src/sgml/ref/update.sgml @@ -1,5 +1,5 @@ @@ -164,7 +164,8 @@ UPDATE weather SET temp_lo = temp_lo+1, temp_hi = temp_lo+15, prcp = DEFAULT This command conforms to the SQL standard. The - FROM clause is a PostgreSQL extension. + FROM clause is a + PostgreSQL extension. -- cgit v1.2.3