Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 5394b87

Browse filesBrowse files
bmomjianbmomjian
committed
doc: add commas after 'i.e.' and 'e.g.'
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
1 parent 160c8a4 commit 5394b87
Copy full SHA for 5394b87

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Dismiss banner
Expand file treeCollapse file tree

41 files changed

+93
-93
lines changed

‎doc/src/sgml/config.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/config.sgml
+6-6Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -407,7 +407,7 @@ include_dir 'directory'
407407
start with the <literal>.</literal> character are also ignored, to
408408
prevent mistakes since such files are hidden on some platforms. Multiple
409409
files within an include directory are processed in file name order
410-
(according to C locale rules, i.e. numbers before letters, and
410+
(according to C locale rules, i.e., numbers before letters, and
411411
uppercase letters before lowercase ones).
412412
</para>
413413

@@ -1259,7 +1259,7 @@ include_dir 'conf.d'
12591259
<para>
12601260
With this parameter enabled, you can still create ordinary global
12611261
users. Simply append <literal>@</> when specifying the user
1262-
name in the client, e.g. <literal>joe@</>. The <literal>@</>
1262+
name in the client, e.g., <literal>joe@</>. The <literal>@</>
12631263
will be stripped off before the user name is looked up by the
12641264
server.
12651265
</para>
@@ -2820,7 +2820,7 @@ include_dir 'conf.d'
28202820
disabled, but the server continues to accumulate WAL segment files in
28212821
the expectation that a command will soon be provided. Setting
28222822
<varname>archive_command</> to a command that does nothing but
2823-
return true, e.g. <literal>/bin/true</> (<literal>REM</> on
2823+
return true, e.g., <literal>/bin/true</> (<literal>REM</> on
28242824
Windows), effectively disables
28252825
archiving, but also breaks the chain of WAL files needed for
28262826
archive recovery, so it should only be used in unusual circumstances.
@@ -3652,7 +3652,7 @@ include_dir 'conf.d'
36523652
if your data is likely to be completely in cache, such as when
36533653
the database is smaller than the total server memory, decreasing
36543654
random_page_cost can be appropriate. Storage that has a low random
3655-
read cost relative to sequential, e.g. solid-state drives, might
3655+
read cost relative to sequential, e.g., solid-state drives, might
36563656
also be better modeled with a lower value for random_page_cost,
36573657
e.g., <literal>1.1</literal>.
36583658
</para>
@@ -7134,7 +7134,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
71347134
rows that can be locked; that value is unlimited. The default,
71357135
64, has historically proven sufficient, but you might need to
71367136
raise this value if you have queries that touch many different
7137-
tables in a single transaction, e.g. query of a parent table with
7137+
tables in a single transaction, e.g., query of a parent table with
71387138
many children. This parameter can only be set at server start.
71397139
</para>
71407140

@@ -7639,7 +7639,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
76397639
with assertions enabled. That is the case if the
76407640
macro <symbol>USE_ASSERT_CHECKING</symbol> is defined
76417641
when <productname>PostgreSQL</productname> is built (accomplished
7642-
e.g. by the <command>configure</command> option
7642+
e.g., by the <command>configure</command> option
76437643
<option>--enable-cassert</option>). By
76447644
default <productname>PostgreSQL</productname> is built without
76457645
assertions.

‎doc/src/sgml/datatype.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/datatype.sgml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -501,7 +501,7 @@
501501
very large number of digits. It is especially recommended for
502502
storing monetary amounts and other quantities where exactness is
503503
required. Calculations with <type>numeric</type> values yield exact
504-
results where possible, e.g. addition, subtraction, multiplication.
504+
results where possible, e.g., addition, subtraction, multiplication.
505505
However, calculations on <type>numeric</type> values are very slow
506506
compared to the integer types, or to the floating-point types
507507
described in the next section.

‎doc/src/sgml/ddl.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/ddl.sgml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1510,7 +1510,7 @@ ALTER TABLE products RENAME TO items;
15101510

15111511
<para>
15121512
An object can be assigned to a new owner with an <command>ALTER</command>
1513-
command of the appropriate kind for the object, e.g. <xref
1513+
command of the appropriate kind for the object, e.g., <xref
15141514
linkend="sql-altertable">. Superusers can always do
15151515
this; ordinary roles can only do it if they are both the current owner
15161516
of the object (or a member of the owning role) and a member of the new

‎doc/src/sgml/docguide.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/docguide.sgml
+4-4Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -692,16 +692,16 @@ save_size.pdfjadetex = 15000
692692

693693
<para>
694694
Occasionally text is too wide for the printed margins, and in
695-
extreme cases, too wide for the printed page, e.g. non-wrapped
695+
extreme cases, too wide for the printed page, e.g., non-wrapped
696696
text, wide tables. Overly wide text generates <quote>Overfull
697-
hbox</quote> messages in the TeX log output file, e.g.
697+
hbox</quote> messages in the TeX log output file, e.g.,
698698
<filename>postgres-US.log</> or <filename>postgres-A4.log</>.
699699
There are 72 points in an inch so anything reported as over 72
700700
points too wide will probably not fit on the printed page (assuming
701701
one inch margins). To find the <acronym>SGML</acronym> text
702702
causing the overflow, find the first page number mentioned above
703-
the overflow message, e.g. <literal>[50 ###]</> (page 50), and
704-
look at the page after that (e.g. page 51) in the <acronym>PDF</acronym>
703+
the overflow message, e.g., <literal>[50 ###]</> (page 50), and
704+
look at the page after that (e.g., page 51) in the <acronym>PDF</acronym>
705705
file to see the overflow text and adjust the <acronym>SGML</acronym>
706706
accordingly.
707707
</para>

‎doc/src/sgml/ecpg.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/ecpg.sgml
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3627,7 +3627,7 @@ EXEC SQL DEALLOCATE DESCRIPTOR <replaceable>identifier</replaceable>;
36273627
EXEC SQL FETCH NEXT FROM mycursor INTO SQL DESCRIPTOR mydesc;
36283628
</programlisting>
36293629
If the result set is empty, the Descriptor Area will still contain
3630-
the metadata from the query, i.e. the field names.
3630+
the metadata from the query, i.e., the field names.
36313631
</para>
36323632

36333633
<para>
@@ -4044,7 +4044,7 @@ typedef struct sqlvar_struct sqlvar_t;
40444044
<term><literal>sqllen</></term>
40454045
<listitem>
40464046
<para>
4047-
Contains the binary length of the field. e.g. 4 bytes for <type>ECPGt_int</type>.
4047+
Contains the binary length of the field. e.g., 4 bytes for <type>ECPGt_int</type>.
40484048
</para>
40494049
</listitem>
40504050
</varlistentry>
@@ -7971,7 +7971,7 @@ EXEC SQL CLOSE DATABASE;
79717971
<term><literal>FREE cursor_name</></term>
79727972
<listitem>
79737973
<para>
7974-
Due to the differences how ECPG works compared to Informix's ESQL/C (i.e. which steps
7974+
Due to the differences how ECPG works compared to Informix's ESQL/C (i.e., which steps
79757975
are purely grammar transformations and which steps rely on the underlying run-time library)
79767976
there is no <literal>FREE cursor_name</> statement in ECPG. This is because in ECPG,
79777977
<literal>DECLARE CURSOR</literal> doesn't translate to a function call into

‎doc/src/sgml/extend.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/extend.sgml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -533,7 +533,7 @@
533533
<para>
534534
An extension is <firstterm>relocatable</> if it is possible to move
535535
its contained objects into a different schema after initial creation
536-
of the extension. The default is <literal>false</>, i.e. the
536+
of the extension. The default is <literal>false</>, i.e., the
537537
extension is not relocatable.
538538
See <xref linkend="extend-extensions-relocation"> for more information.
539539
</para>

‎doc/src/sgml/func.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/func.sgml
+6-6Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6151,7 +6151,7 @@ SELECT regexp_matches('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
61516151
will be replaced by the year data, but the single <literal>Y</literal> in <literal>Year</literal>
61526152
will not be. In <function>to_date</>, <function>to_number</>,
61536153
and <function>to_timestamp</>, double-quoted strings skip the number of
6154-
input characters contained in the string, e.g. <literal>"XX"</>
6154+
input characters contained in the string, e.g., <literal>"XX"</>
61556155
skips two input characters.
61566156
</para>
61576157
</listitem>
@@ -6166,9 +6166,9 @@ SELECT regexp_matches('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
61666166

61676167
<listitem>
61686168
<para>
6169-
If the year format specification is less than four digits, e.g.
6169+
If the year format specification is less than four digits, e.g.,
61706170
<literal>YYY</>, and the supplied year is less than four digits,
6171-
the year will be adjusted to be nearest to the year 2020, e.g.
6171+
the year will be adjusted to be nearest to the year 2020, e.g.,
61726172
<literal>95</> becomes 1995.
61736173
</para>
61746174
</listitem>
@@ -6281,7 +6281,7 @@ SELECT regexp_matches('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
62816281
<listitem>
62826282
<para>
62836283
<function>to_char(interval)</function> formats <literal>HH</> and
6284-
<literal>HH12</> as shown on a 12-hour clock, i.e. zero hours
6284+
<literal>HH12</> as shown on a 12-hour clock, i.e., zero hours
62856285
and 36 hours output as <literal>12</>, while <literal>HH24</>
62866286
outputs the full hour value, which can exceed 23 for intervals.
62876287
</para>
@@ -19849,7 +19849,7 @@ FOR EACH ROW EXECUTE PROCEDURE suppress_redundant_updates_trigger();
1984919849
<row>
1985019850
<entry><literal>objsubid</literal></entry>
1985119851
<entry><type>integer</type></entry>
19852-
<entry>Sub-object ID (e.g. attribute number for a column)</entry>
19852+
<entry>Sub-object ID (e.g., attribute number for a column)</entry>
1985319853
</row>
1985419854
<row>
1985519855
<entry><literal>command_tag</literal></entry>
@@ -19936,7 +19936,7 @@ FOR EACH ROW EXECUTE PROCEDURE suppress_redundant_updates_trigger();
1993619936
<row>
1993719937
<entry><literal>objsubid</literal></entry>
1993819938
<entry><type>integer</type></entry>
19939-
<entry>Sub-object ID (e.g. attribute number for a column)</entry>
19939+
<entry>Sub-object ID (e.g., attribute number for a column)</entry>
1994019940
</row>
1994119941
<row>
1994219942
<entry><literal>original</literal></entry>

‎doc/src/sgml/high-availability.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/high-availability.sgml
+4-4Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,7 @@ protocol to make nodes agree on a serializable transactional order.
201201
this is unacceptable, either the middleware or the application
202202
must query such values from a single server and then use those
203203
values in write queries. Another option is to use this replication
204-
option with a traditional master-standby setup, i.e. data modification
204+
option with a traditional master-standby setup, i.e., data modification
205205
queries are sent only to the master and are propagated to the
206206
standby servers via master-standby replication, not by the replication
207207
middleware. Care must also be taken that all
@@ -628,7 +628,7 @@ protocol to make nodes agree on a serializable transactional order.
628628
Set up continuous archiving on the primary to an archive directory
629629
accessible from the standby, as described
630630
in <xref linkend="continuous-archiving">. The archive location should be
631-
accessible from the standby even when the master is down, i.e. it should
631+
accessible from the standby even when the master is down, i.e., it should
632632
reside on the standby server itself or another trusted server, not on
633633
the master server.
634634
</para>
@@ -2131,7 +2131,7 @@ LOG: database system is ready to accept read only connections
21312131
<itemizedlist>
21322132
<listitem>
21332133
<para>
2134-
Data Definition Language (DDL) - e.g. <command>CREATE INDEX</>
2134+
Data Definition Language (DDL) - e.g., <command>CREATE INDEX</>
21352135
</para>
21362136
</listitem>
21372137
<listitem>
@@ -2197,7 +2197,7 @@ LOG: database system is ready to accept read only connections
21972197

21982198
<para>
21992199
WAL file control commands will not work during recovery,
2200-
e.g. <function>pg_start_backup</>, <function>pg_switch_xlog</> etc.
2200+
e.g., <function>pg_start_backup</>, <function>pg_switch_xlog</> etc.
22012201
</para>
22022202

22032203
<para>

‎doc/src/sgml/indexam.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/indexam.sgml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -352,7 +352,7 @@ amcanreturn (Relation indexRelation, int attno);
352352
linkend="indexes-index-only-scans"><firstterm>index-only scans</></link> on
353353
the given column, by returning the indexed column values for an index entry
354354
in the form of an <structname>IndexTuple</structname>. The attribute number
355-
is 1-based, i.e. the first column's attno is 1. Returns TRUE if supported,
355+
is 1-based, i.e., the first column's attno is 1. Returns TRUE if supported,
356356
else FALSE. If the access method does not support index-only scans at all,
357357
the <structfield>amcanreturn</> field in its <structname>IndexAmRoutine</>
358358
struct can be set to NULL.

‎doc/src/sgml/install-windows.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/install-windows.sgml
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@
116116
In the <productname>Microsoft Windows SDK</productname>, start the
117117
<application>CMD shell</application> listed under the SDK on the Start Menu.
118118
In recent SDK versions you can change the targeted CPU architecture, build
119-
type, and target OS by using the <command>setenv</command> command, e.g.
119+
type, and target OS by using the <command>setenv</command> command, e.g.,
120120
<command>setenv /x86 /release /xp</command> to target Windows XP or later
121121
with a 32-bit release build. See <command>/?</command> for other options to
122122
<command>setenv</command>. All commands should be run from the
@@ -241,7 +241,7 @@ $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';
241241
installations <filename>C:\Program Files\GnuWin32</filename>.
242242
Consider installing into <filename>C:\GnuWin32</filename> or use the
243243
NTFS short name path to GnuWin32 in your PATH environment setting
244-
(e.g. <filename>C:\PROGRA~1\GnuWin32</filename>).
244+
(e.g., <filename>C:\PROGRA~1\GnuWin32</filename>).
245245
</para>
246246
</note>
247247

‎doc/src/sgml/libpq.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/libpq.sgml
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1949,7 +1949,7 @@ const char *PQsslAttribute(const PGconn *conn, const char *attribute_name);
19491949
<term><literal>cipher</literal></term>
19501950
<listitem>
19511951
<para>
1952-
A short name of the ciphersuite used, e.g.
1952+
A short name of the ciphersuite used, e.g.,
19531953
<literal>"DHE-RSA-DES-CBC3-SHA"</literal>. The names are specific
19541954
to each SSL implementation.
19551955
</para>
@@ -4596,7 +4596,7 @@ int PQflush(PGconn *conn);
45964596
<function>PQflush</function> again. Repeat until
45974597
<function>PQflush</function> returns 0. (It is necessary to check for
45984598
read-ready and drain the input with <function>PQconsumeInput</function>,
4599-
because the server can block trying to send us data, e.g. NOTICE
4599+
because the server can block trying to send us data, e.g., NOTICE
46004600
messages, and won't read our data until we read its.) Once
46014601
<function>PQflush</function> returns 0, wait for the socket to be
46024602
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=*)
75257525
For a connection to be known secure, SSL usage must be configured
75267526
on <emphasis>both the client and the server</> before the connection
75277527
is made. If it is only configured on the server, the client may end up
7528-
sending sensitive information (e.g. passwords) before
7528+
sending sensitive information (e.g., passwords) before
75297529
it knows that the server requires high security. In libpq, secure
75307530
connections can be ensured
75317531
by setting the <literal>sslmode</> parameter to <literal>verify-full</> or

‎doc/src/sgml/monitoring.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/monitoring.sgml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
206206
When the server shuts down cleanly, a permanent copy of the statistics
207207
data is stored in the <filename>pg_stat</filename> subdirectory, so that
208208
statistics can be retained across server restarts. When recovery is
209-
performed at server start (e.g. after immediate shutdown, server crash,
209+
performed at server start (e.g., after immediate shutdown, server crash,
210210
and point-in-time recovery), all statistics counters are reset.
211211
</para>
212212

‎doc/src/sgml/mvcc.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/mvcc.sgml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -269,7 +269,7 @@
269269
<para>
270270
In <productname>PostgreSQL</productname>, you can request any of
271271
the four standard transaction isolation levels, but internally only
272-
three distinct isolation levels are implemented, i.e. PostgreSQL's
272+
three distinct isolation levels are implemented, i.e., PostgreSQL's
273273
Read Uncommitted mode behaves like Read Committed. This is because
274274
it is the only sensible way to map the standard isolation levels to
275275
PostgreSQL's multiversion concurrency control architecture.

‎doc/src/sgml/parallel.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/parallel.sgml
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -336,7 +336,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
336336
<xref linkend="guc-parallel-tuple-cost">. Of course, this plan may turn
337337
out to be slower than the serial plan which the planner preferred, but
338338
this will not always be the case. If you don't get a parallel
339-
plan even with very small values of these settings (e.g. after setting
339+
plan even with very small values of these settings (e.g., after setting
340340
them both to zero), there may be some reason why the query planner is
341341
unable to generate a parallel plan for your query. See
342342
<xref linkend="when-can-parallel-query-be-used"> and
@@ -428,7 +428,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
428428
<para>
429429
Functions and aggregates must be marked <literal>PARALLEL UNSAFE</> if
430430
they write to the database, access sequences, change the transaction state
431-
even temporarily (e.g. a PL/pgsql function which establishes an
431+
even temporarily (e.g., a PL/pgsql function which establishes an
432432
<literal>EXCEPTION</> block to catch errors), or make persistent changes to
433433
settings. Similarly, functions must be marked <literal>PARALLEL
434434
RESTRICTED</> if they access temporary tables, client connection state,

‎doc/src/sgml/perform.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/perform.sgml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1578,7 +1578,7 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
15781578
<listitem>
15791579
<para>
15801580
Place the database cluster's data directory in a memory-backed
1581-
file system (i.e. <acronym>RAM</> disk). This eliminates all
1581+
file system (i.e., <acronym>RAM</> disk). This eliminates all
15821582
database disk I/O, but limits data storage to the amount of
15831583
available memory (and perhaps swap).
15841584
</para>

‎doc/src/sgml/protocol.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/protocol.sgml
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@
2828
the server, the connection will be rejected (for example, this would occur
2929
if the client requested protocol version 4.0, which does not exist as of
3030
this writing). If the minor version requested by the client is not
31-
supported by the server (e.g. the client requests version 3.1, but the
31+
supported by the server (e.g., the client requests version 3.1, but the
3232
server supports only 3.0), the server may either reject the connection or
3333
may respond with a NegotiateProtocolVersion message containing the highest
3434
minor protocol version which it supports. The client may then choose either
@@ -382,7 +382,7 @@
382382
by the client, but does support an earlier version of the protocol;
383383
this message indicates the highest supported minor version. This
384384
message will also be sent if the client requested unsupported protocol
385-
options (i.e. beginning with <literal>_pq_.</literal>) in the
385+
options (i.e., beginning with <literal>_pq_.</literal>) in the
386386
startup packet. This message will be followed by an ErrorResponse or
387387
a message indicating the success or failure of authentication.
388388
</para>

‎doc/src/sgml/queries.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/queries.sgml
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1258,7 +1258,7 @@ GROUPING SETS (
12581258
( )
12591259
)
12601260
</programlisting>
1261-
This is commonly used for analysis over hierarchical data; e.g. total
1261+
This is commonly used for analysis over hierarchical data; e.g., total
12621262
salary by department, division, and company-wide total.
12631263
</para>
12641264

@@ -1267,7 +1267,7 @@ GROUPING SETS (
12671267
<programlisting>
12681268
CUBE ( <replaceable>e1</>, <replaceable>e2</>, ... )
12691269
</programlisting>
1270-
represents the given list and all of its possible subsets (i.e. the power
1270+
represents the given list and all of its possible subsets (i.e., the power
12711271
set). Thus
12721272
<programlisting>
12731273
CUBE ( a, b, c )

‎doc/src/sgml/recovery-config.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/recovery-config.sgml
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
172172
<listitem>
173173
<para>
174174
This parameter specifies that recovery should end as soon as a
175-
consistent state is reached, i.e. as early as possible. When restoring
175+
consistent state is reached, i.e., as early as possible. When restoring
176176
from an online backup, this means the point where taking the backup
177177
ended.
178178
</para>

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.