From e987e0cda53a17328edf3adc560a61927b873f47 Mon Sep 17 00:00:00 2001 From: Marti Raudsepp Date: Mon, 25 Aug 2014 19:57:17 +0300 Subject: [PATCH 2/3] doc: Fix usages of etc., e.g., i.e., et al. Using two custom rules with Topy: --- doc/src/sgml/advanced.sgml | 2 +- doc/src/sgml/arch-dev.sgml | 2 +- doc/src/sgml/biblio.sgml | 6 ++--- doc/src/sgml/bki.sgml | 4 ++-- doc/src/sgml/config.sgml | 18 +++++++------- doc/src/sgml/cube.sgml | 4 ++-- doc/src/sgml/datatype.sgml | 4 ++-- doc/src/sgml/datetime.sgml | 2 +- doc/src/sgml/ddl.sgml | 4 ++-- doc/src/sgml/docguide.sgml | 8 +++---- doc/src/sgml/ecpg.sgml | 6 ++--- doc/src/sgml/extend.sgml | 4 ++-- doc/src/sgml/func.sgml | 14 +++++------ doc/src/sgml/gin.sgml | 2 +- doc/src/sgml/high-availability.sgml | 8 +++---- doc/src/sgml/install-windows.sgml | 4 ++-- doc/src/sgml/libpq.sgml | 12 +++++----- doc/src/sgml/manage-ag.sgml | 2 +- doc/src/sgml/monitoring.sgml | 2 +- doc/src/sgml/perform.sgml | 2 +- doc/src/sgml/pgbench.sgml | 2 +- doc/src/sgml/pgupgrade.sgml | 22 ++++++++--------- doc/src/sgml/plperl.sgml | 6 ++--- doc/src/sgml/pltcl.sgml | 2 +- doc/src/sgml/protocol.sgml | 26 ++++++++++---------- doc/src/sgml/recovery-config.sgml | 2 +- doc/src/sgml/ref/create_database.sgml | 4 ++-- doc/src/sgml/ref/create_domain.sgml | 2 +- doc/src/sgml/ref/create_event_trigger.sgml | 2 +- doc/src/sgml/ref/create_function.sgml | 2 +- doc/src/sgml/ref/create_table.sgml | 2 +- doc/src/sgml/ref/grant.sgml | 2 +- doc/src/sgml/ref/initdb.sgml | 2 +- doc/src/sgml/ref/pg_dump.sgml | 2 +- doc/src/sgml/ref/pg_dumpall.sgml | 2 +- doc/src/sgml/ref/pg_restore.sgml | 2 +- doc/src/sgml/ref/postgres-ref.sgml | 2 +- doc/src/sgml/ref/psql-ref.sgml | 6 ++--- doc/src/sgml/ref/values.sgml | 2 +- doc/src/sgml/release-7.4.sgml | 8 +++---- doc/src/sgml/release-8.0.sgml | 8 +++---- doc/src/sgml/release-8.1.sgml | 10 ++++---- doc/src/sgml/release-8.2.sgml | 10 ++++---- doc/src/sgml/release-8.3.sgml | 6 ++--- doc/src/sgml/release-8.4.sgml | 4 ++-- doc/src/sgml/release-9.0.sgml | 4 ++-- doc/src/sgml/release-9.1.sgml | 6 ++--- doc/src/sgml/release-9.2.sgml | 6 ++--- doc/src/sgml/release-9.3.sgml | 4 ++-- doc/src/sgml/release-9.4.sgml | 6 ++--- doc/src/sgml/release-old.sgml | 38 +++++++++++++++--------------- doc/src/sgml/runtime.sgml | 4 ++-- doc/src/sgml/sepgsql.sgml | 2 +- doc/src/sgml/sources.sgml | 4 ++-- doc/src/sgml/sslinfo.sgml | 4 ++-- doc/src/sgml/syntax.sgml | 2 +- doc/src/sgml/tsearch2.sgml | 2 +- doc/src/sgml/wal.sgml | 2 +- doc/src/sgml/xfunc.sgml | 6 ++--- doc/src/sgml/xml2.sgml | 4 ++-- 60 files changed, 171 insertions(+), 171 deletions(-) diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml index 1e45511..2b6ed22 100644 --- a/doc/src/sgml/advanced.sgml +++ b/doc/src/sgml/advanced.sgml @@ -225,7 +225,7 @@ UPDATE branches SET balance = balance + 100.00 BEGIN; UPDATE accounts SET balance = balance - 100.00 WHERE name = 'Alice'; --- etc etc +-- etc. etc. COMMIT; diff --git a/doc/src/sgml/arch-dev.sgml b/doc/src/sgml/arch-dev.sgml index c835e87..9daddee 100644 --- a/doc/src/sgml/arch-dev.sgml +++ b/doc/src/sgml/arch-dev.sgml @@ -259,7 +259,7 @@ system catalog lookups can only be done within a transaction, and we do not wish to start a transaction immediately upon receiving a query string. The raw parsing stage is sufficient to identify the transaction - control commands (BEGIN, ROLLBACK, etc), and + control commands (BEGIN, ROLLBACK, etc.), and these can then be correctly executed without any further analysis. Once we know that we are dealing with an actual query (such as SELECT or UPDATE), it is okay to diff --git a/doc/src/sgml/biblio.sgml b/doc/src/sgml/biblio.sgml index e2cd69d..12e59ea 100644 --- a/doc/src/sgml/biblio.sgml +++ b/doc/src/sgml/biblio.sgml @@ -22,7 +22,7 @@ The Practical <acronym>SQL</acronym> Handbook - Bowman et al, 2001 + Bowman et al., 2001 Using SQL Variants Fourth Edition @@ -434,7 +434,7 @@ ssimkovi@ag.or.at <ulink url="http://db.cs.berkeley.edu/papers/ERL-M89-82.pdf"> A commentary on the <productname>POSTGRES</productname> rules system </ulink> - Stonebraker et al, 1989 + Stonebraker et al., 1989 M. @@ -511,7 +511,7 @@ ssimkovi@ag.or.at <ulink url="http://db.cs.berkeley.edu/papers/ERL-M90-36.pdf"> On Rules, Procedures, Caching and Views in Database Systems </ulink> - Stonebraker et al, ACM, 1990 + Stonebraker et al., ACM, 1990 M. diff --git a/doc/src/sgml/bki.sgml b/doc/src/sgml/bki.sgml index aaf500a..39b7a7b 100644 --- a/doc/src/sgml/bki.sgml +++ b/doc/src/sgml/bki.sgml @@ -111,11 +111,11 @@ When bootstrap is specified, the table will only be created on disk; nothing is entered into pg_class, - pg_attribute, etc, for it. Thus the + pg_attribute, etc., for it. Thus the table will not be accessible by ordinary SQL operations until such entries are made the hard way (with insert commands). This option is used for creating - pg_class etc themselves. + pg_class etc. themselves. diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index f23e5dc..f91ab0e 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -248,7 +248,7 @@ include_dir 'directory' names that start with the . character are also excluded, to prevent mistakes as they are hidden on some platforms. Multiple files within an include directory are processed in file name order. The file names - are ordered by C locale rules, i.e. numbers before letters, and uppercase + are ordered by C locale rules, i.e., numbers before letters, and uppercase letters before lowercase ones. @@ -1118,7 +1118,7 @@ include_dir 'conf.d' With this parameter enabled, you can still create ordinary global users. Simply append @ when specifying the user - name in the client, e.g. joe@. The @ + name in the client, e.g., joe@. The @ will be stripped off before the user name is looked up by the server. @@ -2377,7 +2377,7 @@ include_dir 'conf.d' disabled, but the server continues to accumulate WAL segment files in the expectation that a command will soon be provided. Setting archive_command to a command that does nothing but - return true, e.g. /bin/true (REM on + return true, e.g., /bin/true (REM on Windows), effectively disables archiving, but also breaks the chain of WAL files needed for archive recovery, so it should only be used in unusual circumstances. @@ -3117,7 +3117,7 @@ include_dir 'conf.d' if your data is likely to be completely in cache, such as when the database is smaller than the total server memory, decreasing random_page_cost can be appropriate. Storage that has a low random - read cost relative to sequential, e.g. solid-state drives, might + read cost relative to sequential, e.g., solid-state drives, might also be better modeled with a lower value for random_page_cost. @@ -3815,7 +3815,7 @@ local0.* /var/log/postgresql Example: To keep 7 days of logs, one log file per day named server_log.Mon, server_log.Tue, - etc, and automatically overwrite last week's log with this week's log, + etc., and automatically overwrite last week's log with this week's log, set log_filename to server_log.%a, log_truncate_on_rotation to on, and log_rotation_age to 1440. @@ -5259,7 +5259,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; alias pg_temppg_temp. If it is not listed in the path then it is searched first (even before pg_catalog). However, the temporary schema is only searched for relation (table, view, - sequence, etc) and data type names. It is never searched for + sequence, etc.) and data type names. It is never searched for function or operator names. @@ -6309,7 +6309,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' rows that can be locked; that value is unlimited. The default, 64, has historically proven sufficient, but you might need to raise this value if you have queries that touch many different - tables in a single transaction, e.g. query of a parent table with + tables in a single transaction, e.g., query of a parent table with many children. This parameter can only be set at server start. @@ -6757,8 +6757,8 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' Reports whether PostgreSQL has been built with assertions enabled. That is the case if the macro USE_ASSERT_CHECKING is defined - when PostgreSQL is built (accomplished - e.g. by the configure option + when PostgreSQL is built (accomplished, + e.g., by the configure option ). By default PostgreSQL is built without assertions. diff --git a/doc/src/sgml/cube.sgml b/doc/src/sgml/cube.sgml index e2da685..fc3b94d 100644 --- a/doc/src/sgml/cube.sgml +++ b/doc/src/sgml/cube.sgml @@ -272,9 +272,9 @@ Makes a new cube from an existing cube, using a list of dimension indexes from an array. Can be used to find both the LL and UR - coordinates of a single dimension, e.g. + coordinates of a single dimension, e.g., cube_subset(cube('(1,3,5),(6,7,8)'), ARRAY[2]) = '(3),(7)'. - Or can be used to drop dimensions, or reorder them as desired, e.g. + Or can be used to drop dimensions, or reorder them as desired, e.g., cube_subset(cube('(1,3,5),(6,7,8)'), ARRAY[3,2,1,1]) = '(5, 3, 1, 1),(8, 7, 6, 6)'. diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 3e83dbb..5148cb0 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1074,13 +1074,13 @@ SELECT '52093.89'::money::numeric::float8; semantically insignificant and disregarded when comparing two values of type character. In collations where whitespace is significant, this behavior can produce unexpected results, - e.g. SELECT 'a '::CHAR(2) collate "C" < + e.g., SELECT 'a '::CHAR(2) collate "C" < 'a\n'::CHAR(2) returns true. Trailing spaces are removed when converting a character value to one of the other string types. Note that trailing spaces are semantically significant in character varying and text values, and - when using pattern matching, e.g. LIKE, + when using pattern matching, e.g., LIKE, regular expressions. diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml index 444b0ec..9c550c6 100644 --- a/doc/src/sgml/datetime.sgml +++ b/doc/src/sgml/datetime.sgml @@ -415,7 +415,7 @@ For reference purposes, a standard installation also contains files - Africa.txt, America.txt, etc, containing + Africa.txt, America.txt, etc., containing information about every time zone abbreviation known to be in use according to the zoneinfo timezone database. The zone name definitions found in these files can be copied and pasted into a custom diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 0fcd9f8..65fdf0b 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -1438,7 +1438,7 @@ ALTER TABLE products RENAME TO items; CREATE, CONNECT, TEMPORARY, EXECUTE, and USAGE. The privileges applicable to a particular - object vary depending on the object's type (table, function, etc). + 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 @@ -1453,7 +1453,7 @@ ALTER TABLE products RENAME TO items; An object can be assigned to a new owner with an ALTER - command of the appropriate kind for the object, e.g. . Superusers can always do this; ordinary roles can only do it if they are both the current owner of the object (or a member of the owning role) and a member of the new diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml index 816375f..36b2b30 100644 --- a/doc/src/sgml/docguide.sgml +++ b/doc/src/sgml/docguide.sgml @@ -687,16 +687,16 @@ save_size.pdfjadetex = 15000 Occasionally text is too wide for the printed margins, and in - extreme cases, too wide for the printed page, e.g. non-wrapped + extreme cases, too wide for the printed page, e.g., non-wrapped text, wide tables. Overly wide text generates Overfull - hbox messages in the TeX log output file, e.g. + hbox messages in the TeX log output file, e.g., postgres-US.log or postgres-A4.log. There are 72 points in an inch so anything reported as over 72 points too wide will probably not fit on the printed page (assuming one inch margins). To find the SGML text causing the overflow, find the first page number mentioned above - the overflow message, e.g. [50 ###] (page 50), and - look at the page after that (e.g. page 51) in the PDF + the overflow message, e.g., [50 ###] (page 50), and + look at the page after that (e.g., page 51) in the PDF file to see the overflow text and adjust the SGML accordingly. diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index f9536ee..5398ee2 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -3577,7 +3577,7 @@ EXEC SQL DEALLOCATE DESCRIPTOR identifier; EXEC SQL FETCH NEXT FROM mycursor INTO SQL DESCRIPTOR mydesc; If the result set is empty, the Descriptor Area will still contain - the metadata from the query, i.e. the field names. + the metadata from the query, i.e., the field names. @@ -3994,7 +3994,7 @@ typedef struct sqlvar_struct sqlvar_t; sqllen - Contains the binary length of the field. e.g. 4 bytes for ECPGt_int. + Contains the binary length of the field. e.g., 4 bytes for ECPGt_int. @@ -7911,7 +7911,7 @@ EXEC SQL CLOSE DATABASE; FREE cursor_name - Due to the differences how ECPG works compared to Informix's ESQL/C (i.e. which steps + Due to the differences how ECPG works compared to Informix's ESQL/C (i.e., which steps are purely grammar transformations and which steps rely on the underlying run-time library) there is no FREE cursor_name statement in ECPG. This is because in ECPG, DECLARE CURSOR doesn't translate to a function call into diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index a2d4ca2..0cfd704 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -495,7 +495,7 @@ An extension is relocatable if it is possible to move its contained objects into a different schema after initial creation - of the extension. The default is false, i.e. the + of the extension. The default is false, i.e., the extension is not relocatable. See below for more information. @@ -530,7 +530,7 @@ An extension's SQL script files can contain any SQL commands, except for transaction control commands (BEGIN, - COMMIT, etc) and commands that cannot be executed inside a + COMMIT, etc.) and commands that cannot be executed inside a transaction block (such as VACUUM). This is because the script files are implicitly executed within a transaction block. diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 734ef5f..8ded515 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -4193,7 +4193,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo; A branch is zero or more quantified atoms or constraints, concatenated. - It matches a match for the first, followed by a match for the second, etc; + It matches a match for the first, followed by a match for the second, etc.; an empty branch matches the empty string. @@ -5807,7 +5807,7 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})'); will be replaced by the year data, but the single Y in Year will not be. In to_date, to_number, and to_timestamp, double-quoted strings skip the number of - input characters contained in the string, e.g. "XX" + input characters contained in the string, e.g., "XX" skips two input characters. @@ -5822,9 +5822,9 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})'); - If the year format specification is less than four digits, e.g. + If the year format specification is less than four digits, e.g., YYY, and the supplied year is less than four digits, - the year will be adjusted to be nearest to the year 2020, e.g. + the year will be adjusted to be nearest to the year 2020, e.g., 95 becomes 1995. @@ -5925,7 +5925,7 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})'); to_char(interval) formats HH and - HH12 as shown on a 12-hour clock, i.e. zero hours + HH12 as shown on a 12-hour clock, i.e., zero hours and 36 hours output as 12, while HH24 outputs the full hour value, which can exceed 23 for intervals. @@ -8863,7 +8863,7 @@ CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple In addition to the operators shown in the table, the ordinary B-tree - comparison operators (=, <, etc) are defined + comparison operators (=, <, etc.) are defined for types tsvector and tsquery. These are not very useful for text searching but allow, for example, unique indexes to be built on columns of these types. @@ -17561,7 +17561,7 @@ FOR EACH ROW EXECUTE PROCEDURE suppress_redundant_updates_trigger(); objsubid int32 - Object sub-id (e.g. attribute number for columns) + Object sub-id (e.g., attribute number for columns) object_type diff --git a/doc/src/sgml/gin.sgml b/doc/src/sgml/gin.sgml index 80a578d..c9454c4 100644 --- a/doc/src/sgml/gin.sgml +++ b/doc/src/sgml/gin.sgml @@ -630,7 +630,7 @@ contains the corresponding query keys. Likewise, the function must return GIN_FALSE only if the item does not match, whether or not it contains the GIN_MAYBE keys. If the result depends on the GIN_MAYBE - entries, i.e. the match cannot be confirmed or refuted based on the + entries, i.e., the match cannot be confirmed or refuted based on the known query keys, the function must return GIN_MAYBE. diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index d249959..fc26438 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -203,7 +203,7 @@ protocol to make nodes agree on a serializable transactional order. this is unacceptable, either the middleware or the application must query such values from a single server and then use those values in write queries. Another option is to use this replication - option with a traditional master-standby setup, i.e. data modification + option with a traditional master-standby setup, i.e., data modification queries are sent only to the master and are propagated to the standby servers via master-standby replication, not by the replication middleware. Care must also be taken that all @@ -631,7 +631,7 @@ protocol to make nodes agree on a serializable transactional order. Set up continuous archiving on the primary to an archive directory accessible from the standby, as described in . The archive location should be - accessible from the standby even when the master is down, i.e. it should + accessible from the standby even when the master is down, i.e., it should reside on the standby server itself or another trusted server, not on the master server. @@ -2029,7 +2029,7 @@ LOG: database system is ready to accept read only connections - Data Definition Language (DDL) - e.g. CREATE INDEX + Data Definition Language (DDL) - e.g., CREATE INDEX @@ -2095,7 +2095,7 @@ LOG: database system is ready to accept read only connections WAL file control commands will not work during recovery, - e.g. pg_start_backup, pg_switch_xlog etc. + e.g., pg_start_backup, pg_switch_xlog etc. diff --git a/doc/src/sgml/install-windows.sgml b/doc/src/sgml/install-windows.sgml index 71a5c2e..f00668a 100644 --- a/doc/src/sgml/install-windows.sgml +++ b/doc/src/sgml/install-windows.sgml @@ -106,7 +106,7 @@ In the Microsoft Windows SDK, start the CMD shell listed under the SDK on the Start Menu. In recent SDK versions you can change the targeted CPU architecture, build - type, and target OS by using the setenv command, e.g. + type, and target OS by using the setenv command, e.g., setenv /x86 /release /xp to target Windows XP or later with a 32-bit release build. See /? for other options to setenv. All commands should be run from the @@ -234,7 +234,7 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin'; installations C:\Program Files\GnuWin32. Consider installing into C:\GnuWin32 or use the NTFS short name path to GnuWin32 in your PATH environment setting - (e.g. C:\PROGRA~1\GnuWin32). + (e.g., C:\PROGRA~1\GnuWin32). diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index ef45fbf..8210e71 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -2316,7 +2316,7 @@ PGresult *PQdescribePrepared(PGconn *conn, const char *stmtName); PGresult to obtain information about the parameters of the prepared statement, and the functions PQnfields, PQfname, - PQftype, etc provide information about the + PQftype, etc. provide information about the result columns (if any) of the statement. @@ -2355,7 +2355,7 @@ PGresult *PQdescribePortal(PGconn *conn, const char *portalName); portal. On success, a PGresult with status PGRES_COMMAND_OK is returned. The functions PQnfields, PQfname, - PQftype, etc can be applied to the + PQftype, etc. can be applied to the PGresult to obtain information about the result columns (if any) of the portal. @@ -4437,7 +4437,7 @@ int PQflush(PGconn *conn); more rows will arrive. (But note that it is still necessary to continue calling PQgetResult until it returns null.) All of these PGresult objects will contain the same row - description data (column names, types, etc) that an ordinary + description data (column names, types, etc.) that an ordinary PGresult object for the query would have. Each object should be freed with PQclear as usual. @@ -4907,7 +4907,7 @@ typedef struct pgNotify 0 indicates the overall copy format is textual (rows separated by - newlines, columns separated by separator characters, etc). 1 + newlines, columns separated by separator characters, etc.). 1 indicates the overall copy format is binary. See for more information. @@ -7195,7 +7195,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*) certificate of the signing authority to the postgresql.crt file, then its parent authority's certificate, and so on up to a certificate authority, root or intermediate, that is trusted by - the server, i.e. signed by a certificate in the server's + the server, i.e., signed by a certificate in the server's root.crt file. @@ -7262,7 +7262,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*) For a connection to be known secure, SSL usage must be configured on both the client and the server before the connection is made. If it is only configured on the server, the client may end up - sending sensitive information (e.g. passwords) before + sending sensitive information (e.g., passwords) before it knows that the server requires high security. In libpq, secure connections can be ensured by setting the sslmode parameter to verify-full or diff --git a/doc/src/sgml/manage-ag.sgml b/doc/src/sgml/manage-ag.sgml index 78ec509..8269438 100644 --- a/doc/src/sgml/manage-ag.sgml +++ b/doc/src/sgml/manage-ag.sgml @@ -387,7 +387,7 @@ dropdb dbname of data files. They are dependent on metadata contained in the main data directory, and therefore cannot be attached to a different database cluster or backed up individually. Similarly, if you lose - a tablespace (file deletion, disk failure, etc), the database cluster + a tablespace (file deletion, disk failure, etc.), the database cluster might become unreadable or unable to start. Placing a tablespace on a temporary file system like a ramdisk risks the reliability of the entire cluster. diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 5e9e735..9fbfde4 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -204,7 +204,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser When the server shuts down cleanly, a permanent copy of the statistics data is stored in the pg_stat subdirectory, so that statistics can be retained across server restarts. When recovery is - performed at server start (e.g. after immediate shutdown, server crash, + performed at server start (e.g., after immediate shutdown, server crash, and point-in-time recovery), all statistics counters are reset. diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml index 94c11ad..e128f2e 100644 --- a/doc/src/sgml/perform.sgml +++ b/doc/src/sgml/perform.sgml @@ -1559,7 +1559,7 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse; Place the database cluster's data directory in a memory-backed - file system (i.e. RAM disk). This eliminates all + file system (i.e., RAM disk). This eliminates all database disk I/O, but limits data storage to the amount of available memory (and perhaps swap). diff --git a/doc/src/sgml/pgbench.sgml b/doc/src/sgml/pgbench.sgml index b479105..a4b0d1f 100644 --- a/doc/src/sgml/pgbench.sgml +++ b/doc/src/sgml/pgbench.sgml @@ -554,7 +554,7 @@ pgbench options dbname Remember to take the sampling rate into account when processing the log file. For example, when computing tps values, you need to multiply - the numbers accordingly (e.g. with 0.01 sample rate, you'll only get + the numbers accordingly (e.g., with 0.01 sample rate, you'll only get 1/100 of the actual tps). diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index b79f0db..4e32713 100644 --- a/doc/src/sgml/pgupgrade.sgml +++ b/doc/src/sgml/pgupgrade.sgml @@ -38,8 +38,8 @@ pg_upgrade (formerly called pg_migrator) allows data stored in PostgreSQL data files to be upgraded to a later PostgreSQL major version without the data dump/reload typically required for - major version upgrades, e.g. from 8.4.7 to the current major release - of PostgreSQL. It is not required for minor version upgrades, e.g. from + major version upgrades, e.g., from 8.4.7 to the current major release + of PostgreSQL. It is not required for minor version upgrades, e.g., from 9.0.1 to 9.0.4. @@ -57,7 +57,7 @@ pg_upgrade does its best to - make sure the old and new clusters are binary-compatible, e.g. by + make sure the old and new clusters are binary-compatible, e.g., by checking for compatible compile-time settings, including 32/64-bit binaries. It is important that any external modules are also binary compatible, though this cannot @@ -204,13 +204,13 @@ Optionally move the old cluster - If you are using a version-specific installation directory, e.g. + If you are using a version-specific installation directory, e.g., /opt/PostgreSQL/9.1, you do not need to move the old cluster. The graphical installers all use version-specific installation directories. - If your installation directory is not version-specific, e.g. + If your installation directory is not version-specific, e.g., /usr/local/pgsql, it is necessary to move the current PostgreSQL install directory so it does not interfere with the new PostgreSQL installation. Once the current PostgreSQL server is shut down, it is safe to rename the @@ -277,9 +277,9 @@ make prefix=/usr/local/pgsql.new install Install any custom shared object files (or DLLs) used by the old cluster - into the new cluster, e.g. pgcrypto.so, + into the new cluster, e.g., pgcrypto.so, whether they are from contrib - or some other source. Do not install the schema definitions, e.g. + or some other source. Do not install the schema definitions, e.g., pgcrypto.sql, because these will be upgraded from the old cluster. @@ -407,7 +407,7 @@ pg_upgrade.exe If you modified pg_hba.conf, restore its original settings. It might also be necessary to adjust other configuration files in the new - cluster to match the old cluster, e.g. postgresql.conf. + cluster to match the old cluster, e.g., postgresql.conf. @@ -459,7 +459,7 @@ psql --username postgres --file script.sql postgres pg_upgrade completes. (Automatic deletion is not possible if you have user-defined tablespaces inside the old data directory.) You can also delete the old installation directories - (e.g. bin, share). + (e.g., bin, share). @@ -539,7 +539,7 @@ psql --username postgres --file script.sql postgres If you are upgrading a pre-PostgreSQL 9.2 cluster that uses a configuration-file-only directory, you must pass the real data directory location to pg_upgrade, and - pass the configuration directory location to the server, e.g. + pass the configuration directory location to the server, e.g., -d /real-data-directory -o '-D /configuration-directory'. @@ -567,7 +567,7 @@ psql --username postgres --file script.sql postgres copy of the old cluster while the server is running, then shut down the old server and run rsync again to update the copy with any changes to make it consistent. You might want to exclude some - files, e.g. postmaster.pid, as documented in postmaster.pid, as documented in . If your file system supports file system snapshots or copy-on-write file copies, you can use that to make a backup of the old cluster and tablespaces, though the snapshot diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml index 9117769..3259b29 100644 --- a/doc/src/sgml/plperl.sgml +++ b/doc/src/sgml/plperl.sgml @@ -572,7 +572,7 @@ SELECT * from lotsa_md5(500); spi_prepare, spi_query_prepared, spi_exec_prepared, and spi_freeplan implement the same functionality but for prepared queries. - spi_prepare accepts a query string with numbered argument placeholders ($1, $2, etc) + spi_prepare accepts a query string with numbered argument placeholders ($1, $2, etc.) and a string list of argument types: $plan = spi_prepare('SELECT * FROM test WHERE id > $1 AND name = $2', @@ -617,7 +617,7 @@ SELECT done(); 2005-12-10 | 2005-12-11 | 2005-12-12 Note that the parameter subscript in spi_prepare is defined via - $1, $2, $3, etc, so avoid declaring query strings in double quotes that might easily + $1, $2, $3, etc., so avoid declaring query strings in double quotes that might easily lead to hard-to-catch bugs. @@ -942,7 +942,7 @@ $$ LANGUAGE plperl; PL/Perl functions will share the same value of %_SHARED if and only if they are executed by the same SQL role. In an application wherein a single session executes code under multiple SQL roles (via - SECURITY DEFINER functions, use of SET ROLE, etc) + SECURITY DEFINER functions, use of SET ROLE, etc.) you may need to take explicit steps to ensure that PL/Perl functions can share data via %_SHARED. To do that, make sure that functions that should communicate are owned by the same user, and mark diff --git a/doc/src/sgml/pltcl.sgml b/doc/src/sgml/pltcl.sgml index d2175d5..9839d55 100644 --- a/doc/src/sgml/pltcl.sgml +++ b/doc/src/sgml/pltcl.sgml @@ -228,7 +228,7 @@ $$ LANGUAGE pltcl; functions will share the same global variables if and only if they are executed by the same SQL role. In an application wherein a single session executes code under multiple SQL roles (via SECURITY - DEFINER functions, use of SET ROLE, etc) you may need to + DEFINER functions, use of SET ROLE, etc.) you may need to take explicit steps to ensure that PL/Tcl functions can share data. To do that, make sure that functions that should communicate are owned by the same user, and mark them SECURITY DEFINER. You must of diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index e519ff9..8867800 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -140,7 +140,7 @@ bind step, which creates a portal given a prepared statement and values for any needed parameters; and an execute step that runs a portal's query. In the case of - a query that returns rows (SELECT, SHOW, etc), + a query that returns rows (SELECT, SHOW, etc.), the execute step can be told to fetch only a limited number of rows, so that multiple execute steps might be needed to complete the operation. @@ -519,7 +519,7 @@ Indicates that rows are about to be returned in response to - a SELECT, FETCH, etc query. + a SELECT, FETCH, etc. query. The contents of this message describe the column layout of the rows. This will be followed by a DataRow message for each row being returned to the frontend. @@ -532,7 +532,7 @@ One of the set of rows returned by - a SELECT, FETCH, etc query. + a SELECT, FETCH, etc. query. @@ -1410,7 +1410,7 @@ The commands accepted in walsender mode are: - Filename of the timeline history file, e.g 00000002.history. + Filename of the timeline history file, e.g., 00000002.history. @@ -1476,7 +1476,7 @@ The commands accepted in walsender mode are: If TIMELINE option is specified, streaming starts on timeline tli; otherwise, the server's current timeline is selected. The server can - reply with an error, e.g. if the requested section of WAL has already + reply with an error, e.g., if the requested section of WAL has already been recycled. On success, server responds with a CopyBothResponse message, and then starts to stream WAL to the frontend. @@ -1801,7 +1801,7 @@ The commands accepted in walsender mode are: Instructs server to start streaming WAL for logical replication, starting at WAL position XXX/XXX. The server can - reply with an error, e.g. if the requested section of WAL has already + reply with an error, e.g., if the requested section of WAL has already been recycled. On success, server responds with a CopyBothResponse message, and then starts to stream WAL to the frontend. @@ -2101,7 +2101,7 @@ This section describes the base data types used in messages. order (most significant byte first). If i is specified it is the exact value that will appear, otherwise the value - is variable. Eg. Int16, Int32(42). + is variable. E.g., Int16, Int32(42). @@ -2116,7 +2116,7 @@ This section describes the base data types used in messages. n-bit integers, each in network byte order. The array length k is always determined by an earlier field in the message. - Eg. Int16[M]. + E.g., Int16[M]. @@ -2131,7 +2131,7 @@ This section describes the base data types used in messages. specific length limitation on strings. If s is specified it is the exact value that will appear, otherwise the value is variable. - Eg. String, String("user"). + E.g., String, String("user"). @@ -2156,7 +2156,7 @@ characters that don't fit into your fixed-size buffer. width n is not a constant, it is always determinable from an earlier field in the message. If c is specified it is the exact - value. Eg. Byte2, Byte1('\n'). + value. E.g., Byte2, Byte1('\n'). @@ -3215,7 +3215,7 @@ CopyInResponse (B) 0 indicates the overall COPY format is textual (rows separated by newlines, columns separated by separator - characters, etc). + characters, etc.). 1 indicates the overall copy format is binary (similar to DataRow format). See @@ -3290,7 +3290,7 @@ CopyOutResponse (B) 0 indicates the overall COPY format is textual (rows separated by newlines, columns - separated by separator characters, etc). 1 indicates + separated by separator characters, etc.). 1 indicates the overall copy format is binary (similar to DataRow format). See for more information. @@ -3363,7 +3363,7 @@ CopyBothResponse (B) 0 indicates the overall COPY format is textual (rows separated by newlines, columns - separated by separator characters, etc). 1 indicates + separated by separator characters, etc.). 1 indicates the overall copy format is binary (similar to DataRow format). See for more information. diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml index 0f1ff34..05f07eb 100644 --- a/doc/src/sgml/recovery-config.sgml +++ b/doc/src/sgml/recovery-config.sgml @@ -170,7 +170,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows This parameter specifies that recovery should end as soon as a - consistent state is reached, i.e. as early as possible. When restoring + consistent state is reached, i.e., as early as possible. When restoring from an online backup, this means the point where taking the backup ended. diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml index 9711b1f..8b1f94a 100644 --- a/doc/src/sgml/ref/create_database.sgml +++ b/doc/src/sgml/ref/create_database.sgml @@ -116,7 +116,7 @@ CREATE DATABASE name Collation order (LC_COLLATE) to use in the new database. - This affects the sort order applied to strings, e.g. in queries with + This affects the sort order applied to strings, e.g., in queries with ORDER BY, as well as the order used in indexes on text columns. The default is to use the collation order of the template database. See below for additional restrictions. @@ -128,7 +128,7 @@ CREATE DATABASE name Character classification (LC_CTYPE) to use in the new - database. This affects the categorization of characters, e.g. lower, + database. This affects the categorization of characters, e.g., lower, upper and digit. The default is to use the character classification of the template database. See below for additional restrictions. diff --git a/doc/src/sgml/ref/create_domain.sgml b/doc/src/sgml/ref/create_domain.sgml index dd782e4..bd928aa 100644 --- a/doc/src/sgml/ref/create_domain.sgml +++ b/doc/src/sgml/ref/create_domain.sgml @@ -142,7 +142,7 @@ CREATE DOMAIN name [ AS ] INSERT INTO tab (domcol) VALUES ((SELECT domcol FROM tab WHERE false)). diff --git a/doc/src/sgml/ref/create_event_trigger.sgml b/doc/src/sgml/ref/create_event_trigger.sgml index 7cdf4c7..ac68911 100644 --- a/doc/src/sgml/ref/create_event_trigger.sgml +++ b/doc/src/sgml/ref/create_event_trigger.sgml @@ -86,7 +86,7 @@ CREATE EVENT TRIGGER name A list of values for the associated filter_variable for which the trigger should fire. For TAG, this means a - list of command tags (e.g. 'DROP FUNCTION'). + list of command tags (e.g., 'DROP FUNCTION'). diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml index 2001921..f62040c 100644 --- a/doc/src/sgml/ref/create_function.sgml +++ b/doc/src/sgml/ref/create_function.sgml @@ -254,7 +254,7 @@ CREATE [ OR REPLACE ] FUNCTION The name of the language that the function is implemented in. It can be sql, c, internal, or the name of a user-defined - procedural language, e.g. plpgsql. Enclosing the + procedural language, e.g., plpgsql. Enclosing the name in single quotes is deprecated and requires matching case. diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 299cce8..45c45a0 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -1055,7 +1055,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI user_catalog_table (boolean) - Declare a table as an additional catalog table, e.g. for the purpose of + Declare a table as an additional catalog table, e.g., for the purpose of logical replication. See for details. diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml index f2b25e5..52e58b3 100644 --- a/doc/src/sgml/ref/grant.sgml +++ b/doc/src/sgml/ref/grant.sgml @@ -334,7 +334,7 @@ GRANT role_name [, ...] TO look up objects within the schema. Without this permission, it is still - possible to see the object names, e.g. by querying the system tables. + possible to see the object names, e.g., by querying the system tables. Also, after revoking this permission, existing backends might have statements that have previously performed this lookup, so this is not a completely secure way to prevent object access. diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index 228edf7..3938098 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -80,7 +80,7 @@ PostgreSQL documentation initdb initializes the database cluster's default locale and character set encoding. The character set encoding, collation order (LC_COLLATE) and character set classes - (LC_CTYPE, e.g. upper, lower, digit) can be set separately + (LC_CTYPE, e.g., upper, lower, digit) can be set separately for a database when it is created. initdb determines those settings for the template1 database, which will serve as the default for all other databases. diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index eabdc62..36ccc2f 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -709,7 +709,7 @@ PostgreSQL documentation - Use conditional commands (i.e. add an IF EXISTS + Use conditional commands (i.e., add an IF EXISTS clause) when cleaning database objects. This option is not valid unless diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index fcf5f77..7c78163 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -304,7 +304,7 @@ PostgreSQL documentation - Use conditional commands (i.e. add an IF EXISTS + Use conditional commands (i.e., add an IF EXISTS clause) to clean databases and other objects. This option is not valid unless diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index 4bc30ce..374c74f 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -494,7 +494,7 @@ - Use conditional commands (i.e. add an IF EXISTS + Use conditional commands (i.e., add an IF EXISTS clause) when cleaning database objects. This option is not valid unless diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index cdfdaa0..9c8985d 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -813,7 +813,7 @@ PostgreSQL documentation To start postgres with a specific - port, e.g. 1234: + port, e.g., 1234: $ postgres -p 1234 diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 74d4618..f0a60d8 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -577,7 +577,7 @@ EOF psql returns 0 to the shell if it - finished normally, 1 if a fatal error of its own occurs (e.g. out of memory, + finished normally, 1 if a fatal error of its own occurs (e.g., out of memory, file not found), 2 if the connection to the server went bad and the session was not interactive, and 3 if an error occurred in a script and the variable ON_ERROR_STOP was set. @@ -2266,7 +2266,7 @@ lo_import 152801 In latex-longtable format, this controls the proportional width of each column containing a left-aligned data type. It is specified as a whitespace-separated list of values, - e.g. '0.2 0.2 0.6'. Unspecified output columns + e.g., '0.2 0.2 0.6'. Unspecified output columns use the last specified value. @@ -3397,7 +3397,7 @@ testdb=> \set PROMPT1 '%[%033[1;33;40m%]%n@%/%R%[%033[0m%]%# ' psql starts up. Tab-completion is also supported, although the completion logic makes no claim to be an SQL parser. The queries generated by tab-completion - can also interfere with other SQL commands, e.g. SET + can also interfere with other SQL commands, e.g., SET TRANSACTION ISOLATION LEVEL. If for some reason you do not like the tab completion, you can turn it off by putting this in a file named diff --git a/doc/src/sgml/ref/values.sgml b/doc/src/sgml/ref/values.sgml index 0fb3cd7..57ac1d4 100644 --- a/doc/src/sgml/ref/values.sgml +++ b/doc/src/sgml/ref/values.sgml @@ -200,7 +200,7 @@ UPDATE employees SET salary = salary * v.increase SELECT. It is not required that the AS clause specify names for all the columns, but it's good practice to do so. (The default column names for VALUES are column1, - column2, etc in PostgreSQL, but + column2, etc. in PostgreSQL, but these names might be different in other database systems.) diff --git a/doc/src/sgml/release-7.4.sgml b/doc/src/sgml/release-7.4.sgml index 5a4c52d..0c5e11d 100644 --- a/doc/src/sgml/release-7.4.sgml +++ b/doc/src/sgml/release-7.4.sgml @@ -605,7 +605,7 @@ Fix money data type to work in locales where currency - amounts have no fractional digits, e.g. Japan (Itagaki Takahiro) + amounts have no fractional digits, e.g., Japan (Itagaki Takahiro) @@ -1094,7 +1094,7 @@ subexpression hasn't got a match. An example is substring('foo' from 'foo(bar)?'). This should return NULL, since (bar) isn't matched, but - it was mistakenly returning the whole-pattern match instead (ie, + it was mistakenly returning the whole-pattern match instead (i.e., foo). @@ -1207,7 +1207,7 @@ Prevent functions in indexes from executing with the privileges of - the user running VACUUM, ANALYZE, etc (Tom) + the user running VACUUM, ANALYZE, etc. (Tom) @@ -2159,7 +2159,7 @@ misuse Change contrib/tsearch2 to avoid unsafe use of INTERNAL function results Repair ancient race condition that allowed a transaction to be -seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner +seen as committed for some purposes (e.g., SELECT FOR UPDATE) slightly sooner than for other purposes This is an extremely serious bug since it could lead to apparent data inconsistencies being briefly visible to applications. diff --git a/doc/src/sgml/release-8.0.sgml b/doc/src/sgml/release-8.0.sgml index 299c34e..ab7a270 100644 --- a/doc/src/sgml/release-8.0.sgml +++ b/doc/src/sgml/release-8.0.sgml @@ -795,7 +795,7 @@ Fix money data type to work in locales where currency - amounts have no fractional digits, e.g. Japan (Itagaki Takahiro) + amounts have no fractional digits, e.g., Japan (Itagaki Takahiro) @@ -1412,7 +1412,7 @@ subexpression hasn't got a match. An example is substring('foo' from 'foo(bar)?'). This should return NULL, since (bar) isn't matched, but - it was mistakenly returning the whole-pattern match instead (ie, + it was mistakenly returning the whole-pattern match instead (i.e., foo). @@ -1606,7 +1606,7 @@ Prevent functions in indexes from executing with the privileges of - the user running VACUUM, ANALYZE, etc (Tom) + the user running VACUUM, ANALYZE, etc. (Tom) @@ -2799,7 +2799,7 @@ misuse Guard against incorrect second parameter to record_out Repair ancient race condition that allowed a transaction to be -seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner +seen as committed for some purposes (e.g., SELECT FOR UPDATE) slightly sooner than for other purposes This is an extremely serious bug since it could lead to apparent data inconsistencies being briefly visible to applications. diff --git a/doc/src/sgml/release-8.1.sgml b/doc/src/sgml/release-8.1.sgml index 0cb5587..b7bb89f 100644 --- a/doc/src/sgml/release-8.1.sgml +++ b/doc/src/sgml/release-8.1.sgml @@ -1061,7 +1061,7 @@ Fix money data type to work in locales where currency - amounts have no fractional digits, e.g. Japan (Itagaki Takahiro) + amounts have no fractional digits, e.g., Japan (Itagaki Takahiro) @@ -1851,7 +1851,7 @@ subexpression hasn't got a match. An example is substring('foo' from 'foo(bar)?'). This should return NULL, since (bar) isn't matched, but - it was mistakenly returning the whole-pattern match instead (ie, + it was mistakenly returning the whole-pattern match instead (i.e., foo). @@ -2058,7 +2058,7 @@ Prevent functions in indexes from executing with the privileges of - the user running VACUUM, ANALYZE, etc (Tom) + the user running VACUUM, ANALYZE, etc. (Tom) @@ -3626,7 +3626,7 @@ DISTINCT query Currently PostgreSQL processes a backslash in a string literal as introducing a special escape sequence, - e.g. \n or \010. + e.g., \n or \010. While this allows easy entry of special values, it is nonstandard and makes porting of applications from other databases more difficult. For this reason, the @@ -3635,7 +3635,7 @@ DISTINCT query backward compatibility and for users who want special backslash processing, a new string syntax has been created. This new string syntax is formed by writing an E immediately preceding the - single quote that starts the string, e.g. E'hi\n'. While + single quote that starts the string, e.g., E'hi\n'. While this release does not change the handling of backslashes in strings, it does add new configuration parameters to help users migrate applications for future releases: diff --git a/doc/src/sgml/release-8.2.sgml b/doc/src/sgml/release-8.2.sgml index 7f6a74b..1c972ad 100644 --- a/doc/src/sgml/release-8.2.sgml +++ b/doc/src/sgml/release-8.2.sgml @@ -2188,7 +2188,7 @@ Fix money data type to work in locales where currency - amounts have no fractional digits, e.g. Japan (Itagaki Takahiro) + amounts have no fractional digits, e.g., Japan (Itagaki Takahiro) @@ -3233,7 +3233,7 @@ subexpression hasn't got a match. An example is substring('foo' from 'foo(bar)?'). This should return NULL, since (bar) isn't matched, but - it was mistakenly returning the whole-pattern match instead (ie, + it was mistakenly returning the whole-pattern match instead (i.e., foo). @@ -3600,7 +3600,7 @@ Prevent functions in indexes from executing with the privileges of - the user running VACUUM, ANALYZE, etc (Tom) + the user running VACUUM, ANALYZE, etc. (Tom) @@ -6032,7 +6032,7 @@ - Intervals and times are treated as 24-hour periods, e.g. + Intervals and times are treated as 24-hour periods, e.g., 25 hours is considered AM. @@ -6804,7 +6804,7 @@ This is like server_version, but is an - integer, e.g. 80200. This allows applications to + integer, e.g., 80200. This allows applications to make version checks more easily. diff --git a/doc/src/sgml/release-8.3.sgml b/doc/src/sgml/release-8.3.sgml index 3ce96f1..350f6d8 100644 --- a/doc/src/sgml/release-8.3.sgml +++ b/doc/src/sgml/release-8.3.sgml @@ -3939,7 +3939,7 @@ Fix money data type to work in locales where currency - amounts have no fractional digits, e.g. Japan (Itagaki Takahiro) + amounts have no fractional digits, e.g., Japan (Itagaki Takahiro) @@ -5535,7 +5535,7 @@ subexpression hasn't got a match. An example is substring('foo' from 'foo(bar)?'). This should return NULL, since (bar) isn't matched, but - it was mistakenly returning the whole-pattern match instead (ie, + it was mistakenly returning the whole-pattern match instead (i.e., foo). @@ -8350,7 +8350,7 @@ current_date < 2017-11-17 Provide strlcpy() and strlcat() on all platforms, and replace error-prone uses of strncpy(), - strncat(), etc (Peter) + strncat(), etc. (Peter) diff --git a/doc/src/sgml/release-8.4.sgml b/doc/src/sgml/release-8.4.sgml index 0baa735..6ce0fa3 100644 --- a/doc/src/sgml/release-8.4.sgml +++ b/doc/src/sgml/release-8.4.sgml @@ -1259,7 +1259,7 @@ - Avoid possible failure when performing transaction control commands (e.g + Avoid possible failure when performing transaction control commands (e.g., ROLLBACK) in prepared queries (Tom Lane) @@ -7835,7 +7835,7 @@ WITH w AS (SELECT * FROM foo) SELECT * FROM w, bar ... FOR UPDATE Add support for Unicode string literal and identifier specifications - using code points, e.g. U&'d\0061t\+000061' + using code points, e.g., U&'d\0061t\+000061' (Peter) diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml index 0c77d24..568ce33 100644 --- a/doc/src/sgml/release-9.0.sgml +++ b/doc/src/sgml/release-9.0.sgml @@ -1465,7 +1465,7 @@ - Avoid possible failure when performing transaction control commands (e.g + Avoid possible failure when performing transaction control commands (e.g., ROLLBACK) in prepared queries (Tom Lane) @@ -7766,7 +7766,7 @@ Such triggers are fired only when the specified column(s) are affected - by the query, e.g. appear in an UPDATE's SET + by the query, e.g., appear in an UPDATE's SET list. diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml index 4f86b64..40c021e 100644 --- a/doc/src/sgml/release-9.1.sgml +++ b/doc/src/sgml/release-9.1.sgml @@ -1653,7 +1653,7 @@ - Avoid possible failure when performing transaction control commands (e.g + Avoid possible failure when performing transaction control commands (e.g., ROLLBACK) in prepared queries (Tom Lane) @@ -2920,7 +2920,7 @@ Improve selectivity estimation for text search queries involving - prefixes, i.e. word:* patterns (Tom Lane) + prefixes, i.e., word:* patterns (Tom Lane) @@ -5857,7 +5857,7 @@ Support host names and host suffixes - (e.g. .example.com) in .example.com) in pg_hba.conf (Peter Eisentraut) diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml index 911f52a..0264c8d 100644 --- a/doc/src/sgml/release-9.2.sgml +++ b/doc/src/sgml/release-9.2.sgml @@ -1974,7 +1974,7 @@ - Avoid possible failure when performing transaction control commands (e.g + Avoid possible failure when performing transaction control commands (e.g., ROLLBACK) in prepared queries (Tom Lane) @@ -3722,7 +3722,7 @@ Improve selectivity estimation for text search queries involving - prefixes, i.e. word:* patterns (Tom Lane) + prefixes, i.e., word:* patterns (Tom Lane) @@ -5969,7 +5969,7 @@ Various shell tools use zero-byte (NUL) separators, - e.g. find. + e.g., find. diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml index 8788b80..3943889 100644 --- a/doc/src/sgml/release-9.3.sgml +++ b/doc/src/sgml/release-9.3.sgml @@ -4709,7 +4709,7 @@ ALTER EXTENSION hstore UPDATE; Allow text timezone - designations, e.g. America/Chicago, in the + designations, e.g., America/Chicago, in the T field of ISO-format timestamptz input (Bruce Momjian) @@ -4800,7 +4800,7 @@ ALTER EXTENSION hstore UPDATE; Previously the behavior was either wrong or inconsistent - with positive/AD handling, e.g. with the format mask + with positive/AD handling, e.g., with the format mask IYYY-IW-DY. diff --git a/doc/src/sgml/release-9.4.sgml b/doc/src/sgml/release-9.4.sgml index 26abce1..6280d4b 100644 --- a/doc/src/sgml/release-9.4.sgml +++ b/doc/src/sgml/release-9.4.sgml @@ -98,7 +98,7 @@ Previously, an input array string that started with a single-element array dimension could later contain multidimensional segments, - e.g. '{{1}, {2,3}}'::int[]. + e.g., '{{1}, {2,3}}'::int[]. @@ -324,7 +324,7 @@ Remove native support for Kerberos authentication - ( @@ -1501,7 +1501,7 @@ These functions' names are prefixed with make_, - e.g. make_date(). + e.g., make_date(). diff --git a/doc/src/sgml/release-old.sgml b/doc/src/sgml/release-old.sgml index ec8e43f..ec86043 100644 --- a/doc/src/sgml/release-old.sgml +++ b/doc/src/sgml/release-old.sgml @@ -39,7 +39,7 @@ Prevent functions in indexes from executing with the privileges of - the user running VACUUM, ANALYZE, etc (Tom) + the user running VACUUM, ANALYZE, etc. (Tom) @@ -782,7 +782,7 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0'; Change encoding function signature to prevent misuse Repair ancient race condition that allowed a transaction to be -seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner +seen as committed for some purposes (e.g., SELECT FOR UPDATE) slightly sooner than for other purposes This is an extremely serious bug since it could lead to apparent data inconsistencies being briefly visible to applications. @@ -2010,7 +2010,7 @@ operations on bytea columns (Joe) Repair ancient race condition that allowed a transaction to be -seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner +seen as committed for some purposes (e.g., SELECT FOR UPDATE) slightly sooner than for other purposes This is an extremely serious bug since it could lead to apparent data inconsistencies being briefly visible to applications. @@ -2505,7 +2505,7 @@ since PostgreSQL 7.1. The SELECT ... LIMIT #,# syntax will be removed in the next release. You should change your queries to use - separate LIMIT and OFFSET clauses, e.g. LIMIT 10 OFFSET + separate LIMIT and OFFSET clauses, e.g., LIMIT 10 OFFSET 20. @@ -2821,7 +2821,7 @@ since PostgreSQL 7.1. <application>ECPG</> EXECUTE ... INTO implemented (Christof Petig) -Multiple row descriptor support (e.g. CARDINALITY) (Christof Petig) +Multiple row descriptor support (e.g., CARDINALITY) (Christof Petig) Fix for GRANT parameters (Lee Kindness) Fix INITIALLY DEFERRED bug Various bug fixes (Michael, Christof Petig) @@ -3225,7 +3225,7 @@ New PL/pgSQL EXECUTE command which allows dynamic SQL and utility statements New PL/pgSQL GET DIAGNOSTICS statement for SPI value access (Jan) New quote_identifiers() and quote_literal() functions (Jan) New ALTER TABLE table OWNER TO user command (Mark Hollomon) -Allow subselects in FROM, i.e. FROM (SELECT ...) [AS] alias (Tom) +Allow subselects in FROM, i.e., FROM (SELECT ...) [AS] alias (Tom) Update PyGreSQL to version 3.1 (D'Arcy) Store tables as files named by OID (Vadim) New SQL function setval(seq,val,bool) for use in pg_dump (Philip) @@ -3793,7 +3793,7 @@ Allow SELECT .. FOR UPDATE in PL/pgSQL (Hiroshi) Enable backward sequential scan even after reaching EOF (Hiroshi) Add btree indexing of boolean values, >= and <= (Don Baccus) Print current line number when COPY FROM fails (Massimo) -Recognize POSIX time zone e.g. "PST+8" and "GMT-8" (Thomas) +Recognize POSIX time zone, e.g., "PST+8" and "GMT-8" (Thomas) Add DEC as synonym for DECIMAL (Thomas) Add SESSION_USER as SQL92 key word, same as CURRENT_USER (Thomas) Implement SQL92 column aliases (aka correlation names) (Thomas) @@ -3860,7 +3860,7 @@ New TIME WITH TIME ZONE type (Thomas) Add MAX()/MIN() on time type (Thomas) Add abs(), mod(), fac() for int8 (Thomas) Rename functions to round(), sqrt(), cbrt(), pow() for float8 (Thomas) -Add transcendental math functions (e.g. sin(), acos()) for float8 (Thomas) +Add transcendental math functions (e.g., sin(), acos()) for float8 (Thomas) Add exp() and ln() for NUMERIC type Rename NUMERIC power() to pow() (Thomas) Improved TRANSLATE() function (Edwin Ramirez, Tom) @@ -4282,7 +4282,7 @@ Add Win1250 (Czech) support (Pavel Behal) isolation level, data read by one transaction can be overwritten by another. In other words, if a row is returned by SELECT it doesn't mean that this row really exists - at the time it is returned (i.e. sometime after the statement or + at the time it is returned (i.e., sometime after the statement or transaction began) nor that the row is protected from being deleted or updated by concurrent transactions before the current transaction does a commit or rollback. @@ -4738,7 +4738,7 @@ Define "tz_hour" and "tz_minute" arguments to date_part()(Thomas) Add routines to convert between varchar and bpchar(Thomas) Add routines to allow sizing of varchar and bpchar into target columns(Thomas) Add bit flags to support timezonehour and minute in data retrieval(Thomas) -Allow more variations on valid floating point numbers (e.g. ".1", "1e6")(Thomas) +Allow more variations on valid floating point numbers (e.g., ".1", "1e6")(Thomas) Fixes for unary minus parsing with leading spaces(Thomas) Implement TIMEZONE_HOUR, TIMEZONE_MINUTE per SQL92 specs(Thomas) Check for and properly ignore FOREIGN KEY column constraints(Thomas) @@ -5243,11 +5243,11 @@ Allow NOT NULL UNIQUE constraint clause (each allowed separately before)(Thomas) Allow PostgreSQL-style casting ("::") of non-constants(Thomas) Add support for SQL3 TRUE and FALSE boolean constants(Thomas) Support SQL92 syntax for IS TRUE/IS FALSE/IS NOT TRUE/IS NOT FALSE(Thomas) -Allow shorter strings for boolean literals (e.g. "t", "tr", "tru")(Thomas) +Allow shorter strings for boolean literals (e.g., "t", "tr", "tru")(Thomas) Allow SQL92 delimited identifiers(Thomas) Implement SQL92 binary and hexadecimal string decoding (b'10' and x'1F')(Thomas) Support SQL92 syntax for type coercion of literal strings - (e.g. "DATETIME 'now'")(Thomas) + (e.g., "DATETIME 'now'")(Thomas) Add conversions for int2, int4, and OID types to and from text(Thomas) Use shared lock when building indexes(Vadim) Free memory allocated for a user query inside transaction block after @@ -5277,7 +5277,7 @@ Increase 16 char limit on system table/index names to 32 characters(Bruce) Rename system indexes(Bruce) Add 'GERMAN' option to SET DATESTYLE(Thomas) Define an "ISO-style" timespan output format with "hh:mm:ss" fields(Thomas) -Allow fractional values for delta times (e.g. '2.5 days')(Thomas) +Allow fractional values for delta times (e.g., '2.5 days')(Thomas) Validate numeric input more carefully for delta times(Thomas) Implement day of year as possible input to date_part()(Thomas) Define timespan_finite() and text_timespan() functions(Thomas) @@ -5670,7 +5670,7 @@ optimizer which uses genetic tables (giving the optimizer a choice on order of evaluation). Several regression tests have been modified to explicitly order the results, and hence are insensitive to optimizer choices. A few regression tests are - for data types which are inherently unordered (e.g. points and time + for data types which are inherently unordered (e.g., points and time intervals) and tests involving those types are explicitly bracketed with set geqo to 'off' and reset geqo. @@ -6387,10 +6387,10 @@ Incompatible changes: (due to system catalog changes and indexing structure changes). * double-quote (") is deprecated as a quoting character for string literals; you need to convert them to single quotes ('). - * name of aggregates (eg. int4sum) are renamed in accordance with the - SQL standard (eg. sum). + * name of aggregates (e.g., int4sum) are renamed in accordance with the + SQL standard (e.g., sum). * CHANGE ACL syntax is replaced by GRANT/REVOKE syntax. - * float literals (eg. 3.14) are now of type float4 (instead of float8 in + * float literals (e.g., 3.14) are now of type float4 (instead of float8 in previous releases); you might have to do typecasting if you depend on it being of type float8. If you neglect to do the typecasting and you assign a float literal to a field of type float8, you might get incorrect values @@ -6416,7 +6416,7 @@ more compliant to the SQL-92 standard): * single-quote (') is used for quoting string literals; '' (in addition to \') is supported as means of inserting a single quote in a string * SQL standard aggregate names (MAX, MIN, AVG, SUM, COUNT) are used - (Also, aggregates can now be overloaded, i.e. you can define your + (Also, aggregates can now be overloaded, i.e., you can define your own MAX aggregate to take in a user-defined type.) * CHANGE ACL removed. GRANT/REVOKE syntax added. - Privileges can be given to a group using the "GROUP" key word. @@ -6449,7 +6449,7 @@ Bug fixes: Other changes and enhancements: * addition of an EXPLAIN statement used for explaining the query execution - plan (eg. "EXPLAIN SELECT * FROM EMP" prints out the execution plan for + plan (e.g., "EXPLAIN SELECT * FROM EMP" prints out the execution plan for the query). * WARN and NOTICE messages no longer have timestamps on them. To turn on timestamps of error messages, uncomment the line in diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index f337485..18e52e5 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1766,7 +1766,7 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433 be migrated in-place from one major PostgreSQL version to another. Upgrades can be performed in minutes, particularly with