Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 4ad6f13

Browse files
committed
Copyedit comments and documentation.
1 parent f07d18b commit 4ad6f13

File tree

17 files changed

+25
-25
lines changed

17 files changed

+25
-25
lines changed

config/c-compiler.m4

+1-1
Original file line numberDiff line numberDiff line change
@@ -335,7 +335,7 @@ if test x"$Ac_cachevar" = x"yes"; then
335335
$1="${$1} $2"
336336
fi
337337
undefine([Ac_cachevar])dnl
338-
])# PGAC_PROG_CC_CFLAGS_OPT
338+
])# PGAC_PROG_CC_VAR_OPT
339339

340340

341341

contrib/pgstattuple/pgstatapprox.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
/*-------------------------------------------------------------------------
22
*
3-
* pgstatapproc.c
3+
* pgstatapprox.c
44
* Bloat estimation functions
55
*
66
* Copyright (c) 2014-2016, PostgreSQL Global Development Group

doc/src/sgml/install-windows.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -457,7 +457,7 @@ $ENV{CONFIG}="Debug";
457457
<para>
458458
Running the regression tests on client programs, with
459459
<command>vcregress bincheck</>, or on recovery tests, with
460-
<command>vcregress recoverycheck</> requires an additional Perl module
460+
<command>vcregress recoverycheck</>, requires an additional Perl module
461461
to be installed:
462462
<variablelist>
463463
<varlistentry>

doc/src/sgml/release-9.3.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -9689,7 +9689,7 @@ ALTER EXTENSION hstore UPDATE;
96899689

96909690
<listitem>
96919691
<para>
9692-
Remove <filename>src/tool/backend</>, now that the content is on
9692+
Remove <filename>src/tools/backend</>, now that the content is on
96939693
the <productname>PostgreSQL</> wiki (Bruce Momjian)
96949694
</para>
96959695
</listitem>

doc/src/sgml/xml2.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -324,7 +324,7 @@ AS t(article_id integer, author text, page_count integer, title text);
324324
</para>
325325

326326
<para>
327-
The calling <command>SELECT</> statement doesn't necessarily have be
327+
The calling <command>SELECT</> statement doesn't necessarily have to be
328328
just <literal>SELECT *</> &mdash; it can reference the output
329329
columns by name or join them to other tables. The function produces a
330330
virtual table with which you can perform any operation you wish (e.g.

src/backend/executor/execParallel.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ typedef struct ExecParallelEstimateContext
7171
int nnodes;
7272
} ExecParallelEstimateContext;
7373

74-
/* Context object for ExecParallelEstimate. */
74+
/* Context object for ExecParallelInitializeDSM. */
7575
typedef struct ExecParallelInitializeDSMContext
7676
{
7777
ParallelContext *pcxt;

src/backend/storage/buffer/README

+6-6
Original file line numberDiff line numberDiff line change
@@ -89,12 +89,12 @@ then returns false, while LockBufferForCleanup() releases the exclusive lock
8989
(but not the caller's pin) and waits until signaled by another backend,
9090
whereupon it tries again. The signal will occur when UnpinBuffer decrements
9191
the shared pin count to 1. As indicated above, this operation might have to
92-
wait a good while before it acquires lock, but that shouldn't matter much for
93-
concurrent VACUUM. The current implementation only supports a single waiter
94-
for pin-count-1 on any particular shared buffer. This is enough for VACUUM's
95-
use, since we don't allow multiple VACUUMs concurrently on a single relation
96-
anyway. Anyone wishing to obtain a cleanup lock outside of recovery or a
97-
VACUUM must use the conditional variant of the function.
92+
wait a good while before it acquires the lock, but that shouldn't matter much
93+
for concurrent VACUUM. The current implementation only supports a single
94+
waiter for pin-count-1 on any particular shared buffer. This is enough for
95+
VACUUM's use, since we don't allow multiple VACUUMs concurrently on a single
96+
relation anyway. Anyone wishing to obtain a cleanup lock outside of recovery
97+
or a VACUUM must use the conditional variant of the function.
9898

9999

100100
Buffer Manager's Internal Locking

src/backend/storage/buffer/bufmgr.c

+2-2
Original file line numberDiff line numberDiff line change
@@ -921,7 +921,7 @@ ReadBuffer_common(SMgrRelation smgr, char relpersistence, ForkNumber forkNum,
921921
*
922922
* Since no-one else can be looking at the page contents yet, there is no
923923
* difference between an exclusive lock and a cleanup-strength lock. (Note
924-
* that we cannot use LockBuffer() of LockBufferForCleanup() here, because
924+
* that we cannot use LockBuffer() or LockBufferForCleanup() here, because
925925
* they assert that the buffer is already valid.)
926926
*/
927927
if ((mode == RBM_ZERO_AND_LOCK || mode == RBM_ZERO_AND_CLEANUP_LOCK) &&
@@ -1882,7 +1882,7 @@ BufferSync(int flags)
18821882
* and clears the flag right after we check, but that doesn't matter
18831883
* since SyncOneBuffer will then do nothing. However, there is a
18841884
* further race condition: it's conceivable that between the time we
1885-
* examine the bit here and the time SyncOneBuffer acquires lock,
1885+
* examine the bit here and the time SyncOneBuffer acquires the lock,
18861886
* someone else not only wrote the buffer but replaced it with another
18871887
* page and dirtied it. In that improbable case, SyncOneBuffer will
18881888
* write the buffer though we didn't need to. It doesn't seem worth

src/backend/storage/freespace/freespace.c

+2-2
Original file line numberDiff line numberDiff line change
@@ -393,7 +393,7 @@ fsm_space_needed_to_cat(Size needed)
393393
}
394394

395395
/*
396-
* Returns the physical block number an FSM page
396+
* Returns the physical block number of a FSM page
397397
*/
398398
static BlockNumber
399399
fsm_logical_to_physical(FSMAddress addr)
@@ -472,7 +472,7 @@ fsm_get_parent(FSMAddress child, uint16 *slot)
472472
}
473473

474474
/*
475-
* Given a logical address of a parent page, and a slot number get the
475+
* Given a logical address of a parent page and a slot number, get the
476476
* logical address of the corresponding child page.
477477
*/
478478
static FSMAddress

src/backend/storage/ipc/procarray.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -2673,7 +2673,7 @@ MinimumActiveBackends(int min)
26732673

26742674
/*
26752675
* Since we're not holding a lock, need to be prepared to deal with
2676-
* garbage, as someone could have incremented numPucs but not yet
2676+
* garbage, as someone could have incremented numProcs but not yet
26772677
* filled the structure.
26782678
*
26792679
* If someone just decremented numProcs, 'proc' could also point to a

src/backend/storage/lmgr/predicate.c

+2-2
Original file line numberDiff line numberDiff line change
@@ -496,8 +496,8 @@ SerializationNeededForRead(Relation relation, Snapshot snapshot)
496496
* Don't acquire locks or conflict when scanning with a special snapshot.
497497
* This excludes things like CLUSTER and REINDEX. They use the wholesale
498498
* functions TransferPredicateLocksToHeapRelation() and
499-
* CheckTableForSerializableConflictIn() to participate serialization, but
500-
* the scans involved don't need serialization.
499+
* CheckTableForSerializableConflictIn() to participate in serialization,
500+
* but the scans involved don't need serialization.
501501
*/
502502
if (!IsMVCCSnapshot(snapshot))
503503
return false;

src/backend/storage/smgr/md.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -901,7 +901,7 @@ mdnblocks(SMgrRelation reln, ForkNumber forknum)
901901
* We used to pass O_CREAT here, but that's has the disadvantage
902902
* that it might create a segment which has vanished through some
903903
* operating system misadventure. In such a case, creating the
904-
* segment here undermine _mdfd_getseg's attempts to notice and
904+
* segment here undermines _mdfd_getseg's attempts to notice and
905905
* report an error upon access to a missing segment.
906906
*/
907907
v->mdfd_chain = _mdfd_openseg(reln, forknum, segno, 0);

src/backend/utils/adt/timestamp.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -5148,7 +5148,7 @@ timestamp_zone_transform(PG_FUNCTION_ARGS)
51485148
* This function is just timestamp2timestamptz() except instead of
51495149
* shifting to the global timezone, we shift to the specified timezone.
51505150
* This is different from the other AT TIME ZONE cases because instead
5151-
* of shifting to a _to_ a new time zone, it sets the time to _be_ the
5151+
* of shifting _to_ a new time zone, it sets the time to _be_ the
51525152
* specified timezone.
51535153
*/
51545154
Datum

src/backend/utils/hash/dynahash.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@
6767
* are not implemented; otherwise functionality is identical.
6868
*
6969
* Compilation controls:
70-
* DEBUG controls some informative traces, mainly for debugging.
70+
* HASH_DEBUG controls some informative traces, mainly for debugging.
7171
* HASH_STATISTICS causes HashAccesses and HashCollisions to be maintained;
7272
* when combined with HASH_DEBUG, these are displayed by hdestroy().
7373
*

src/pl/plperl/plperl.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -3977,7 +3977,7 @@ plperl_inline_callback(void *arg)
39773977

39783978

39793979
/*
3980-
* Perl's own setlocal() copied from POSIX.xs
3980+
* Perl's own setlocale(), copied from POSIX.xs
39813981
* (needed because of the calls to new_*())
39823982
*/
39833983
#ifdef WIN32

src/test/perl/TestLib.pm

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# TestLib, low-level routines and actions regression tests.
22
#
33
# This module contains a set of routines dedicated to environment setup for
4-
# a PostgreSQL regression test tun, and includes some low-level routines
4+
# a PostgreSQL regression test run and includes some low-level routines
55
# aimed at controlling command execution, logging and test functions. This
66
# module should never depend on any other PostgreSQL regression test modules.
77

src/tools/valgrind.supp

+1-1
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@
136136

137137
# Atomic writes to 64bit atomic vars uses compare/exchange to
138138
# guarantee atomic writes of 64bit variables. pg_atomic_write is used
139-
# during initialization of the atomic variable, hat leads to an
139+
# during initialization of the atomic variable; that leads to an
140140
# initial read of the old, undefined, memory value. But that's just to
141141
# make sure the swap works correctly.
142142
{

0 commit comments

Comments
 (0)