Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
4ad6f135
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
前往新版Gitcode,体验更适合开发者的 AI 搜索 >>
提交
4ad6f135
编写于
4月 01, 2016
作者:
N
Noah Misch
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Copyedit comments and documentation.
上级
f07d18b6
变更
17
隐藏空白更改
内联
并排
Showing
17 changed file
with
25 addition
and
25 deletion
+25
-25
config/c-compiler.m4
config/c-compiler.m4
+1
-1
contrib/pgstattuple/pgstatapprox.c
contrib/pgstattuple/pgstatapprox.c
+1
-1
doc/src/sgml/install-windows.sgml
doc/src/sgml/install-windows.sgml
+1
-1
doc/src/sgml/release-9.3.sgml
doc/src/sgml/release-9.3.sgml
+1
-1
doc/src/sgml/xml2.sgml
doc/src/sgml/xml2.sgml
+1
-1
src/backend/executor/execParallel.c
src/backend/executor/execParallel.c
+1
-1
src/backend/storage/buffer/README
src/backend/storage/buffer/README
+6
-6
src/backend/storage/buffer/bufmgr.c
src/backend/storage/buffer/bufmgr.c
+2
-2
src/backend/storage/freespace/freespace.c
src/backend/storage/freespace/freespace.c
+2
-2
src/backend/storage/ipc/procarray.c
src/backend/storage/ipc/procarray.c
+1
-1
src/backend/storage/lmgr/predicate.c
src/backend/storage/lmgr/predicate.c
+2
-2
src/backend/storage/smgr/md.c
src/backend/storage/smgr/md.c
+1
-1
src/backend/utils/adt/timestamp.c
src/backend/utils/adt/timestamp.c
+1
-1
src/backend/utils/hash/dynahash.c
src/backend/utils/hash/dynahash.c
+1
-1
src/pl/plperl/plperl.c
src/pl/plperl/plperl.c
+1
-1
src/test/perl/TestLib.pm
src/test/perl/TestLib.pm
+1
-1
src/tools/valgrind.supp
src/tools/valgrind.supp
+1
-1
未找到文件。
config/c-compiler.m4
浏览文件 @
4ad6f135
...
...
@@ -335,7 +335,7 @@ if test x"$Ac_cachevar" = x"yes"; then
$1="${$1} $2"
fi
undefine([Ac_cachevar])dnl
])# PGAC_PROG_CC_
CFLAGS
_OPT
])# PGAC_PROG_CC_
VAR
_OPT
...
...
contrib/pgstattuple/pgstatapprox.c
浏览文件 @
4ad6f135
/*-------------------------------------------------------------------------
*
* pgstatappro
c
.c
* pgstatappro
x
.c
* Bloat estimation functions
*
* Copyright (c) 2014-2016, PostgreSQL Global Development Group
...
...
doc/src/sgml/install-windows.sgml
浏览文件 @
4ad6f135
...
...
@@ -457,7 +457,7 @@ $ENV{CONFIG}="Debug";
<para>
Running the regression tests on client programs, with
<command>vcregress bincheck</>, or on recovery tests, with
<command>vcregress recoverycheck</> requires an additional Perl module
<command>vcregress recoverycheck</>
,
requires an additional Perl module
to be installed:
<variablelist>
<varlistentry>
...
...
doc/src/sgml/release-9.3.sgml
浏览文件 @
4ad6f135
...
...
@@ -9689,7 +9689,7 @@ ALTER EXTENSION hstore UPDATE;
<listitem>
<para>
Remove <filename>src/tool/backend</>, now that the content is on
Remove <filename>src/tool
s
/backend</>, now that the content is on
the <productname>PostgreSQL</> wiki (Bruce Momjian)
</para>
</listitem>
...
...
doc/src/sgml/xml2.sgml
浏览文件 @
4ad6f135
...
...
@@ -324,7 +324,7 @@ AS t(article_id integer, author text, page_count integer, title text);
</para>
<para>
The calling <command>SELECT</> statement doesn't necessarily have be
The calling <command>SELECT</> statement doesn't necessarily have
to
be
just <literal>SELECT *</> — it can reference the output
columns by name or join them to other tables. The function produces a
virtual table with which you can perform any operation you wish (e.g.
...
...
src/backend/executor/execParallel.c
浏览文件 @
4ad6f135
...
...
@@ -71,7 +71,7 @@ typedef struct ExecParallelEstimateContext
int
nnodes
;
}
ExecParallelEstimateContext
;
/* Context object for ExecParallel
Estimate
. */
/* Context object for ExecParallel
InitializeDSM
. */
typedef
struct
ExecParallelInitializeDSMContext
{
ParallelContext
*
pcxt
;
...
...
src/backend/storage/buffer/README
浏览文件 @
4ad6f135
...
...
@@ -89,12 +89,12 @@ then returns false, while LockBufferForCleanup() releases the exclusive lock
(but not the caller's pin) and waits until signaled by another backend,
whereupon it tries again. The signal will occur when UnpinBuffer decrements
the shared pin count to 1. As indicated above, this operation might have to
wait a good while before it acquires
lock, but that shouldn't matter much for
concurrent VACUUM. The current implementation only supports a single waiter
for pin-count-1 on any particular shared buffer. This is enough for VACUUM's
use, since we don't allow multiple VACUUMs concurrently on a single relation
anyway. Anyone wishing to obtain a cleanup lock outside of recovery or a
VACUUM must use the conditional variant of the function.
wait a good while before it acquires
the lock, but that shouldn't matter much
for concurrent VACUUM. The current implementation only supports a single
waiter for pin-count-1 on any particular shared buffer. This is enough for
VACUUM's use, since we don't allow multiple VACUUMs concurrently on a single
relation anyway. Anyone wishing to obtain a cleanup lock outside of recovery
or a
VACUUM must use the conditional variant of the function.
Buffer Manager's Internal Locking
...
...
src/backend/storage/buffer/bufmgr.c
浏览文件 @
4ad6f135
...
...
@@ -921,7 +921,7 @@ ReadBuffer_common(SMgrRelation smgr, char relpersistence, ForkNumber forkNum,
*
* Since no-one else can be looking at the page contents yet, there is no
* difference between an exclusive lock and a cleanup-strength lock. (Note
* that we cannot use LockBuffer() o
f
LockBufferForCleanup() here, because
* that we cannot use LockBuffer() o
r
LockBufferForCleanup() here, because
* they assert that the buffer is already valid.)
*/
if
((
mode
==
RBM_ZERO_AND_LOCK
||
mode
==
RBM_ZERO_AND_CLEANUP_LOCK
)
&&
...
...
@@ -1882,7 +1882,7 @@ BufferSync(int flags)
* and clears the flag right after we check, but that doesn't matter
* since SyncOneBuffer will then do nothing. However, there is a
* further race condition: it's conceivable that between the time we
* examine the bit here and the time SyncOneBuffer acquires lock,
* examine the bit here and the time SyncOneBuffer acquires
the
lock,
* someone else not only wrote the buffer but replaced it with another
* page and dirtied it. In that improbable case, SyncOneBuffer will
* write the buffer though we didn't need to. It doesn't seem worth
...
...
src/backend/storage/freespace/freespace.c
浏览文件 @
4ad6f135
...
...
@@ -393,7 +393,7 @@ fsm_space_needed_to_cat(Size needed)
}
/*
* Returns the physical block number
an
FSM page
* Returns the physical block number
of a
FSM page
*/
static
BlockNumber
fsm_logical_to_physical
(
FSMAddress
addr
)
...
...
@@ -472,7 +472,7 @@ fsm_get_parent(FSMAddress child, uint16 *slot)
}
/*
* Given a logical address of a parent page
, and a slot number
get the
* Given a logical address of a parent page
and a slot number,
get the
* logical address of the corresponding child page.
*/
static
FSMAddress
...
...
src/backend/storage/ipc/procarray.c
浏览文件 @
4ad6f135
...
...
@@ -2673,7 +2673,7 @@ MinimumActiveBackends(int min)
/*
* Since we're not holding a lock, need to be prepared to deal with
* garbage, as someone could have incremented numP
u
cs but not yet
* garbage, as someone could have incremented numP
ro
cs but not yet
* filled the structure.
*
* If someone just decremented numProcs, 'proc' could also point to a
...
...
src/backend/storage/lmgr/predicate.c
浏览文件 @
4ad6f135
...
...
@@ -496,8 +496,8 @@ SerializationNeededForRead(Relation relation, Snapshot snapshot)
* Don't acquire locks or conflict when scanning with a special snapshot.
* This excludes things like CLUSTER and REINDEX. They use the wholesale
* functions TransferPredicateLocksToHeapRelation() and
* CheckTableForSerializableConflictIn() to participate
serialization, but
* the scans involved don't need serialization.
* CheckTableForSerializableConflictIn() to participate
in serialization,
*
but
the scans involved don't need serialization.
*/
if
(
!
IsMVCCSnapshot
(
snapshot
))
return
false
;
...
...
src/backend/storage/smgr/md.c
浏览文件 @
4ad6f135
...
...
@@ -901,7 +901,7 @@ mdnblocks(SMgrRelation reln, ForkNumber forknum)
* We used to pass O_CREAT here, but that's has the disadvantage
* that it might create a segment which has vanished through some
* operating system misadventure. In such a case, creating the
* segment here undermine _mdfd_getseg's attempts to notice and
* segment here undermine
s
_mdfd_getseg's attempts to notice and
* report an error upon access to a missing segment.
*/
v
->
mdfd_chain
=
_mdfd_openseg
(
reln
,
forknum
,
segno
,
0
);
...
...
src/backend/utils/adt/timestamp.c
浏览文件 @
4ad6f135
...
...
@@ -5148,7 +5148,7 @@ timestamp_zone_transform(PG_FUNCTION_ARGS)
* This function is just timestamp2timestamptz() except instead of
* shifting to the global timezone, we shift to the specified timezone.
* This is different from the other AT TIME ZONE cases because instead
* of shifting
to a
_to_ a new time zone, it sets the time to _be_ the
* of shifting _to_ a new time zone, it sets the time to _be_ the
* specified timezone.
*/
Datum
...
...
src/backend/utils/hash/dynahash.c
浏览文件 @
4ad6f135
...
...
@@ -67,7 +67,7 @@
* are not implemented; otherwise functionality is identical.
*
* Compilation controls:
* DEBUG controls some informative traces, mainly for debugging.
*
HASH_
DEBUG controls some informative traces, mainly for debugging.
* HASH_STATISTICS causes HashAccesses and HashCollisions to be maintained;
* when combined with HASH_DEBUG, these are displayed by hdestroy().
*
...
...
src/pl/plperl/plperl.c
浏览文件 @
4ad6f135
...
...
@@ -3977,7 +3977,7 @@ plperl_inline_callback(void *arg)
/*
* Perl's own setlocal
()
copied from POSIX.xs
* Perl's own setlocal
e(),
copied from POSIX.xs
* (needed because of the calls to new_*())
*/
#ifdef WIN32
...
...
src/test/perl/TestLib.pm
浏览文件 @
4ad6f135
# TestLib, low-level routines and actions regression tests.
#
# This module contains a set of routines dedicated to environment setup for
# a PostgreSQL regression test
tun,
and includes some low-level routines
# a PostgreSQL regression test
run
and includes some low-level routines
# aimed at controlling command execution, logging and test functions. This
# module should never depend on any other PostgreSQL regression test modules.
...
...
src/tools/valgrind.supp
浏览文件 @
4ad6f135
...
...
@@ -136,7 +136,7 @@
# Atomic writes to 64bit atomic vars uses compare/exchange to
# guarantee atomic writes of 64bit variables. pg_atomic_write is used
# during initialization of the atomic variable
,
hat leads to an
# during initialization of the atomic variable
; t
hat leads to an
# initial read of the old, undefined, memory value. But that's just to
# make sure the swap works correctly.
{
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录