summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: e4263c4)
raw | patch | inline | side by side (parent: e4263c4)
| author | Bruce Momjian <bruce@momjian.us> | |
| Mon, 31 Aug 2020 22:33:37 +0000 (18:33 -0400) | ||
| committer | Bruce Momjian <bruce@momjian.us> | |
| Mon, 31 Aug 2020 22:33:37 +0000 (18:33 -0400) |
This follows the American format,
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.
Discussion: https://postgr.es/m/20200825183619.GA22369@momjian.us
Backpatch-through: 9.5
https://jakubmarian.com/comma-after-i-e-and-e-g/. There is no intention
of requiring this format for future text, but making existing text
consistent every few years makes sense.
Discussion: https://postgr.es/m/20200825183619.GA22369@momjian.us
Backpatch-through: 9.5
44 files changed:
index 19abd7fe65d55c52e1c86cd0f11724813f99a842..53bf6608e03f49852a2dff72a1fa43ad5e4a2979 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
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>
<para>
With this parameter enabled, you can still create ordinary global
users. Simply append <literal>@</literal> when specifying the user
- name in the client, e.g. <literal>joe@</literal>. The <literal>@</literal>
+ name in the client, e.g., <literal>joe@</literal>. The <literal>@</literal>
will be stripped off before the user name is looked up by the
server.
</para>
disabled, but the server continues to accumulate WAL segment files in
the expectation that a command will soon be provided. Setting
<varname>archive_command</varname> to a command that does nothing but
- return true, e.g. <literal>/bin/true</literal> (<literal>REM</literal> on
+ return true, e.g., <literal>/bin/true</literal> (<literal>REM</literal> 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 <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
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>
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>
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.
index eeefcda0dd38b66a08ea8924119ddeac88d1d914..0d38bee1820a23b724adde2e46d038a9495c8c5f 100644 (file)
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.
<row>
<entry><type>unknown</type></entry>
- <entry>Identifies a not-yet-resolved type, e.g. of an undecorated
+ <entry>Identifies a not-yet-resolved type, e.g., of an undecorated
string literal.</entry>
</row>
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 30cc3f6a0f7b7b9c2a3cecc160d58d82dfbdbd95..18155f1a4758d5327066ab1e1da6707a65bf2938 100644 (file)
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
</para>
<para>
- However, if the default value is volatile (e.g.
+ However, if the default value is volatile (e.g.,
<function>clock_timestamp()</function>)
each row will need to be updated with the value calculated at the time
<command>ALTER TABLE</command> is executed. To avoid a potentially
<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/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 03eb266d1255c297bf0113ef079e1c4c2b7388c9..b4e69664057885dc3f7fa770d41bca23419c2ee5 100644 (file)
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
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>
<term><literal>sqllen</literal></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>
<term><literal>FREE cursor_name</literal></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</literal> statement in ECPG. This is because in ECPG,
<literal>DECLARE CURSOR</literal> doesn't translate to a function call into
index 7dbe02a64ca651fad85acd756e5eac6953e8c4c3..5c28d5aeb0f3d2c902f32b904cc4cefc9218bf79 100644 (file)
--- a/doc/src/sgml/extend.sgml
+++ b/doc/src/sgml/extend.sgml
<para>
An extension is <firstterm>relocatable</firstterm> if it is possible to move
its contained objects into a different schema after initial creation
- of the extension. The default is <literal>false</literal>, i.e. the
+ of the extension. The default is <literal>false</literal>, i.e., the
extension is not relocatable.
See <xref linkend="extend-extensions-relocation"/> for more information.
</para>
<term><varname>NO_INSTALLCHECK</varname></term>
<listitem>
<para>
- don't define an <literal>installcheck</literal> target, useful e.g. if tests require special configuration, or don't use <application>pg_regress</application>
+ don't define an <literal>installcheck</literal> target, useful e.g., if tests require special configuration, or don't use <application>pg_regress</application>
</para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 8b9aab82d5599921eaa6142a99907e6e36a1304c..e049a24dfd5369277426e826d5931866149853c1 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
<listitem>
<para>
In <function>to_timestamp</function> and <function>to_date</function>,
- 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</literal>, 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</literal> becomes 1995.
</para>
</listitem>
@@ -9786,7 +9786,7 @@ CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple
<literal>"string"</literal> (to include all string values), <literal>"numeric"</literal> (to include all numeric values in the string format),
<literal>"boolean"</literal> (to include all Boolean values in the string format <literal>"true"</literal>/<literal>"false"</literal>),
<literal>"key"</literal> (to include all keys) or <literal>"all"</literal> (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.
</entry>
<entry><literal>json_to_tsvector('english', '{"a": "The Fat Rats", "b": 123}'::json, '["string", "numeric"]')</literal></entry>
<entry><literal>'123':5 'fat':2 'rat':3</literal></entry>
<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>
<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>
index 3403dcd9fb43a7dd96a95011103b130736f3a60f..ec5f5620ae5cc9dee171547e29923da496a03a23 100644 (file)
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
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>
<itemizedlist>
<listitem>
<para>
- Data Definition Language (DDL) - e.g. <command>CREATE INDEX</command>
+ Data Definition Language (DDL) - e.g., <command>CREATE INDEX</command>
</para>
</listitem>
<listitem>
<para>
WAL file control commands will not work during recovery,
- e.g. <function>pg_start_backup</function>, <function>pg_switch_wal</function> etc.
+ e.g., <function>pg_start_backup</function>, <function>pg_switch_wal</function> etc.
</para>
<para>
index d758a4987dc66af647b04a4837d17d2f48b1884b..40b9d78e0fe95cf5bf2f84f68751b0d74af88f77 100644 (file)
linkend="indexes-index-only-scans"><firstterm>index-only scans</firstterm></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</structfield> field in its <structname>IndexAmRoutine</structname>
struct can be set to NULL.
index 93241d993a09f6693065676a3cd4f8dc16427364..318c508276088850a7f7474543f981a7ed8489b8 100644 (file)
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
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>
index 3915098158fd59a824e75419d86b0c009394c561..c54b3340391bc496facf19c56f90318ad535ee5b 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
Conversely, if <function>PQconnectPoll(conn)</function> last returned
<symbol>PGRES_POLLING_WRITING</symbol>, wait until the socket is ready
to write, then call <function>PQconnectPoll(conn)</function> 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
<function>PQconnectPoll</function>, behave as if it last returned
<symbol>PGRES_POLLING_WRITING</symbol>. Continue this loop until
<function>PQconnectPoll(conn)</function> returns
<para>
Percent-encoding may be used to include symbols with special meaning in any
- of the <acronym>URI</acronym> parts, e.g. replace <literal>=</literal> with
+ of the <acronym>URI</acronym> parts, e.g., replace <literal>=</literal> with
<literal>%3D</literal>.
</para>
<literal>hostaddr</literal>, and <literal>port</literal> 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 <literal>hostaddr</literal> corresponds to the first host name,
+ that e.g., the first <literal>hostaddr</literal> corresponds to the first host name,
the second <literal>hostaddr</literal> corresponds to the second host name, and so
forth. As an exception, if only one <literal>port</literal> is specified, it
applies to all the hosts.
<para>
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.
</para>
</sect3>
<listitem>
<para>
Maximum wait for connection, in seconds (write as a decimal integer,
- e.g. <literal>10</literal>). Zero, negative, or not specified means
+ e.g., <literal>10</literal>). Zero, negative, or not specified means
wait indefinitely. The minimum allowed timeout is 2 seconds, therefore
a value of <literal>1</literal> is interpreted as <literal>2</literal>.
This timeout applies separately to each host name or IP address.
<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>
<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.
For a connection to be known secure, SSL usage must be configured
on <emphasis>both the client and the server</emphasis> 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</literal> parameter to <literal>verify-full</literal> or
index f63988865f9c8b0b742e2794689928f0ae75c36e..3293247534072d8942e125db2cb2aa618b5e816b 100644 (file)
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 34a3ae5a0bf2b9e8292c7163132c939e31dd37c8..b64f79c49e3fc18fcc92a4393084f34f595c1915 100644 (file)
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
<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.
index 6c30916655d70b95c05a4a6dd0c3a3720081f7aa..891586f83d4dc0971913a15e6d16f7d3e6691ef5 100644 (file)
<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
<para>
Functions and aggregates must be marked <literal>PARALLEL UNSAFE</literal> 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</literal> block to catch errors), or make persistent changes to
settings. Similarly, functions must be marked <literal>PARALLEL
RESTRICTED</literal> if they access temporary tables, client connection state,
index 992486eabeab88c020a88f3ef89734534a284ec4..f1a322d0788eaa307f6f2248bec491441a88891e 100644 (file)
<listitem>
<para>
Place the database cluster's data directory in a memory-backed
- file system (i.e. <acronym>RAM</acronym> disk). This eliminates all
+ file system (i.e., <acronym>RAM</acronym> disk). This eliminates all
database disk I/O, but limits data storage to the amount of
available memory (and perhaps swap).
</para>
index 30e6a0ab20afba695010aceaa994fbab6480782e..d6f111e28f76bb0a26684e2a3d9042640f96183d 100644 (file)
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
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>
index 88bc1896468e3e00a3377f0c4833eaf91347ee2e..90ad45a12e3c97de687f9598e55a559c8dba56be 100644 (file)
( )
)
</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>
<programlisting>
CUBE ( <replaceable>e1</replaceable>, <replaceable>e2</replaceable>, ... )
</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 )
index 92825fdf1920e64d801889cc9c47271962cedc9d..d139fa28eb9c26a13c548058a8ed0be83167a584 100644 (file)
<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>
index a3b2e98b467da73dcc54bd7a340d7da4484ebed7..88e93ea2a15bf2399f19c9891a9f4617629015ff 100644 (file)
<listitem>
<para>
Collation order (<literal>LC_COLLATE</literal>) 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.
<listitem>
<para>
Character classification (<literal>LC_CTYPE</literal>) 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 52ba746166be3d907f14901491b63a4001ac817a..becd31bcadf7c1362bd4e0c0804b26df323712e9 100644 (file)
A list of values for the
associated <replaceable class="parameter">filter_variable</replaceable>
for which the trigger should fire. For <literal>TAG</literal>, this means a
- list of command tags (e.g. <literal>'DROP FUNCTION'</literal>).
+ list of command tags (e.g., <literal>'DROP FUNCTION'</literal>).
</para>
</listitem>
</varlistentry>
index 7b16aff72154f307286567489f869711959a2bc0..831529db17f17ab009310896cec83458037834eb 100644 (file)
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>
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</literal>). They should
+ persistent changes to settings (e.g., <literal>setval</literal>). 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</literal> cannot be executed other than by the group
+ (e.g., <literal>setseed</literal> 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
index 0ea6513cb588ed9f19aace6476d4da445cf82636..d225695626cbf173a92b8acfc2b4127972676587 100644 (file)
The name of the language that the procedure 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>
index 539f5bded5469353913b795a42244a5e964e49cc..f5367cfcc67ad19157fc08d248d7403fcd999c5a 100644 (file)
@@ -129,7 +129,7 @@ CREATE STATISTICS [ IF NOT EXISTS ] <replaceable class="parameter">statistics_na
<title>Examples</title>
<para>
- Create table <structname>t1</structname> with two functionally dependent columns, i.e.
+ Create table <structname>t1</structname> 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:
index b9e178834b0d08f3216ffdba58ce888296e9cb45..2b9848b68061fab1709265a14b0b7cb61b5b8f67 100644 (file)
@@ -813,7 +813,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, 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. <literal>DROP COLUMN</literal>) can cause cascaded constraint and
+ (e.g., <literal>DROP COLUMN</literal>) can cause cascaded constraint and
index deletion.
</para>
</listitem>
@@ -859,7 +859,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, 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. <literal>DROP COLUMN</literal>) can cause cascaded
+ included columns (e.g., <literal>DROP COLUMN</literal>) can cause cascaded
constraint and index deletion.
</para>
</listitem>
index 1f0a9791ed4e5dfc9a88f92607e9feb6403bf051..86cd167635f32589f20cfcb376d02feb61666016 100644 (file)
@@ -357,7 +357,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</quote>
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.
index 84fb37c293a3a93fd321b019cd6f31075be38c36..a37311d55383ffde8fb1618cc4bff7e4d52effcf 100644 (file)
<command>initdb</command> initializes the database cluster's default
locale and character set encoding. The character set encoding,
collation order (<literal>LC_COLLATE</literal>) and character set classes
- (<literal>LC_CTYPE</literal>, e.g. upper, lower, digit) can be set separately
+ (<literal>LC_CTYPE</literal>, 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.
index 13d15c27dc3de3a04ea1cfe1ff800a321ab4bd52..3c76aad36066c99e4fa77dc1a0b2f2ec28832df9 100644 (file)
<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</option> is also specified.
</para>
index b1562e6ceebd838d25d80ec315705cab6f30379a..af0a02bc12958321fcd0564f7d240a0691bb8ec9 100644 (file)
<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 drop databases and other objects. This option is not valid
unless <option>--clean</option> is also specified.
</para>
index 800d635336d0222432ae9003390367a1fdc23297..e03450362a5d5c960bbe210746f8b92ace167c49 100644 (file)
<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 drop database objects. This option is not valid
unless <option>--clean</option> is also specified.
</para>
index 670371e0dfccd0876877a6b156fb0ae69be79188..3cd6fc9464f7b37e8a9422d6a198d67f53a69329 100644 (file)
files might no longer be present. In that case, they can be manually
copied from the WAL archive to the <filename>pg_wal</filename> directory, or
fetched on startup by configuring <filename>recovery.conf</filename>. The use of
- <application>pg_rewind</application> is not limited to failover, e.g. a standby
+ <application>pg_rewind</application> 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>
index 2df606d83e48047144bd063fed8f812036fd1696..b7463177d15bd6a0137012ab0a5b8ff7e5c55061 100644 (file)
@@ -561,7 +561,7 @@ pgbench <optional> <replaceable>options</replaceable> </optional> <replaceable>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.
</para>
@@ -711,7 +711,7 @@ pgbench <optional> <replaceable>options</replaceable> </optional> <replaceable>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 <optional> <replaceable>options</replaceable> </optional> <replaceable>d
<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>
<literal>2.0 / parameter</literal>, that is a relative
<literal>1.0 / parameter</literal> around the mean; for instance, if
<replaceable>parameter</replaceable> 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</literal> to <literal>5.0 / 8.0</literal>) and 95% from
the middle half (<literal>2.0 / 4.0</literal>) of the interval (second and third
quartiles). The minimum <replaceable>parameter</replaceable> is 2.0 for performance
and <replaceable>max_lag</replaceable>, are only present if the <option>--rate</option>
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, <replaceable>skipped</replaceable>,
is only present if the <option>--latency-limit</option> option is used, too.
index e3f5c5c750d2b1a59e615d04fe3e86db554423a1..f711cb5297be04e10977885ddebdb55d6b344796 100644 (file)
<application>pg_upgrade</application> (formerly called <application>pg_migrator</application>) allows data
stored in <productname>PostgreSQL</productname> data files to be upgraded to a later <productname>PostgreSQL</productname>
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.
</para>
<para>
<application>pg_upgrade</application> 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
<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/&majorversion;</filename>, 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</filename>, it is necessary to move the current PostgreSQL install
directory so it does not interfere with the new <productname>PostgreSQL</productname> installation.
Once the current <productname>PostgreSQL</productname> server is shut down, it is safe to rename the
<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</command>, because these will be upgraded
from the old cluster.
Also, any custom full text search files (dictionary, synonym,
<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</application> 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 \
<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>, <filename>share</filename>).
+ (e.g., <filename>bin</filename>, <filename>share</filename>).
</para>
</step>
If you are upgrading a pre-<productname>PostgreSQL</productname> 9.2 cluster
that uses a configuration-file-only directory, you must pass the
real data directory location to <application>pg_upgrade</application>, 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'</literal>.
</para>
copy with any changes to make it consistent. (<option>--checksum</option>
is necessary because <command>rsync</command> only has file modification-time
granularity of one second.) You might want to exclude some
- files, e.g. <filename>postmaster.pid</filename>, as documented in <xref
+ files, e.g., <filename>postmaster.pid</filename>, 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
index 53dc05a78f06e3693c86fbc7caccddeee10b5891..2a0d4fce5102e226beb4d13f6bb2376ea8681941 100644 (file)
<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>
index 3d799b5b5793a7f1ab51e1caf4d461f72102a0b5..86ce607792cbed90044e92a96a9965f2b5fee569 100644 (file)
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</command>.
If a generic plan is in use, it will contain parameter symbols
<literal>$<replaceable>n</replaceable></literal>, while a custom plan will have the
index d76ed41149b4aa245fb2a5da2beb075dcaec3380..4d695c901880706fcda1db449090defe50e7f3a1 100644 (file)
<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.
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'</literal>. Unspecified output columns
+ e.g., <literal>'0.2 0.2 0.6'</literal>. Unspecified output columns
use the last specified value.
</para>
</listitem>
<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</literal>.
If for some reason you do not like the tab completion, you
can turn it off by putting this in a file named
index bb66ef07dc95bf80bffe9a8f2a4b0451a59da5c6..bd85114f3dc9aa5e816eb04bde7ad5c73b175a40 100644 (file)
-->
<para>
- Allow single-evaluation queries, e.g. <literal>WHERE</literal>
+ Allow single-evaluation queries, e.g., <literal>WHERE</literal>
clause aggregate queries, and functions in the target list to be
parallelized (Amit Kapila, Robert Haas)
</para>
<para>
<productname>PostgreSQL</productname> only allows superusers to
access <filename>postgres_fdw</filename> tables without
- passwords, e.g. via <literal>peer</literal>. Previously, the
+ passwords, e.g., via <literal>peer</literal>. Previously, the
session owner had to be a superuser to allow such access; now
the view owner is checked instead.
</para>
-->
<para>
- 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)
</para>
<acronym>SCRAM</acronym> 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.
</para>
</listitem>
index a03ce76e2ef36c1369bb94a4af0c64ce5c00fae3..7e02c4605b25f33a843f77290c2b08333e957777 100644 (file)
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.
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
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
index a73e9d78e3e7d89eff7d02927ce7b9ea05438331..b3875d6e21be14b4d9d24afe78d70e421c2105ed 100644 (file)
be migrated in-place from one major <productname>PostgreSQL</productname>
version to another. Upgrades can be performed in minutes,
particularly with <option>--link</option> mode. It requires steps similar to
- <application>pg_dumpall</application> above, e.g. starting/stopping the server,
+ <application>pg_dumpall</application> above, e.g., starting/stopping the server,
running <application>initdb</application>. The <application>pg_upgrade</application> <link
linkend="pgupgrade">documentation</link> outlines the necessary steps.
</para>
index f8c99e1b002501243ef0840b52f88c228668bba8..64cde0adb56d0dd6873193f6135bb4aeb475114c 100644 (file)
commands. <productname>SELinux</productname> 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:
index 1a3d905ab7ef94b6c8be7c86657f76641460c5f7..f1e5bf291c54a76e024abf44b4931ec76c270e4f 100644 (file)
<para>
Both, macros with arguments and <literal>static inline</literal>
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))
</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>
index 45d1136ac9ab14fc4eccf1c6d46070ab294280d8..74aaf1b2af3b41cb935a267849b702a10aee36a9 100644 (file)
</term>
<listitem>
<para>
- 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).
</para>
</listitem>
<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>
index 13feb1fc3b680d07a4c38346edd86af1c8c51e89..9c889feb6b87ccd6919c8907d71522d4637f099b 100644 (file)
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 <link
+ servers and collecting external search results, e.g., via <link
linkend="ddl-foreign-data">Foreign Data</link> 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 bd9fae544c1dfb7bd8ca0a1d97ee7226197952d7..a94edf4d8b6279cafbd5c2429947a2764f1e36c5 100644 (file)
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
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</literal> on a Linux ext3 file system.
Journaled file systems do improve boot speed after a crash.
</para>
index ea72622c47fd1979c2a001d03f34c99ce40c8256..4b0d2ff12be2e478a02f0b925e9f932b2a5f2bb8 100644 (file)
--- a/doc/src/sgml/xfunc.sgml
+++ b/doc/src/sgml/xfunc.sgml
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>, <command>SAVEPOINT</command>, and some utility
- commands, e.g. <literal>VACUUM</literal>, in <acronym>SQL</acronym> functions.)
+ commands, e.g., <literal>VACUUM</literal>, in <acronym>SQL</acronym> functions.)
However, the final command
must be a <command>SELECT</command> or have a <literal>RETURNING</literal>
clause that returns whatever is
exceptions. Any exceptions must be caught and appropriate errors
passed back to the C interface. If possible, compile C++ with
<option>-fno-exceptions</option> 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()</function>.
</para>
</listitem>
diff --git a/doc/src/sgml/xml2.sgml b/doc/src/sgml/xml2.sgml
index 560faa000ecdc1bd89d2f9899fd73cffc7416b55..f5346336104ab50cad68d4972e7a15135d6728dc 100644 (file)
--- a/doc/src/sgml/xml2.sgml
+++ b/doc/src/sgml/xml2.sgml
The calling <command>SELECT</command> statement doesn't necessarily have to be
just <literal>SELECT *</literal> — 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