From f3ad615ce8aeabb3de138a6f2eeb550426061a51 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 20 Sep 2003 20:12:05 +0000 Subject: [PATCH] Fix a batch of speling misteaks identified by Peter's spell-checker tool. --- doc/src/sgml/datetime.sgml | 4 ++-- doc/src/sgml/ecpg.sgml | 6 +++--- doc/src/sgml/features.sgml | 6 +++--- doc/src/sgml/func.sgml | 4 ++-- doc/src/sgml/information_schema.sgml | 8 ++++---- doc/src/sgml/jdbc.sgml | 10 +++++----- doc/src/sgml/libpq.sgml | 4 ++-- doc/src/sgml/mvcc.sgml | 4 ++-- doc/src/sgml/protocol.sgml | 6 +++--- doc/src/sgml/ref/create_sequence.sgml | 4 ++-- doc/src/sgml/ref/ecpg-ref.sgml | 4 ++-- doc/src/sgml/ref/grant.sgml | 4 ++-- doc/src/sgml/ref/notify.sgml | 6 +++--- doc/src/sgml/release.sgml | 16 ++++++++-------- doc/src/sgml/runtime.sgml | 6 +++--- doc/src/sgml/wal.sgml | 9 +++++---- doc/src/sgml/xplang.sgml | 4 ++-- src/backend/catalog/sql_features.txt | 2 +- 18 files changed, 54 insertions(+), 53 deletions(-) diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml index 24acb96f1e8..5f40d81e0a8 100644 --- a/doc/src/sgml/datetime.sgml +++ b/doc/src/sgml/datetime.sgml @@ -1,5 +1,5 @@ @@ -570,7 +570,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.35 2003/09/11 16:22:42 mo AFT +04:30 - Afganistan Time + Afghanistan Time EAST diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index d9856c6d55e..14dda019a62 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -1,5 +1,5 @@ @@ -992,7 +992,7 @@ EXEC SQL WHENEVER SQLERROR STOP; different action was set for the same condition between the first EXEC SQL WHENEVER and the SQL statement causing the condition, regardless of the flow of control in the C program. - So neither of the two following C program exerpts will have the + So neither of the two following C program excerpts will have the desired effect. /* @@ -1072,7 +1072,7 @@ struct If no error occurred in the last SQL statement, sqlca.sqlcode will be 0 and sqlca.sqlstate will be - "00000". If a warning or error occured, then + "00000". If a warning or error occurred, then sqlca.sqlcode will be negative and sqlca.sqlstate will be different from "00000". A positive diff --git a/doc/src/sgml/features.sgml b/doc/src/sgml/features.sgml index 4056d770f18..09e08960202 100644 --- a/doc/src/sgml/features.sgml +++ b/doc/src/sgml/features.sgml @@ -1,5 +1,5 @@ @@ -17,12 +17,12 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.19 2003/09/11 21:42:19 mo The formal name of the SQL standard is ISO/IEC 9075 Database Language SQL. A revised version of the standard is released from time to time; the most recent one appearing in 1999. That - version is refered to as ISO/IEC 9075:1999, or informally as SQL99. + version is referred to as ISO/IEC 9075:1999, or informally as SQL99. The version prior to that was SQL92. PostgreSQL development tends to aim for conformance with the latest official version of the standard where such conformance does not contradict traditional features or common - sense. At the time of this writing, ballotting is under way for a + sense. At the time of this writing, balloting is under way for a new revision of the standard, which, if approved, will eventually become the conformance target for future PostgreSQL development. diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 463e3c7a21e..b97f9f79799 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -1,5 +1,5 @@ @@ -469,7 +469,7 @@ PostgreSQL documentation << - biwise shift left + bitwise shift left 1 << 4 16 diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 87afdbb2109..c4b619e4e59 100644 --- a/doc/src/sgml/information_schema.sgml +++ b/doc/src/sgml/information_schema.sgml @@ -1,4 +1,4 @@ - + The Information Schema @@ -330,7 +330,7 @@ SELECT, INSERT, UPDATE, REFERENCES. If you want to make your applications fit for possible future - developements, it is generally the right choice to use this view + developments, it is generally the right choice to use this view instead of table_privileges if one of those privilege types is concerned. @@ -1508,7 +1508,7 @@ ORDER BY c.ordinal_position; object_type character_data - The type of the object that uses the array being descibed: one + The type of the object that uses the array being described: one of TABLE (the array is used by a column of that table), DOMAIN (the array is used by that domain), ROUTINE (the array is used by @@ -2424,7 +2424,7 @@ ORDER BY c.ordinal_position; objects to a group that the current user is a member of. In PostgreSQL, this currently only applies to domains, and since domains do not have real privileges in - PostgreSQL, this view is empty. Futher + PostgreSQL, this view is empty. Further information can be found under usage_privileges. In the future, this view may contain more useful information. diff --git a/doc/src/sgml/jdbc.sgml b/doc/src/sgml/jdbc.sgml index ec79565fefa..bff52a9668b 100644 --- a/doc/src/sgml/jdbc.sgml +++ b/doc/src/sgml/jdbc.sgml @@ -1,5 +1,5 @@ @@ -262,7 +262,7 @@ jdbc:postgresql://host: - The parametes have the following meanings: + The parameters have the following meanings: @@ -397,7 +397,7 @@ st.close(); Getting results based on a cursor By default the driver collects all the results for the - query at once. This can be inconvieniant for large data sets so + query at once. This can be inconvenient for large data sets so the JDBC driver provides a means of basing a ResultSet on a database cursor and only fetching a small number of rows. @@ -631,7 +631,7 @@ upperProc.close(); as ResultSet values. - Gettig <type>refcursor</type> values from a + <title>Getting <type>refcursor</type> values from a function When calling a function that returns @@ -741,7 +741,7 @@ st.close(); that contains a Large Object reference does not delete the Large Object. Deleting the Large Object is a separate operation that needs to be performed. Large Objects also have some security - issues since anyone connected to the database cann view + issues since anyone connected to the database can view and/or modify any Large Object, even if they don't have permissions to view/update the row containing the Large Object reference. diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 7d91fdf808a..cd2a8f491ff 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1,5 +1,5 @@ @@ -1945,7 +1945,7 @@ It is not thread-safe. PQescapeString escapes a string for use within an SQL -commmand. This is useful when inserting data values as literal constants +command. This is useful when inserting data values as literal constants in SQL commands. Certain characters (such as quotes and backslashes) must be escaped to prevent them from being interpreted specially by the SQL parser. PQescapeString performs this operation. diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index b74d03804c5..edc9b1c267c 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -1,5 +1,5 @@ @@ -661,7 +661,7 @@ ERROR: could not serialize access due to concurrent update - The use of explicit locking can increase the likelyhood of + The use of explicit locking can increase the likelihood of deadlocks, wherein two (or more) transactions each hold locks that the other wants. For example, if transaction 1 acquires an exclusive lock on table A and then tries to acquire diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index 1819a33c07a..ba41fda7932 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -1,4 +1,4 @@ - + Frontend/Backend Protocol @@ -238,7 +238,7 @@ The authentication cycle ends with the server either rejecting the - connection attempt (ErrorResponse), or sending AuthenticationOK. + connection attempt (ErrorResponse), or sending AuthenticationOk. @@ -729,7 +729,7 @@ BEGIN/COMMIT transaction block (close meaning to commit if no error, or roll back if error). Then a ReadyForQuery response is issued. The purpose of Sync is to provide - a resychronization point for error recovery. When an error is detected + a resynchronization point for error recovery. When an error is detected while processing any extended-query message, the backend issues ErrorResponse, then reads and discards messages until a Sync is reached, then issues ReadyForQuery and returns to normal message processing. diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml index 089695b1bbc..dc4b2e776b9 100644 --- a/doc/src/sgml/ref/create_sequence.sgml +++ b/doc/src/sgml/ref/create_sequence.sgml @@ -1,5 +1,5 @@ @@ -230,7 +230,7 @@ SELECT * FROM seqname; Furthermore, although multiple sessions are guaranteed to allocate distinct sequence values, the values may be generated out of - sequence when all the sessions are considered. FFor example, with + sequence when all the sessions are considered. For example, with a cache setting of 10, session A might reserve values 1..10 and return nextval=1, then session B might reserve values diff --git a/doc/src/sgml/ref/ecpg-ref.sgml b/doc/src/sgml/ref/ecpg-ref.sgml index fc4aeef337c..f47c33601b8 100644 --- a/doc/src/sgml/ref/ecpg-ref.sgml +++ b/doc/src/sgml/ref/ecpg-ref.sgml @@ -1,5 +1,5 @@ @@ -42,7 +42,7 @@ PostgreSQL documentation ecpg will convert each input file given on the command line to the corresponding C output file. Input files - preferrably have the extension .pgc, in which + preferably have the extension .pgc, in which case the extension will be replaced by .c to determine the output file name. If the extension of the input file is not .pgc, then the output file name is diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml index d0fb343bbd9..b2ad6310525 100644 --- a/doc/src/sgml/ref/grant.sgml +++ b/doc/src/sgml/ref/grant.sgml @@ -1,5 +1,5 @@ @@ -316,7 +316,7 @@ GRANT SELECT, UPDATE, INSERT ON mytable TO GROUP todos; If the Access privileges column is empty for a given object, -it means the object has default privileges (that is, its privileges columm +it means the object has default privileges (that is, its privileges column is null). Default privileges always include all privileges for the owner, and may include some privileges for PUBLIC depending on the object type, as explained above. The first GRANT or diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml index 60f0d66bfbc..7c9c9fc7f77 100644 --- a/doc/src/sgml/ref/notify.sgml +++ b/doc/src/sgml/ref/notify.sgml @@ -1,5 +1,5 @@ @@ -35,7 +35,7 @@ NOTIFY name - The information passed to the client for a notifiation event includes the notification + The information passed to the client for a notification event includes the notification name and the notifying session's server process PID. It is up to the database designer to define the notification names that will be used in a given database and what each one means. @@ -111,7 +111,7 @@ NOTIFY name are the same, the notification 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. - PostgreSQL keeps self-notifiications + PostgreSQL keeps self-notifications separate from notifications arriving from other sessions, so you cannot miss an outside notification by ignoring your own notifications.) diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index c67e93ba8d8..0414f81e2a4 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,5 +1,5 @@ @@ -782,7 +782,7 @@ Properly escape jdbc setObject() strings to improve security (Barry) Add locale variables (Peter) Escape byes >= 0x7f for multibyte in PQescapeBytea/PQunescapeBytea (Tatsuo) Add locale awareness to regular expression character classes -Enable multibyte support by default (Tatso) +Enable multibyte support by default (Tatsuo) Add GB18030 multibyte support (Bill Huang) Add CREATE/DROP CONVERSION, allowing loadable encodings (Tatsuo, Kaori) Add pg_conversion table (Tatsuo) @@ -1058,7 +1058,7 @@ Properly escape jdbc setObject() strings to improve security (Barry) Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom) Fix for compressed transaction log id wraparound (Tom) Fix PQescapeBytea/PQunescapeBytea so that they handle bytes > 0x7f (Tatsuo) -Fix for psql and pg_dump crashing when invoked with non-existand long options (Tatsuo) +Fix for psql and pg_dump crashing when invoked with non-existent long options (Tatsuo) Fix crash when invoking geometric operators (Tom) Allow OPEN cursor(args) (Tom) Fix for rtree_gist index build (Teodor) @@ -1066,7 +1066,7 @@ Properly escape jdbc setObject() strings to improve security (Barry) contrib/intarray fixes (Oleg) Fix for complex UNION/EXCEPT/INTERSECT queries using parens (Tom) Fix to pg_convert (Tatsuo) -Fix for crash with long DATA strings (Thomes, Neil) +Fix for crash with long DATA strings (Thomas, Neil) Fix for repeat(), lpad(), rpad() and long strings (Neil) @@ -1099,7 +1099,7 @@ Properly escape jdbc setObject() strings to improve security (Barry) Ensure that sequence counters do not go backwards after a crash (Tom) -Fix pgaccess kanji-coversion key binding (Tatsuo) +Fix pgaccess kanji-conversion key binding (Tatsuo) Optimizer improvements (Tom) Cash I/O improvements (Tom) New Russian FAQ @@ -1447,7 +1447,7 @@ Properly escape jdbc setObject() strings to improve security (Barry) New TIMESTAMP WITHOUT TIMEZONE data type (Thomas) Add ISO date/time specification with "T", yyyy-mm-ddThh:mm:ss (Thomas) New xid/int comparison functions (Hiroshi) -Add precision to TIME, TIMESTAMP, and INVERVAL data types (Thomas) +Add precision to TIME, TIMESTAMP, and INTERVAL data types (Thomas) Modify type coercion logic to attempt binary-compatible functions first (Tom) New encode() function installed by default (Marko Kreen) Improved to_*() conversion functions (Karel Zak) @@ -1584,7 +1584,7 @@ Properly escape jdbc setObject() strings to improve security (Barry) Fix for SQLPrimaryKeys in multibyte mode (Hiroshi) Allow ODBC procedure calls (Hiroshi) Improve boolean handing (Aidan Mountford) -Most configuration options on setable via DSN (Hiroshi) +Most configuration options now settable via DSN (Hiroshi) Multibyte, performance fixes (Hiroshi) Allow driver to be used with iODBC or unixODBC (Peter E) MD5 password encryption support (Bruce) @@ -3351,7 +3351,7 @@ Add pg_dump -N flag to force double quotes around identifiers. This is Fix for NOT in where clause causing crash(Bruce) EXPLAIN VERBOSE coredump fix(Vadim) Fix shared-library problems on Linux -Fix test for table existance to allow mixed-case and whitespace in +Fix test for table existence to allow mixed-case and whitespace in the table name(Thomas) Fix a couple of pg_dump bugs Configure matches template/.similar entries better(Tom) diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 853126c9812..21089df6794 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -3119,7 +3119,7 @@ kernel.shmmax = 134217728 - The symptom of this occuring is a kernel message looking like + The symptom of this occurring is a kernel message looking like this (consult your system documentation and configuration on where to look for such a message): @@ -3507,7 +3507,7 @@ openssl req -new -text -out server.req Fill out the information that openssl asks for. Make sure that you enter the local host name as Common Name; the challenge - password can be left blank. The programm will generate a key that is + password can be left blank. The program will generate a key that is passphrase protected; it will not accept a passphrase that is less than four characters long. To remove the passphrase (as you must if you want automatic start-up of the server), run the commands diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 2d3f574e391..352da5bab1b 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -1,4 +1,4 @@ - + Write-Ahead Logging (<acronym>WAL</acronym>) @@ -239,9 +239,10 @@ record to the log with LogInsert but before performing a LogFlush. This delay allows other server processes to add their commit records to the log so as to have all - of them flushed with a single log sync. No sleep will occur if fsync - is not enabled or if fewer than commit_siblings - other sessons are currently in active transactions; this avoids + of them flushed with a single log sync. No sleep will occur if + fsync + is not enabled, nor if fewer than commit_siblings + other sessions are currently in active transactions; this avoids sleeping when it's unlikely that any other session will commit soon. Note that on most platforms, the resolution of a sleep request is ten milliseconds, so that any nonzero commit_delay diff --git a/doc/src/sgml/xplang.sgml b/doc/src/sgml/xplang.sgml index c05c4948a2c..c3482909eaa 100644 --- a/doc/src/sgml/xplang.sgml +++ b/doc/src/sgml/xplang.sgml @@ -1,5 +1,5 @@ @@ -68,7 +68,7 @@ createlang plpgsql template1 A procedural language is installed in a database in three steps, which must be carried out by a database superuser. The - createlang programm automates createlang program automates and . diff --git a/src/backend/catalog/sql_features.txt b/src/backend/catalog/sql_features.txt index 0fe363db5a6..72b17d54e08 100644 --- a/src/backend/catalog/sql_features.txt +++ b/src/backend/catalog/sql_features.txt @@ -13,7 +13,7 @@ B041 Extensions to embedded SQL exception declarations NO B051 Enhanced execution rights NO E011 Numeric data types YES E011 Numeric data types 01 INTEGER and SMALLINT data types YES -E011 Numeric data types 02 REAL, DOUBLE PRECISON, and FLOAT data types YES +E011 Numeric data types 02 REAL, DOUBLE PRECISION, and FLOAT data types YES E011 Numeric data types 03 DECIMAL and NUMERIC data types YES E011 Numeric data types 04 Arithmetic operators YES E011 Numeric data types 05 Numeric comparison YES