From 8c05ca7754bb49526bab106af0049eba55ffa698 Mon Sep 17 00:00:00 2001 From: Neil Conway Date: Mon, 13 Jun 2005 02:40:08 +0000 Subject: [PATCH] SGML cleanup: consistently use "endterm" in s that link to the reference page for SQL commands, so that the link text is italicized. --- doc/src/sgml/ddl.sgml | 38 ++++++++++++++++++---------------- doc/src/sgml/func.sgml | 4 ++-- doc/src/sgml/maintenance.sgml | 15 +++++++------- doc/src/sgml/manage-ag.sgml | 14 +++++++------ doc/src/sgml/mvcc.sgml | 7 ++++--- doc/src/sgml/query.sgml | 5 +++-- doc/src/sgml/ref/psql-ref.sgml | 16 +++++++------- doc/src/sgml/runtime.sgml | 10 +++++---- 8 files changed, 59 insertions(+), 50 deletions(-) diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index b0d413bbea..269f9aab82 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -1,4 +1,4 @@ - + Data Definition @@ -1540,14 +1540,14 @@ ALTER TABLE products RENAME TO items; There are several different privileges: SELECT, INSERT, UPDATE, DELETE, RULE, REFERENCES, TRIGGER, - CREATE, TEMPORARY, EXECUTE, - and USAGE. The privileges applicable to a particular + CREATE, TEMPORARY, EXECUTE, and + USAGE. The privileges applicable to a particular object vary depending on the object's type (table, function, etc). - For complete - information on the different types of privileges supported by - PostgreSQL, refer to the - reference page. The following sections - and chapters will also show you how those privileges are used. + For complete information on the different types of privileges + supported by PostgreSQL, refer to the + reference + page. The following sections and chapters will also show you how + those privileges are used. @@ -1558,8 +1558,9 @@ ALTER TABLE products RENAME TO items; To change the owner of a table, index, sequence, or view, use the - command. There are corresponding - ALTER commands for other object types. + + command. There are corresponding ALTER commands for + other object types. @@ -1596,14 +1597,15 @@ REVOKE ALL ON accounts FROM PUBLIC; - Ordinarily, only the object's owner (or a superuser) can grant or revoke - privileges on an object. However, it is possible to grant a privilege - with grant option, which gives the recipient the right to - grant it in turn to others. If the grant option is subsequently revoked - then all who received the privilege from that recipient (directly or - through a chain of grants) will lose the privilege. For details see - the and reference - pages. + Ordinarily, only the object's owner (or a superuser) can grant or + revoke privileges on an object. However, it is possible to grant a + privilege with grant option, which gives the recipient + the right to grant it in turn to others. If the grant option is + subsequently revoked then all who received the privilege from that + recipient (directly or through a chain of grants) will lose the + privilege. For details see the and reference pages. diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index bc34c96542..22baa22aa6 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -1,5 +1,5 @@ @@ -8152,7 +8152,7 @@ select current_date + s.a as dates from generate_series(0,14,7) as s(a); The session_user is normally the user who initiated the current database connection; but superusers can change this setting - with . + with . The current_user is the user identifier that is applicable for permission checking. Normally, it is equal to the session user, but it changes during the execution of diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 1527a9b743..d68cd817c3 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -1,5 +1,5 @@ @@ -74,12 +74,13 @@ $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.43 2005/05/10 22:27:29 momj - The frequency and scope of the VACUUM operations performed for each of - these reasons will vary depending on the needs of each site. - Therefore, database administrators must understand these issues and - develop an appropriate maintenance strategy. This section concentrates - on explaining the high-level issues; for details about command syntax - and so on, see the reference page. + The frequency and scope of the VACUUM operations + performed for each of these reasons will vary depending on the + needs of each site. Therefore, database administrators must + understand these issues and develop an appropriate maintenance + strategy. This section concentrates on explaining the high-level + issues; for details about command syntax and so on, see the reference page. diff --git a/doc/src/sgml/manage-ag.sgml b/doc/src/sgml/manage-ag.sgml index 49aa764192..e95839f050 100644 --- a/doc/src/sgml/manage-ag.sgml +++ b/doc/src/sgml/manage-ag.sgml @@ -1,5 +1,5 @@ @@ -88,7 +88,7 @@ SELECT datname FROM pg_database; Databases are created with the SQL command - :CREATE + :CREATE DATABASE CREATE DATABASE name; @@ -314,7 +314,7 @@ ALTER DATABASE mydb SET geqo TO off; Databases are destroyed with the command - :DROP DATABASE + :DROP DATABASE DROP DATABASE name; @@ -379,7 +379,8 @@ dropdb dbname - To define a tablespace, use the + To define a tablespace, use the command, for example:CREATE TABLESPACE CREATE TABLESPACE fastspace LOCATION '/mnt/sda1/postgresql/data'; @@ -459,8 +460,9 @@ CREATE TABLE foo(i int); - To remove an empty tablespace, use the - command. + To remove an empty tablespace, use the + command. diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index c88974a8d7..97e351b323 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -1,5 +1,5 @@ @@ -224,7 +224,7 @@ $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.50 2005/04/28 21:47:09 tgl Exp $ To set the transaction isolation level of a transaction, use the - command . + command . @@ -524,7 +524,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2; The list below shows the available lock modes and the contexts in which they are used automatically by PostgreSQL. You can also acquire any - of these locks explicitly with the command . + of these locks explicitly with the command . Remember that all of these lock modes are table-level locks, even if the name contains the word row; the names of the lock modes are historical. diff --git a/doc/src/sgml/query.sgml b/doc/src/sgml/query.sgml index e573db56cb..9c8d0a5a3c 100644 --- a/doc/src/sgml/query.sgml +++ b/doc/src/sgml/query.sgml @@ -1,5 +1,5 @@ @@ -269,7 +269,8 @@ COPY weather FROM '/home/user/weather.txt'; where the file name for the source file must be available to the backend server machine, not the client, since the backend server reads the file directly. You can read more about the - COPY command in . + COPY command in . diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index ee16b1b3e5..64fa55f000 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1,5 +1,5 @@ @@ -1036,9 +1036,9 @@ testdb=> - The commands and - - are used to set access privileges. See + The commands GRANT and + REVOKE are used to set access privileges. + See for more information. @@ -1740,10 +1740,10 @@ lo_import 152801 - The commands and - - are used to set access privileges. See - for more information. + The commands GRANT and + REVOKE are used to set access privileges. + See for + more information. diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index dff9017402..93040bd31d 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -3234,8 +3234,9 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows - Consult and for more - information. + Consult and for more information. @@ -3257,7 +3258,8 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows - Consult for more information. + Consult for more information. -- 2.40.0