Movatterモバイル変換

[0]ホーム
URL:

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

 Sign up
Appearance settings

Commit4ad6f13

Browse files
committed
Copyedit comments and documentation.
1 parentf07d18b commit4ad6f13

File tree

17 files changed

+25
-25
lines changed

17 files changed

+25
-25
lines changed

‎config/c-compiler.m4‎

Lines changed: 1 addition & 1 deletion
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‎

Lines changed: 1 addition & 1 deletion
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‎

Lines changed: 1 addition & 1 deletion
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‎

Lines changed: 1 addition & 1 deletion
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‎

Lines changed: 1 addition & 1 deletion
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 havetobe
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‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ typedef struct ExecParallelEstimateContext
7171
intnnodes;
7272
}ExecParallelEstimateContext;
7373

74-
/* Context object forExecParallelEstimate. */
74+
/* Context object forExecParallelInitializeDSM. */
7575
typedefstructExecParallelInitializeDSMContext
7676
{
7777
ParallelContext*pcxt;

‎src/backend/storage/buffer/README‎

Lines changed: 6 additions & 6 deletions
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 acquiresthelock, but that shouldn't matter much
93+
forconcurrent VACUUM. The current implementation only supports a single
94+
waiterfor pin-count-1 on any particular shared buffer. This is enough for
95+
VACUUM'suse, since we don't allow multiple VACUUMs concurrently on a single
96+
relationanyway. Anyone wishing to obtain a cleanup lock outside of recovery
97+
or aVACUUM must use the conditional variant of the function.
9898

9999

100100
Buffer Manager's Internal Locking

‎src/backend/storage/buffer/bufmgr.c‎

Lines changed: 2 additions & 2 deletions
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 acquiresthelock,
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‎

Lines changed: 2 additions & 2 deletions
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 numberan FSM page
396+
* Returns the physical block numberof a FSM page
397397
*/
398398
staticBlockNumber
399399
fsm_logical_to_physical(FSMAddressaddr)
@@ -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
staticFSMAddress

‎src/backend/storage/ipc/procarray.c‎

Lines changed: 1 addition & 1 deletion
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 incrementednumPucs but not yet
2676+
* garbage, as someone could have incrementednumProcs but not yet
26772677
* filled the structure.
26782678
*
26792679
* If someone just decremented numProcs, 'proc' could also point to a

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp