diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 19abd7fe65d..53bf6608e03 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -408,7 +408,7 @@ include_dir 'directory' start with the . character are also ignored, to prevent mistakes since such files are hidden on some platforms. Multiple files within an include directory are processed in file name order - (according to C locale rules, i.e. numbers before letters, and + (according to C locale rules, i.e., numbers before letters, and uppercase letters before lowercase ones). @@ -1047,7 +1047,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. @@ -2975,7 +2975,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. @@ -4017,7 +4017,7 @@ ANY num_sync ( . 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/ecpg.sgml b/doc/src/sgml/ecpg.sgml index 03eb266d125..b4e69664057 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -3659,7 +3659,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. @@ -4076,7 +4076,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. @@ -8014,7 +8014,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 7dbe02a64ca..5c28d5aeb0f 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -573,7 +573,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 for more information. @@ -1438,7 +1438,7 @@ include $(PGXS) NO_INSTALLCHECK - don't define an installcheck target, useful e.g. if tests require special configuration, or don't use pg_regress + don't define an installcheck target, useful e.g., if tests require special configuration, or don't use pg_regress diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 8b9aab82d55..e049a24dfd5 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -6335,9 +6335,9 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}'); In to_timestamp and to_date, - 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. @@ -9786,7 +9786,7 @@ CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple "string" (to include all string values), "numeric" (to include all numeric values in the string format), "boolean" (to include all Boolean values in the string format "true"/"false"), "key" (to include all keys) or "all" (to include all above). These values - can be combined together to include, e.g. all string and numeric values. + can be combined together to include, e.g., all string and numeric values. json_to_tsvector('english', '{"a": "The Fat Rats", "b": 123}'::json, '["string", "numeric"]') '123':5 'fat':2 'rat':3 @@ -20796,7 +20796,7 @@ FOR EACH ROW EXECUTE FUNCTION suppress_redundant_updates_trigger(); objsubid integer - Sub-object ID (e.g. attribute number for a column) + Sub-object ID (e.g., attribute number for a column) command_tag @@ -20883,7 +20883,7 @@ FOR EACH ROW EXECUTE FUNCTION suppress_redundant_updates_trigger(); objsubid integer - Sub-object ID (e.g. attribute number for a column) + Sub-object ID (e.g., attribute number for a column) original diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 3403dcd9fb4..ec5f5620ae5 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -219,7 +219,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 @@ -657,7 +657,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. @@ -2224,7 +2224,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 @@ -2290,7 +2290,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_wal etc. + e.g., pg_start_backup, pg_switch_wal etc. diff --git a/doc/src/sgml/indexam.sgml b/doc/src/sgml/indexam.sgml index d758a4987dc..40b9d78e0fe 100644 --- a/doc/src/sgml/indexam.sgml +++ b/doc/src/sgml/indexam.sgml @@ -370,7 +370,7 @@ amcanreturn (Relation indexRelation, int attno); linkend="indexes-index-only-scans">index-only scans on the given column, by returning the indexed column values for an index entry in the form of an IndexTuple. The attribute number - is 1-based, i.e. the first column's attno is 1. Returns true if supported, + is 1-based, i.e., the first column's attno is 1. Returns true if supported, else false. If the access method does not support index-only scans at all, the amcanreturn field in its IndexAmRoutine struct can be set to NULL. diff --git a/doc/src/sgml/install-windows.sgml b/doc/src/sgml/install-windows.sgml index 93241d993a0..318c5082760 100644 --- a/doc/src/sgml/install-windows.sgml +++ b/doc/src/sgml/install-windows.sgml @@ -108,7 +108,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 @@ -241,7 +241,7 @@ $ENV{MSBFLAGS}="/m"; 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 3915098158f..c54b3340391 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -355,7 +355,7 @@ PostgresPollingStatusType PQconnectPoll(PGconn *conn); Conversely, if PQconnectPoll(conn) last returned PGRES_POLLING_WRITING, wait until the socket is ready to write, then call PQconnectPoll(conn) again. - On the first iteration, i.e. if you have yet to call + On the first iteration, i.e., if you have yet to call PQconnectPoll, behave as if it last returned PGRES_POLLING_WRITING. Continue this loop until PQconnectPoll(conn) returns @@ -860,7 +860,7 @@ postgresql:///mydb?host=localhost&port=5433 Percent-encoding may be used to include symbols with special meaning in any - of the URI parts, e.g. replace = with + of the URI parts, e.g., replace = with %3D. @@ -919,7 +919,7 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname hostaddr, and port options accept a comma-separated list of values. The same number of elements must be given in each option that is specified, such - that e.g. the first hostaddr corresponds to the first host name, + that e.g., the first hostaddr corresponds to the first host name, the second hostaddr corresponds to the second host name, and so forth. As an exception, if only one port is specified, it applies to all the hosts. @@ -947,7 +947,7 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname If a password file is used, you can have different passwords for different hosts. All the other connection options are the same for every - host in the list; it is not possible to e.g. specify different + host in the list; it is not possible to e.g., specify different usernames for different hosts. @@ -1123,7 +1123,7 @@ postgresql://%2Fvar%2Flib%2Fpostgresql/dbname Maximum wait for connection, in seconds (write as a decimal integer, - e.g. 10). Zero, negative, or not specified means + e.g., 10). Zero, negative, or not specified means wait indefinitely. The minimum allowed timeout is 2 seconds, therefore a value of 1 is interpreted as 2. This timeout applies separately to each host name or IP address. @@ -2231,7 +2231,7 @@ const char *PQsslAttribute(const PGconn *conn, const char *attribute_name); cipher - A short name of the ciphersuite used, e.g. + A short name of the ciphersuite used, e.g., "DHE-RSA-DES-CBC3-SHA". The names are specific to each SSL implementation. @@ -4880,7 +4880,7 @@ int PQflush(PGconn *conn); PQflush again. Repeat until PQflush returns 0. (It is necessary to check for read-ready and drain the input with PQconsumeInput, - because the server can block trying to send us data, e.g. NOTICE + because the server can block trying to send us data, e.g., NOTICE messages, and won't read our data until we read its.) Once PQflush returns 0, wait for the socket to be read-ready and then read the response as described above. @@ -7889,7 +7889,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/monitoring.sgml b/doc/src/sgml/monitoring.sgml index f63988865f9..32932475340 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -206,7 +206,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/mvcc.sgml b/doc/src/sgml/mvcc.sgml index 34a3ae5a0bf..b64f79c49e3 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -269,7 +269,7 @@ In PostgreSQL, you can request any of the four standard transaction isolation levels, but internally only - three distinct isolation levels are implemented, i.e. PostgreSQL's + three distinct isolation levels are implemented, i.e., PostgreSQL's Read Uncommitted mode behaves like Read Committed. This is because it is the only sensible way to map the standard isolation levels to PostgreSQL's multiversion concurrency control architecture. diff --git a/doc/src/sgml/parallel.sgml b/doc/src/sgml/parallel.sgml index 6c30916655d..891586f83d4 100644 --- a/doc/src/sgml/parallel.sgml +++ b/doc/src/sgml/parallel.sgml @@ -458,7 +458,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%'; . Of course, this plan may turn out to be slower than the serial plan which the planner preferred, but this will not always be the case. If you don't get a parallel - plan even with very small values of these settings (e.g. after setting + plan even with very small values of these settings (e.g., after setting them both to zero), there may be some reason why the query planner is unable to generate a parallel plan for your query. See and @@ -556,7 +556,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%'; Functions and aggregates must be marked PARALLEL UNSAFE if they write to the database, access sequences, change the transaction state - even temporarily (e.g. a PL/pgSQL function which establishes an + even temporarily (e.g., a PL/pgSQL function which establishes an EXCEPTION block to catch errors), or make persistent changes to settings. Similarly, functions must be marked PARALLEL RESTRICTED if they access temporary tables, client connection state, diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml index 992486eabea..f1a322d0788 100644 --- a/doc/src/sgml/perform.sgml +++ b/doc/src/sgml/perform.sgml @@ -1821,7 +1821,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/protocol.sgml b/doc/src/sgml/protocol.sgml index 30e6a0ab20a..d6f111e28f7 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -28,7 +28,7 @@ the server, the connection will be rejected (for example, this would occur if the client requested protocol version 4.0, which does not exist as of this writing). If the minor version requested by the client is not - supported by the server (e.g. the client requests version 3.1, but the + supported by the server (e.g., the client requests version 3.1, but the server supports only 3.0), the server may either reject the connection or may respond with a NegotiateProtocolVersion message containing the highest minor protocol version which it supports. The client may then choose either @@ -422,7 +422,7 @@ by the client, but does support an earlier version of the protocol; this message indicates the highest supported minor version. This message will also be sent if the client requested unsupported protocol - options (i.e. beginning with _pq_.) in the + options (i.e., beginning with _pq_.) in the startup packet. This message will be followed by an ErrorResponse or a message indicating the success or failure of authentication. diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml index 88bc1896468..90ad45a12e3 100644 --- a/doc/src/sgml/queries.sgml +++ b/doc/src/sgml/queries.sgml @@ -1256,7 +1256,7 @@ GROUPING SETS ( ( ) ) - This is commonly used for analysis over hierarchical data; e.g. total + This is commonly used for analysis over hierarchical data; e.g., total salary by department, division, and company-wide total. @@ -1265,7 +1265,7 @@ GROUPING SETS ( CUBE ( e1, e2, ... ) - represents the given list and all of its possible subsets (i.e. the power + represents the given list and all of its possible subsets (i.e., the power set). Thus CUBE ( a, b, c ) diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml index 92825fdf192..d139fa28eb9 100644 --- a/doc/src/sgml/recovery-config.sgml +++ b/doc/src/sgml/recovery-config.sgml @@ -173,7 +173,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 a3b2e98b467..88e93ea2a15 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_event_trigger.sgml b/doc/src/sgml/ref/create_event_trigger.sgml index 52ba746166b..becd31bcadf 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 7b16aff7215..831529db17f 100644 --- a/doc/src/sgml/ref/create_function.sgml +++ b/doc/src/sgml/ref/create_function.sgml @@ -256,7 +256,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. @@ -430,11 +430,11 @@ CREATE [ OR REPLACE ] FUNCTION Functions should be labeled parallel unsafe if they modify any database state, or if they make changes to the transaction such as using sub-transactions, or if they access sequences or attempt to make - persistent changes to settings (e.g. setval). They should + persistent changes to settings (e.g., setval). They should be labeled as parallel restricted if they access temporary tables, client connection state, cursors, prepared statements, or miscellaneous backend-local state which the system cannot synchronize in parallel mode - (e.g. setseed cannot be executed other than by the group + (e.g., setseed cannot be executed other than by the group leader because a change made by another process would not be reflected in the leader). In general, if a function is labeled as being safe when it is restricted or unsafe, or if it is labeled as being restricted when diff --git a/doc/src/sgml/ref/create_procedure.sgml b/doc/src/sgml/ref/create_procedure.sgml index 0ea6513cb58..d225695626c 100644 --- a/doc/src/sgml/ref/create_procedure.sgml +++ b/doc/src/sgml/ref/create_procedure.sgml @@ -164,7 +164,7 @@ CREATE [ OR REPLACE ] PROCEDURE The name of the language that the procedure 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_statistics.sgml b/doc/src/sgml/ref/create_statistics.sgml index 539f5bded54..f5367cfcc67 100644 --- a/doc/src/sgml/ref/create_statistics.sgml +++ b/doc/src/sgml/ref/create_statistics.sgml @@ -129,7 +129,7 @@ CREATE STATISTICS [ IF NOT EXISTS ] statistics_na Examples - Create table t1 with two functionally dependent columns, i.e. + Create table t1 with two functionally dependent columns, i.e., knowledge of a value in the first column is sufficient for determining the value in the other column. Then functional dependency statistics are built on those columns: diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index b9e178834b0..2b9848b6806 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -813,7 +813,7 @@ WITH ( MODULUS numeric_literal, REM one or more columns on which the uniqueness is not enforced. Note that although the constraint is not enforced on the included columns, it still depends on them. Consequently, some operations on these columns - (e.g. DROP COLUMN) can cause cascaded constraint and + (e.g., DROP COLUMN) can cause cascaded constraint and index deletion. @@ -859,7 +859,7 @@ WITH ( MODULUS numeric_literal, REM of columns to be specified which will be included in the non-key portion of the index. Although uniqueness is not enforced on the included columns, the constraint still depends on them. Consequently, some operations on the - included columns (e.g. DROP COLUMN) can cause cascaded + included columns (e.g., DROP COLUMN) can cause cascaded constraint and index deletion. diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml index 1f0a9791ed4..86cd167635f 100644 --- a/doc/src/sgml/ref/grant.sgml +++ b/doc/src/sgml/ref/grant.sgml @@ -357,7 +357,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 84fb37c293a..a37311d5538 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -88,7 +88,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 13d15c27dc3..3c76aad3606 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -763,7 +763,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 is also specified. diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index b1562e6ceeb..af0a02bc129 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -305,7 +305,7 @@ PostgreSQL documentation - Use conditional commands (i.e. add an IF EXISTS + Use conditional commands (i.e., add an IF EXISTS clause) to drop databases and other objects. This option is not valid unless is also specified. diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index 800d635336d..e03450362a5 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -571,7 +571,7 @@ PostgreSQL documentation - Use conditional commands (i.e. add an IF EXISTS + Use conditional commands (i.e., add an IF EXISTS clause) to drop database objects. This option is not valid unless is also specified. diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index 670371e0dfc..3cd6fc9464f 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -70,7 +70,7 @@ PostgreSQL documentation files might no longer be present. In that case, they can be manually copied from the WAL archive to the pg_wal directory, or fetched on startup by configuring recovery.conf. The use of - pg_rewind is not limited to failover, e.g. a standby + pg_rewind is not limited to failover, e.g., a standby server can be promoted, run some write transactions, and then rewinded to become a standby again. diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index 2df606d83e4..b7463177d15 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -561,7 +561,7 @@ pgbench options d transaction to finish. The wait time is called the schedule lag time, and its average and maximum are also reported separately. The transaction latency with respect to the actual transaction start time, - i.e. the time spent executing the transaction in the database, can be + i.e., the time spent executing the transaction in the database, can be computed by subtracting the schedule lag time from the reported latency. @@ -711,7 +711,7 @@ pgbench options d client per thread and there are no external or data dependencies. From a statistical viewpoint reproducing runs exactly is a bad idea because it can hide the performance variability or improve performance unduly, - e.g. by hitting the same pages as a previous run. + e.g., by hitting the same pages as a previous run. However, it may also be of great help for debugging, for instance re-running a tricky case which leads to an error. Use wisely. @@ -731,7 +731,7 @@ pgbench options d 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). @@ -1479,7 +1479,7 @@ f(x) = PHI(2.0 * parameter * (x - mu) / (max - min + 1)) / 2.0 / parameter, that is a relative 1.0 / parameter around the mean; for instance, if parameter is 4.0, 67% of values are drawn from the - middle quarter (1.0 / 4.0) of the interval (i.e. from + middle quarter (1.0 / 4.0) of the interval (i.e., from 3.0 / 8.0 to 5.0 / 8.0) and 95% from the middle half (2.0 / 4.0) of the interval (second and third quartiles). The minimum parameter is 2.0 for performance @@ -1679,7 +1679,7 @@ END; and max_lag, are only present if the option is used. They provide statistics about the time each transaction had to wait for the - previous one to finish, i.e. the difference between each transaction's + previous one to finish, i.e., the difference between each transaction's scheduled start time and the time it actually started. The very last field, skipped, is only present if the option is used, too. diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index e3f5c5c750d..f711cb5297b 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -41,8 +41,8 @@ PostgreSQL documentation 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 9.5.8 to 9.6.4 or from 10.7 to 11.2. - It is not required for minor version upgrades, e.g. from 9.6.2 to 9.6.3 + major version upgrades, e.g., from 9.5.8 to 9.6.4 or from 10.7 to 11.2. + It is not required for minor version upgrades, e.g., from 9.6.2 to 9.6.3 or from 10.1 to 10.2. @@ -60,7 +60,7 @@ PostgreSQL documentation 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 @@ -209,13 +209,13 @@ PostgreSQL documentation 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/&majorversion;, 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 @@ -273,9 +273,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., CREATE EXTENSION pgcrypto, because these will be upgraded from the old cluster. Also, any custom full text search files (dictionary, synonym, @@ -481,7 +481,7 @@ pg_upgrade.exe Save any configuration files from the old standbys' configuration - directories you need to keep, e.g. postgresql.conf + directories you need to keep, e.g., postgresql.conf (and any files included by it), postgresql.auto.conf, recovery.conf, pg_hba.conf, because these will be overwritten or removed in the next step. @@ -508,7 +508,7 @@ rsync --archive --delete --hard-links --size-only --no-inc-recursive old_cluster on the standby. The directory structure under the specified directories on the primary and standbys must match. Consult the rsync manual page for details on specifying the - remote directory, e.g. + remote directory, e.g., rsync --archive --delete --hard-links --size-only --no-inc-recursive /opt/PostgreSQL/9.5 \ @@ -634,7 +634,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). @@ -734,7 +734,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'. @@ -755,7 +755,7 @@ psql --username=postgres --file=script.sql postgres copy with any changes to make it consistent. ( is necessary because rsync only has file modification-time granularity of one second.) 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/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index 53dc05a78f0..2a0d4fce510 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -822,7 +822,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/prepare.sgml b/doc/src/sgml/ref/prepare.sgml index 3d799b5b579..86ce607792c 100644 --- a/doc/src/sgml/ref/prepare.sgml +++ b/doc/src/sgml/ref/prepare.sgml @@ -73,7 +73,7 @@ PREPARE name [ ( name [ ( To examine the query plan PostgreSQL is using - for a prepared statement, use , e.g. + for a prepared statement, use , e.g., EXPLAIN EXECUTE. If a generic plan is in use, it will contain parameter symbols $n, while a custom plan will have the diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index d76ed41149b..4d695c90188 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -626,7 +626,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. @@ -2794,7 +2794,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. @@ -4220,7 +4220,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/release-11.sgml b/doc/src/sgml/release-11.sgml index bb66ef07dc9..bd85114f3dc 100644 --- a/doc/src/sgml/release-11.sgml +++ b/doc/src/sgml/release-11.sgml @@ -10402,7 +10402,7 @@ same commits as above --> - Allow single-evaluation queries, e.g. WHERE + Allow single-evaluation queries, e.g., WHERE clause aggregate queries, and functions in the target list to be parallelized (Amit Kapila, Robert Haas) @@ -11039,7 +11039,7 @@ same commits as above PostgreSQL only allows superusers to access postgres_fdw tables without - passwords, e.g. via peer. Previously, the + passwords, e.g., via peer. Previously, the session owner had to be a superuser to allow such access; now the view owner is checked instead. @@ -11636,7 +11636,7 @@ same commits as above --> - Allow PL/pgSQL to handle changes to composite types (e.g. record, + Allow PL/pgSQL to handle changes to composite types (e.g., record, row) that happen between the first and later function executions in the same session (Tom Lane) @@ -12375,7 +12375,7 @@ same commits as above SCRAM cannot prevent them unless it can be forced to be active. Unfortunately, there is no way to do that in libpq. Support for it is expected in future versions of libpq and in - interfaces not built using libpq, e.g. JDBC. + interfaces not built using libpq, e.g., JDBC. diff --git a/doc/src/sgml/replication-origins.sgml b/doc/src/sgml/replication-origins.sgml index a03ce76e2ef..7e02c4605b2 100644 --- a/doc/src/sgml/replication-origins.sgml +++ b/doc/src/sgml/replication-origins.sgml @@ -31,7 +31,7 @@ which is what should be used to refer to the origin across systems, is free-form text. It should be used in a way that makes conflicts between replication origins created by different replication solutions - unlikely; e.g. by prefixing the replication solution's name to it. + unlikely; e.g., by prefixing the replication solution's name to it. The OID is used only to avoid having to store the long version in situations where space efficiency is important. It should never be shared across systems. @@ -68,7 +68,7 @@ manner. Replay progress for all replication origins can be seen in the pg_replication_origin_status - view. An individual origin's progress, e.g. when resuming + view. An individual origin's progress, e.g., when resuming replication, can be acquired using pg_replication_origin_progress() for any origin or @@ -86,7 +86,7 @@ output plugin callbacks (see ) generated by the session is tagged with the replication origin of the generating session. This allows treating them differently in the output - plugin, e.g. ignoring all but locally-originating rows. Additionally + plugin, e.g., ignoring all but locally-originating rows. Additionally the filter_by_origin_cb callback can be used to filter the logical decoding change stream based on the diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index a73e9d78e3e..b3875d6e21b 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1960,7 +1960,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 mode. It requires steps similar to - pg_dumpall above, e.g. starting/stopping the server, + pg_dumpall above, e.g., starting/stopping the server, running initdb. The pg_upgrade documentation outlines the necessary steps. diff --git a/doc/src/sgml/sepgsql.sgml b/doc/src/sgml/sepgsql.sgml index f8c99e1b002..64cde0adb56 100644 --- a/doc/src/sgml/sepgsql.sgml +++ b/doc/src/sgml/sepgsql.sgml @@ -527,7 +527,7 @@ UPDATE t1 SET x = 2, y = func1(y) WHERE z = 100; commands. SELinux provides a feature to allow trusted code to run using a security label different from that of the client, generally for the purpose of providing highly controlled access to - sensitive data (e.g. rows might be omitted, or the precision of stored + sensitive data (e.g., rows might be omitted, or the precision of stored values might be reduced). Whether or not a function acts as a trusted procedure is controlled by its security label and the operating system security policy. For example: diff --git a/doc/src/sgml/sources.sgml b/doc/src/sgml/sources.sgml index 1a3d905ab7e..f1e5bf291c5 100644 --- a/doc/src/sgml/sources.sgml +++ b/doc/src/sgml/sources.sgml @@ -888,7 +888,7 @@ BETTER: unrecognized node type: 42 Both, macros with arguments and static inline functions, may be used. The latter are preferable if there are - multiple-evaluation hazards when written as a macro, as e.g. the + multiple-evaluation hazards when written as a macro, as e.g., the case with #define Max(x, y) ((x) > (y) ? (x) : (y)) @@ -899,7 +899,7 @@ BETTER: unrecognized node type: 42 When the definition of an inline function references symbols - (i.e. variables, functions) that are only available as part of the + (i.e., variables, functions) that are only available as part of the backend, the function may not be visible when included from frontend code. diff --git a/doc/src/sgml/sslinfo.sgml b/doc/src/sgml/sslinfo.sgml index 45d1136ac9a..74aaf1b2af3 100644 --- a/doc/src/sgml/sslinfo.sgml +++ b/doc/src/sgml/sslinfo.sgml @@ -47,7 +47,7 @@ - Returns the name of the protocol used for the SSL connection (e.g. TLSv1.0 + Returns the name of the protocol used for the SSL connection (e.g., TLSv1.0 TLSv1.1, or TLSv1.2). @@ -63,7 +63,7 @@ Returns the name of the cipher used for the SSL connection - (e.g. DHE-RSA-AES256-SHA). + (e.g., DHE-RSA-AES256-SHA). diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml index 13feb1fc3b6..9c889feb6b8 100644 --- a/doc/src/sgml/textsearch.sgml +++ b/doc/src/sgml/textsearch.sgml @@ -3705,7 +3705,7 @@ SELECT plainto_tsquery('supernovae stars'); allows the implementation of very fast searches with online update. Partitioning can be done at the database level using table inheritance, or by distributing documents over - servers and collecting external search results, e.g. via Foreign Data access. The latter is possible because ranking functions use only local information. diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index bd9fae544c1..a94edf4d8b6 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -266,7 +266,7 @@ overhead can reduce performance, especially if journaling causes file system data to be flushed to disk. Fortunately, data flushing during journaling can - often be disabled with a file system mount option, e.g. + often be disabled with a file system mount option, e.g., data=writeback on a Linux ext3 file system. Journaled file systems do improve boot speed after a crash. diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml index ea72622c47f..4b0d2ff12be 100644 --- a/doc/src/sgml/xfunc.sgml +++ b/doc/src/sgml/xfunc.sgml @@ -152,9 +152,9 @@ Besides SELECT queries, the commands can include data modification queries (INSERT, UPDATE, and DELETE), as well as - other SQL commands. (You cannot use transaction control commands, e.g. + other SQL commands. (You cannot use transaction control commands, e.g., COMMIT, SAVEPOINT, and some utility - commands, e.g. VACUUM, in SQL functions.) + commands, e.g., VACUUM, in SQL functions.) However, the final command must be a SELECT or have a RETURNING clause that returns whatever is @@ -3421,7 +3421,7 @@ if (!ptr) exceptions. Any exceptions must be caught and appropriate errors passed back to the C interface. If possible, compile C++ with to eliminate exceptions entirely; in such - cases, you must check for failures in your C++ code, e.g. check for + cases, you must check for failures in your C++ code, e.g., check for NULL returned by new(). diff --git a/doc/src/sgml/xml2.sgml b/doc/src/sgml/xml2.sgml index 560faa000ec..f5346336104 100644 --- a/doc/src/sgml/xml2.sgml +++ b/doc/src/sgml/xml2.sgml @@ -327,7 +327,7 @@ AS t(article_id integer, author text, page_count integer, title text); The calling SELECT statement doesn't necessarily have to be just SELECT * — it can reference the output columns by name or join them to other tables. The function produces a - virtual table with which you can perform any operation you wish (e.g. + virtual table with which you can perform any operation you wish (e.g., aggregation, joining, sorting etc). So we could also have: SELECT t.title, p.fullname, p.email