diff options
41 files changed, 93 insertions, 93 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index d6439d783cf..479b88592e2 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -407,7 +407,7 @@ include_dir 'directory' start with the <literal>.</literal> 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). </para> @@ -1259,7 +1259,7 @@ include_dir 'conf.d' <para> With this parameter enabled, you can still create ordinary global users. Simply append <literal>@</> when specifying the user - name in the client, e.g. <literal>joe@</>. The <literal>@</> + name in the client, e.g., <literal>joe@</>. The <literal>@</> will be stripped off before the user name is looked up by the server. </para> @@ -2820,7 +2820,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 <varname>archive_command</> to a command that does nothing but - return true, e.g. <literal>/bin/true</> (<literal>REM</> on + return true, e.g., <literal>/bin/true</> (<literal>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. @@ -3652,7 +3652,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, e.g., <literal>1.1</literal>. </para> @@ -7134,7 +7134,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. </para> @@ -7639,7 +7639,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' with assertions enabled. That is the case if the macro <symbol>USE_ASSERT_CHECKING</symbol> is defined when <productname>PostgreSQL</productname> is built (accomplished - e.g. by the <command>configure</command> option + e.g., by the <command>configure</command> option <option>--enable-cassert</option>). By default <productname>PostgreSQL</productname> is built without assertions. diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 25adb21faec..8ec92f9ba8c 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -501,7 +501,7 @@ very large number of digits. It is especially recommended for storing monetary amounts and other quantities where exactness is required. Calculations with <type>numeric</type> values yield exact - results where possible, e.g. addition, subtraction, multiplication. + results where possible, e.g., addition, subtraction, multiplication. However, calculations on <type>numeric</type> values are very slow compared to the integer types, or to the floating-point types described in the next section. diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 40fe41463b0..611b0169833 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -1510,7 +1510,7 @@ ALTER TABLE products RENAME TO items; <para> An object can be assigned to a new owner with an <command>ALTER</command> - command of the appropriate kind for the object, e.g. <xref + command of the appropriate kind for the object, e.g., <xref linkend="sql-altertable">. 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 f8389c74c1c..037731feb0a 100644 --- a/doc/src/sgml/docguide.sgml +++ b/doc/src/sgml/docguide.sgml @@ -692,16 +692,16 @@ save_size.pdfjadetex = 15000 <para> 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 <quote>Overfull - hbox</quote> messages in the TeX log output file, e.g. + hbox</quote> messages in the TeX log output file, e.g., <filename>postgres-US.log</> or <filename>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 <acronym>SGML</acronym> text causing the overflow, find the first page number mentioned above - the overflow message, e.g. <literal>[50 ###]</> (page 50), and - look at the page after that (e.g. page 51) in the <acronym>PDF</acronym> + the overflow message, e.g., <literal>[50 ###]</> (page 50), and + look at the page after that (e.g., page 51) in the <acronym>PDF</acronym> file to see the overflow text and adjust the <acronym>SGML</acronym> accordingly. </para> diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index 69f422b4d84..27534872dee 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -3627,7 +3627,7 @@ EXEC SQL DEALLOCATE DESCRIPTOR <replaceable>identifier</replaceable>; EXEC SQL FETCH NEXT FROM mycursor INTO SQL DESCRIPTOR mydesc; </programlisting> 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. </para> <para> @@ -4044,7 +4044,7 @@ typedef struct sqlvar_struct sqlvar_t; <term><literal>sqllen</></term> <listitem> <para> - Contains the binary length of the field. e.g. 4 bytes for <type>ECPGt_int</type>. + Contains the binary length of the field. e.g., 4 bytes for <type>ECPGt_int</type>. </para> </listitem> </varlistentry> @@ -7971,7 +7971,7 @@ EXEC SQL CLOSE DATABASE; <term><literal>FREE cursor_name</></term> <listitem> <para> - 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 <literal>FREE cursor_name</> statement in ECPG. This is because in ECPG, <literal>DECLARE CURSOR</literal> doesn't translate to a function call into diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index d8b68d0dcf4..2a92d75f2b4 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -533,7 +533,7 @@ <para> An extension is <firstterm>relocatable</> if it is possible to move its contained objects into a different schema after initial creation - of the extension. The default is <literal>false</>, i.e. the + of the extension. The default is <literal>false</>, i.e., the extension is not relocatable. See <xref linkend="extend-extensions-relocation"> for more information. </para> diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 0c5f8068c7b..521fa9e0cbe 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -6151,7 +6151,7 @@ SELECT regexp_matches('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}'); will be replaced by the year data, but the single <literal>Y</literal> in <literal>Year</literal> will not be. In <function>to_date</>, <function>to_number</>, and <function>to_timestamp</>, double-quoted strings skip the number of - input characters contained in the string, e.g. <literal>"XX"</> + input characters contained in the string, e.g., <literal>"XX"</> skips two input characters. </para> </listitem> @@ -6166,9 +6166,9 @@ SELECT regexp_matches('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}'); <listitem> <para> - If the year format specification is less than four digits, e.g. + If the year format specification is less than four digits, e.g., <literal>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., <literal>95</> becomes 1995. </para> </listitem> @@ -6281,7 +6281,7 @@ SELECT regexp_matches('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}'); <listitem> <para> <function>to_char(interval)</function> formats <literal>HH</> and - <literal>HH12</> as shown on a 12-hour clock, i.e. zero hours + <literal>HH12</> as shown on a 12-hour clock, i.e., zero hours and 36 hours output as <literal>12</>, while <literal>HH24</> outputs the full hour value, which can exceed 23 for intervals. </para> @@ -19849,7 +19849,7 @@ FOR EACH ROW EXECUTE PROCEDURE suppress_redundant_updates_trigger(); <row> <entry><literal>objsubid</literal></entry> <entry><type>integer</type></entry> - <entry>Sub-object ID (e.g. attribute number for a column)</entry> + <entry>Sub-object ID (e.g., attribute number for a column)</entry> </row> <row> <entry><literal>command_tag</literal></entry> @@ -19936,7 +19936,7 @@ FOR EACH ROW EXECUTE PROCEDURE suppress_redundant_updates_trigger(); <row> <entry><literal>objsubid</literal></entry> <entry><type>integer</type></entry> - <entry>Sub-object ID (e.g. attribute number for a column)</entry> + <entry>Sub-object ID (e.g., attribute number for a column)</entry> </row> <row> <entry><literal>original</literal></entry> diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 2d1b734375c..301befee927 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -201,7 +201,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 @@ -628,7 +628,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 <xref linkend="continuous-archiving">. 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. </para> @@ -2131,7 +2131,7 @@ LOG: database system is ready to accept read only connections <itemizedlist> <listitem> <para> - Data Definition Language (DDL) - e.g. <command>CREATE INDEX</> + Data Definition Language (DDL) - e.g., <command>CREATE INDEX</> </para> </listitem> <listitem> @@ -2197,7 +2197,7 @@ LOG: database system is ready to accept read only connections <para> WAL file control commands will not work during recovery, - e.g. <function>pg_start_backup</>, <function>pg_switch_xlog</> etc. + e.g., <function>pg_start_backup</>, <function>pg_switch_xlog</> etc. </para> <para> diff --git a/doc/src/sgml/indexam.sgml b/doc/src/sgml/indexam.sgml index a613ae7ddc0..2a4b0c61c42 100644 --- a/doc/src/sgml/indexam.sgml +++ b/doc/src/sgml/indexam.sgml @@ -352,7 +352,7 @@ amcanreturn (Relation indexRelation, int attno); linkend="indexes-index-only-scans"><firstterm>index-only scans</></link> on the given column, by returning the indexed column values for an index entry in the form of an <structname>IndexTuple</structname>. 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 <structfield>amcanreturn</> field in its <structname>IndexAmRoutine</> struct can be set to NULL. diff --git a/doc/src/sgml/install-windows.sgml b/doc/src/sgml/install-windows.sgml index 1095a5530eb..a80d043b3f8 100644 --- a/doc/src/sgml/install-windows.sgml +++ b/doc/src/sgml/install-windows.sgml @@ -116,7 +116,7 @@ In the <productname>Microsoft Windows SDK</productname>, start the <application>CMD shell</application> 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 <command>setenv</command> command, e.g. + type, and target OS by using the <command>setenv</command> command, e.g., <command>setenv /x86 /release /xp</command> to target Windows XP or later with a 32-bit release build. See <command>/?</command> for other options to <command>setenv</command>. All commands should be run from the @@ -241,7 +241,7 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin'; installations <filename>C:\Program Files\GnuWin32</filename>. Consider installing into <filename>C:\GnuWin32</filename> or use the NTFS short name path to GnuWin32 in your PATH environment setting - (e.g. <filename>C:\PROGRA~1\GnuWin32</filename>). + (e.g., <filename>C:\PROGRA~1\GnuWin32</filename>). </para> </note> diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 007519e195a..f2eba420788 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1949,7 +1949,7 @@ const char *PQsslAttribute(const PGconn *conn, const char *attribute_name); <term><literal>cipher</literal></term> <listitem> <para> - A short name of the ciphersuite used, e.g. + A short name of the ciphersuite used, e.g., <literal>"DHE-RSA-DES-CBC3-SHA"</literal>. The names are specific to each SSL implementation. </para> @@ -4596,7 +4596,7 @@ int PQflush(PGconn *conn); <function>PQflush</function> again. Repeat until <function>PQflush</function> returns 0. (It is necessary to check for read-ready and drain the input with <function>PQconsumeInput</function>, - 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 <function>PQflush</function> returns 0, wait for the socket to be read-ready and then read the response as described above. @@ -7525,7 +7525,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 <emphasis>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 <literal>sslmode</> parameter to <literal>verify-full</> or diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 879c7d8c167..4744f220647 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 <filename>pg_stat</filename> 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. </para> diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index 56ae543e577..29a4cc3a1e7 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -269,7 +269,7 @@ <para> In <productname>PostgreSQL</productname>, 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 2ec3157a0aa..b4ae248985f 100644 --- a/doc/src/sgml/parallel.sgml +++ b/doc/src/sgml/parallel.sgml @@ -336,7 +336,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%'; <xref linkend="guc-parallel-tuple-cost">. 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 <xref linkend="when-can-parallel-query-be-used"> and @@ -428,7 +428,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%'; <para> Functions and aggregates must be marked <literal>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 <literal>EXCEPTION</> block to catch errors), or make persistent changes to settings. Similarly, functions must be marked <literal>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 9a1c21a5425..9df866442cd 100644 --- a/doc/src/sgml/perform.sgml +++ b/doc/src/sgml/perform.sgml @@ -1578,7 +1578,7 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse; <listitem> <para> Place the database cluster's data directory in a memory-backed - file system (i.e. <acronym>RAM</> disk). This eliminates all + file system (i.e., <acronym>RAM</> disk). This eliminates all database disk I/O, but limits data storage to the amount of available memory (and perhaps swap). </para> diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index d01fdcc3723..87d67c00569 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 @@ -382,7 +382,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 <literal>_pq_.</literal>) in the + options (i.e., beginning with <literal>_pq_.</literal>) in the startup packet. This message will be followed by an ErrorResponse or a message indicating the success or failure of authentication. </para> diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml index b851d134b72..781ea43d4be 100644 --- a/doc/src/sgml/queries.sgml +++ b/doc/src/sgml/queries.sgml @@ -1258,7 +1258,7 @@ GROUPING SETS ( ( ) ) </programlisting> - 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. </para> @@ -1267,7 +1267,7 @@ GROUPING SETS ( <programlisting> CUBE ( <replaceable>e1</>, <replaceable>e2</>, ... ) </programlisting> - 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 <programlisting> CUBE ( a, b, c ) diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml index 4a5375ed593..34a136b6602 100644 --- a/doc/src/sgml/recovery-config.sgml +++ b/doc/src/sgml/recovery-config.sgml @@ -172,7 +172,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows <listitem> <para> 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. </para> diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml index 4ce321ef79f..956da106f1d 100644 --- a/doc/src/sgml/ref/create_database.sgml +++ b/doc/src/sgml/ref/create_database.sgml @@ -116,7 +116,7 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable> <listitem> <para> Collation order (<literal>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 <replaceable class="PARAMETER">name</replaceable> <listitem> <para> Character classification (<literal>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. </para> diff --git a/doc/src/sgml/ref/create_event_trigger.sgml b/doc/src/sgml/ref/create_event_trigger.sgml index be18fc36e80..89410e8d141 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 <replaceable class="PARAMETER">name</replaceable> A list of values for the associated <replaceable class="parameter">filter_variable</replaceable> for which the trigger should fire. For <literal>TAG</>, this means a - list of command tags (e.g. <literal>'DROP FUNCTION'</>). + list of command tags (e.g., <literal>'DROP FUNCTION'</>). </para> </listitem> </varlistentry> diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml index 0f244cfd001..fbee235baa2 100644 --- a/doc/src/sgml/ref/create_function.sgml +++ b/doc/src/sgml/ref/create_function.sgml @@ -257,7 +257,7 @@ CREATE [ OR REPLACE ] FUNCTION The name of the language that the function is implemented in. It can be <literal>sql</literal>, <literal>c</literal>, <literal>internal</literal>, or the name of a user-defined - procedural language, e.g. <literal>plpgsql</literal>. Enclosing the + procedural language, e.g., <literal>plpgsql</literal>. Enclosing the name in single quotes is deprecated and requires matching case. </para> </listitem> @@ -431,11 +431,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. <literal>setval</>). They should + persistent changes to settings (e.g., <literal>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. <literal>setseed</> cannot be executed other than by the group + (e.g., <literal>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/grant.sgml b/doc/src/sgml/ref/grant.sgml index 68fbaa9ed1f..0fc7bb2e0ad 100644 --- a/doc/src/sgml/ref/grant.sgml +++ b/doc/src/sgml/ref/grant.sgml @@ -353,7 +353,7 @@ GRANT <replaceable class="PARAMETER">role_name</replaceable> [, ...] TO <replace schema (assuming that the objects' own privilege requirements are also met). Essentially this allows the grantee to <quote>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 4e339ecce85..ccaefd2082d 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -80,7 +80,7 @@ PostgreSQL documentation <command>initdb</command> initializes the database cluster's default locale and character set encoding. The character set encoding, collation order (<literal>LC_COLLATE</>) and character set classes - (<literal>LC_CTYPE</>, e.g. upper, lower, digit) can be set separately + (<literal>LC_CTYPE</>, e.g., upper, lower, digit) can be set separately for a database when it is created. <command>initdb</command> determines those settings for the <literal>template1</literal> 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 e9443674f81..659cdd77aa0 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -732,7 +732,7 @@ PostgreSQL documentation <term><option>--if-exists</option></term> <listitem> <para> - Use conditional commands (i.e. add an <literal>IF EXISTS</literal> + Use conditional commands (i.e., add an <literal>IF EXISTS</literal> clause) when cleaning database objects. This option is not valid unless <option>--clean</> is also specified. </para> diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml index 806e9694d5c..10c74427b17 100644 --- a/doc/src/sgml/ref/pg_dumpall.sgml +++ b/doc/src/sgml/ref/pg_dumpall.sgml @@ -295,7 +295,7 @@ PostgreSQL documentation <term><option>--if-exists</option></term> <listitem> <para> - Use conditional commands (i.e. add an <literal>IF EXISTS</literal> + Use conditional commands (i.e., add an <literal>IF EXISTS</literal> clause) to clean databases and other objects. This option is not valid unless <option>--clean</> is also specified. </para> diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index 2b762026929..3c23d1c0b0c 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -539,7 +539,7 @@ PostgreSQL documentation <term><option>--if-exists</option></term> <listitem> <para> - Use conditional commands (i.e. add an <literal>IF EXISTS</literal> + Use conditional commands (i.e., add an <literal>IF EXISTS</literal> clause) when cleaning database objects. This option is not valid unless <option>--clean</> is also specified. </para> diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index d3899a4706d..58eda6e351c 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 <filename>pg_xlog</> directory, or fetched on startup by configuring <filename>recovery.conf</>. The use of - <application>pg_rewind</> is not limited to failover, e.g. a standby + <application>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. </para> diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml index d1c87983727..9d5cec7f308 100644 --- a/doc/src/sgml/ref/pgbench.sgml +++ b/doc/src/sgml/ref/pgbench.sgml @@ -484,7 +484,7 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</> 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. </para> @@ -611,7 +611,7 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</> <para> 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). </para> </listitem> @@ -1082,7 +1082,7 @@ f(x) = PHI(2.0 * parameter * (x - mu) / (max - min + 1)) / <literal>2.0 / parameter</>, that is a relative <literal>1.0 / parameter</> around the mean; for instance, if <replaceable>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 <literal>3.0 / 8.0</> to <literal>5.0 / 8.0</>) and 95% from the middle half (<literal>2.0 / 4.0</>) of the interval (second and third quartiles). The minimum <replaceable>parameter</> is 2.0 for performance @@ -1214,7 +1214,7 @@ END; option is used. The very last one, <replaceable>skipped_transactions</>, is only present if the option <option>--latency-limit</> is present, too. They are calculated from 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. </para> diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index fc5cc8d4a25..71ff99fd054 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -41,8 +41,8 @@ PostgreSQL documentation <application>pg_upgrade</> (formerly called <application>pg_migrator</>) allows data stored in <productname>PostgreSQL</> data files to be upgraded to a later <productname>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 <productname>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 <productname>PostgreSQL</>. It is not required for minor version upgrades, e.g., from 9.0.1 to 9.0.4. </para> @@ -60,7 +60,7 @@ PostgreSQL documentation <para> <application>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 <title>Optionally move the old cluster</title> <para> - If you are using a version-specific installation directory, e.g. + If you are using a version-specific installation directory, e.g., <filename>/opt/PostgreSQL/9.1</>, you do not need to move the old cluster. The graphical installers all use version-specific installation directories. </para> <para> - If your installation directory is not version-specific, e.g. + If your installation directory is not version-specific, e.g., <filename>/usr/local/pgsql</>, it is necessary to move the current PostgreSQL install directory so it does not interfere with the new <productname>PostgreSQL</> installation. Once the current <productname>PostgreSQL</> server is shut down, it is safe to rename the @@ -273,9 +273,9 @@ make prefix=/usr/local/pgsql.new install <para> Install any custom shared object files (or DLLs) used by the old cluster - into the new cluster, e.g. <filename>pgcrypto.so</filename>, + into the new cluster, e.g., <filename>pgcrypto.so</filename>, whether they are from <filename>contrib</filename> - or some other source. Do not install the schema definitions, e.g. + or some other source. Do not install the schema definitions, e.g., <command>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 <para> Save any configuration files from the old standbys' configuration - directories you need to keep, e.g. <filename>postgresql.conf</filename> + directories you need to keep, e.g., <filename>postgresql.conf</filename> (and any files included by it), <filename>postgresql.auto.conf</filename>, <literal>recovery.conf</literal>, <literal>pg_hba.conf</literal>, 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 <application>rsync</> manual page for details on specifying the - remote directory, e.g. + remote directory, e.g., <programlisting> 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 <command>pg_upgrade</command> 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. <filename>bin</>, <filename>share</>). + (e.g., <filename>bin</>, <filename>share</>). </para> </step> @@ -734,7 +734,7 @@ psql --username postgres --file script.sql postgres If you are upgrading a pre-<productname>PostgreSQL</> 9.2 cluster that uses a configuration-file-only directory, you must pass the real data directory location to <application>pg_upgrade</>, and - pass the configuration directory location to the server, e.g. + pass the configuration directory location to the server, e.g., <literal>-d /real-data-directory -o '-D /configuration-directory'</>. </para> @@ -755,7 +755,7 @@ psql --username postgres --file script.sql postgres copy with any changes to make it consistent. (<option>--checksum</> is necessary because <command>rsync</> only has file modification-time granularity of one second.) You might want to exclude some - files, e.g. <filename>postmaster.pid</>, as documented in <xref + files, e.g., <filename>postmaster.pid</>, as documented in <xref linkend="backup-lowlevel-base-backup">. 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 fc11aa14a60..aaa7f37f2cf 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -822,7 +822,7 @@ PostgreSQL documentation <para> To start <command>postgres</command> with a specific - port, e.g. 1234: + port, e.g., 1234: <screen> <prompt>$</prompt> <userinput>postgres -p 1234</userinput> </screen> diff --git a/doc/src/sgml/ref/prepare.sgml b/doc/src/sgml/ref/prepare.sgml index 8dd5aa00fad..691d6ac064e 100644 --- a/doc/src/sgml/ref/prepare.sgml +++ b/doc/src/sgml/ref/prepare.sgml @@ -73,7 +73,7 @@ PREPARE <replaceable class="PARAMETER">name</replaceable> [ ( <replaceable class Prepared statements potentially have the largest performance advantage when a single session is being used to execute a large number of similar statements. The performance difference will be particularly - significant if the statements are complex to plan or rewrite, e.g. + significant if the statements are complex to plan or rewrite, e.g., if the query involves a join of many tables or requires the application of several rules. If the statement is relatively simple to plan and rewrite but relatively expensive to execute, the @@ -154,7 +154,7 @@ PREPARE <replaceable class="PARAMETER">name</replaceable> [ ( <replaceable class <para> To examine the query plan <productname>PostgreSQL</productname> is using - for a prepared statement, use <xref linkend="sql-explain">, e.g. + for a prepared statement, use <xref linkend="sql-explain">, e.g., <command>EXPLAIN EXECUTE</>. If a generic plan is in use, it will contain parameter symbols <literal>$<replaceable>n</></literal>, 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 e217898fb89..858e3c5ff55 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -612,7 +612,7 @@ EOF <para> <application>psql</application> 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 <varname>ON_ERROR_STOP</varname> was set. @@ -2546,7 +2546,7 @@ lo_import 152801 In <literal>latex-longtable</literal> 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. <literal>'0.2 0.2 0.6'</>. Unspecified output columns + e.g., <literal>'0.2 0.2 0.6'</>. Unspecified output columns use the last specified value. </para> </listitem> @@ -3781,7 +3781,7 @@ testdb=> \set PROMPT1 '%[%033[1;33;40m%]%n@%/%R%[%033[0m%]%# ' <application>psql</application> starts up. Tab-completion is also supported, although the completion logic makes no claim to be an <acronym>SQL</acronym> parser. The queries generated by tab-completion - can also interfere with other SQL commands, e.g. <literal>SET + can also interfere with other SQL commands, e.g., <literal>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-9.6.sgml b/doc/src/sgml/release-9.6.sgml index 1b1ed23477a..487101144f6 100644 --- a/doc/src/sgml/release-9.6.sgml +++ b/doc/src/sgml/release-9.6.sgml @@ -6052,7 +6052,7 @@ Branch: REL9_4_STABLE [a683df403] 2019-02-05 10:59:38 -0500 <listitem> <para> Fix logical decoding to handle cases where a mapped catalog table is - repeatedly rewritten, e.g. by <literal>VACUUM FULL</literal> + repeatedly rewritten, e.g., by <literal>VACUUM FULL</literal> (Andres Freund) </para> </listitem> @@ -15094,7 +15094,7 @@ XXX this is pending backpatch, may need to remove </para> <para> - This change allows command tags, e.g. <command>SELECT</>, to + This change allows command tags, e.g., <command>SELECT</>, to correctly report tuple counts larger than 4 billion. This also applies to PL/pgSQL's <command>GET DIAGNOSTICS ... ROW_COUNT</> command. @@ -15418,7 +15418,7 @@ XXX this is pending backpatch, may need to remove --> <para> Allow omitting one or both boundaries in an array slice specifier, - e.g. <literal>array_col[3:]</> (Yury Zhuravlev) + e.g., <literal>array_col[3:]</> (Yury Zhuravlev) </para> <para> diff --git a/doc/src/sgml/replication-origins.sgml b/doc/src/sgml/replication-origins.sgml index 317ca9a1dfb..0883ca06d05 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 <type>text</type>. 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 <link linkend="view-pg-replication-origin-status"> <structname>pg_replication_origin_status</structname> - </link> view. An individual origin's progress, e.g. when resuming + </link> view. An individual origin's progress, e.g., when resuming replication, can be acquired using <link linkend="pg-replication-origin-progress"><function>pg_replication_origin_progress()</function></link> for any origin or @@ -86,7 +86,7 @@ output plugin callbacks (see <xref linkend="logicaldecoding-output-plugin">) 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 <link linkend="logicaldecoding-output-plugin-filter-origin"> <function>filter_by_origin_cb</function></link> 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 78ac5e8edea..327ccf0a2b5 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1977,7 +1977,7 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433 be migrated in-place from one major <productname>PostgreSQL</> version to another. Upgrades can be performed in minutes, particularly with <option>--link</> mode. It requires steps similar to - <application>pg_dumpall</> above, e.g. starting/stopping the server, + <application>pg_dumpall</> above, e.g., starting/stopping the server, running <application>initdb</>. The <application>pg_upgrade</> <link linkend="pgupgrade">documentation</> outlines the necessary steps. </para> diff --git a/doc/src/sgml/sepgsql.sgml b/doc/src/sgml/sepgsql.sgml index 0b611eeeca1..cc5fcabde62 100644 --- a/doc/src/sgml/sepgsql.sgml +++ b/doc/src/sgml/sepgsql.sgml @@ -527,7 +527,7 @@ UPDATE t1 SET x = 2, y = md5sum(y) WHERE z = 100; commands. <productname>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 9a6bd3ddf1b..a78eb789263 100644 --- a/doc/src/sgml/sources.sgml +++ b/doc/src/sgml/sources.sgml @@ -888,7 +888,7 @@ BETTER: unrecognized node type: 42 <para> Both, macros with arguments and <literal>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 <programlisting> #define Max(x, y) ((x) > (y) ? (x) : (y)) @@ -899,7 +899,7 @@ BETTER: unrecognized node type: 42 </para> <para> 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. <programlisting> diff --git a/doc/src/sgml/sslinfo.sgml b/doc/src/sgml/sslinfo.sgml index 9302e91da06..ee1ab83213b 100644 --- a/doc/src/sgml/sslinfo.sgml +++ b/doc/src/sgml/sslinfo.sgml @@ -47,7 +47,7 @@ </term> <listitem> <para> - Returns the name of the protocol used for the SSL connection (e.g. SSLv2, + Returns the name of the protocol used for the SSL connection (e.g., SSLv2, SSLv3, or TLSv1). </para> </listitem> @@ -63,7 +63,7 @@ <listitem> <para> Returns the name of the cipher used for the SSL connection - (e.g. DHE-RSA-AES256-SHA). + (e.g., DHE-RSA-AES256-SHA). </para> </listitem> </varlistentry> diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index c7028319e96..b714e53a2a4 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 <emphasis>data</emphasis> 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., <literal>data=writeback</> on a Linux ext3 file system. Journaled file systems do improve boot speed after a crash. </para> diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml index a1f177cd964..8eb454fdef2 100644 --- a/doc/src/sgml/xfunc.sgml +++ b/doc/src/sgml/xfunc.sgml @@ -116,9 +116,9 @@ Besides <command>SELECT</command> queries, the commands can include data modification queries (<command>INSERT</command>, <command>UPDATE</command>, and <command>DELETE</command>), 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., <command>COMMIT</>, <command>SAVEPOINT</>, and some utility - commands, e.g. <literal>VACUUM</>, in <acronym>SQL</acronym> functions.) + commands, e.g., <literal>VACUUM</>, in <acronym>SQL</acronym> functions.) However, the final command must be a <command>SELECT</command> or have a <literal>RETURNING</> clause that returns whatever is @@ -3402,7 +3402,7 @@ if (!ptr) exceptions. Any exceptions must be caught and appropriate errors passed back to the C interface. If possible, compile C++ with <option>-fno-exceptions</> 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 <function>new()</>. </para> </listitem> diff --git a/doc/src/sgml/xml2.sgml b/doc/src/sgml/xml2.sgml index c603914a23f..fd742840ae9 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 <command>SELECT</> statement doesn't necessarily have to be just <literal>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: <programlisting> SELECT t.title, p.fullname, p.email |