Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
1cacb3a0
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,发现更多精彩内容 >>
提交
1cacb3a0
编写于
12月 19, 2006
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Add timeline for next release to developer's FAQ.
上级
f528e242
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
90 addition
and
45 deletion
+90
-45
doc/FAQ_DEV
doc/FAQ_DEV
+23
-1
doc/src/FAQ/FAQ_DEV.html
doc/src/FAQ/FAQ_DEV.html
+67
-44
未找到文件。
doc/FAQ_DEV
浏览文件 @
1cacb3a0
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
Last updated:
Mon Nov 13 23:18:46
EST 2006
Last updated:
Tue Dec 19 17:37:24
EST 2006
Current maintainer: Bruce Momjian (bruce@momjian.us)
...
...
@@ -30,6 +30,7 @@ General Questions
1.16) Where can I get a copy of the SQL standards?
1.17) Where can I get technical assistance?
1.18) How do I get involved in PostgreSQL web site development?
1.19) What is the timeline for the next major PostgreSQL release?
Technical Questions
...
...
@@ -796,3 +797,24 @@ typedef struct nameData
pgsql/data directory. The client profile file will be put in the
client's current directory. Linux requires a compile with
-DLINUX_PROFILE for proper profiling.
2.9) What is the timeline for the next major PostgreSQL release?
The development schedule for the 8.3 release is:
March 1, 2006
Initial community review of all major feature patches
April 1, 2006
Feature freeze, all patches must be submitted for review and
application
mid-May, 2006
All patches applied, beta testing begins
July, 2006
Release of 8.3.0
Patches that appear after appropriate dates are typically not applied
but held for the next major release.
doc/src/FAQ/FAQ_DEV.html
浏览文件 @
1cacb3a0
...
...
@@ -13,7 +13,7 @@
<H1>
Developer's Frequently Asked Questions (FAQ) for
PostgreSQL
</H1>
<P>
Last updated:
Mon Nov 13 23:18:46
EST 2006
</P>
<P>
Last updated:
Tue Dec 19 17:37:24
EST 2006
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:bruce@momjian.us"
>
bruce@momjian.us
</A>
)
<BR>
...
...
@@ -55,6 +55,8 @@
assistance?
<BR>
<A
href=
"#item1.18"
>
1.18
</A>
) How do I get involved in PostgreSQL web
site development?
<BR>
<A
href=
"#item1.19"
>
1.19
</A>
) What is the timeline for the next major
PostgreSQL release?
<BR>
<H2>
Technical Questions
</H2>
...
...
@@ -937,57 +939,78 @@
<H3
id=
"item2.7"
>
2.7) What is CommandCounterIncrement()?
</H3>
<P>
Normally, transactions can not see the rows they modify. This
allows
<CODE>
UPDATE foo SET x = x + 1
</CODE>
to work correctly.
</P>
<P>
Normally, transactions can not see the rows they modify.
This allows
<CODE>
UPDATE foo SET x = x + 1
</CODE>
to work
correctly.
</P>
<P>
However, there are cases where a transactions needs to see
rows
affected in previous parts of the transaction. This is accomplished
using a Command Counter. Incrementing the counter allows
transactions to be broken into pieces so each piece can see rows
modified by previous pieces.
<I>
CommandCounterIncrement()
</I>
<P>
However, there are cases where a transactions needs to see
rows affected in previous parts of the transaction. This is
accomplished using a Command Counter. Incrementing the counter
allows transactions to be broken into pieces so each piece can
see rows
modified by previous pieces.
<I>
CommandCounterIncrement()
</I>
increments the Command Counter, creating a new part of the
transaction.
</P>
<H3
id=
"item2.8"
>
2.8) What debugging features are
available?
</H3>
<H3
id=
"item2.8"
>
2.8) What debugging features are available?
</H3>
<P>
First, try running
<I>
configure
</I>
with the --enable-cassert
option, many
<I>
assert()
</I>
s monitor the progress of the
backend
and halt the program when something unexpected occurs.
</P>
<P>
The
<I>
postmaster
</I>
has a
<I>
-d
</I>
option that allows
even more
detailed information to be reported. The
<I>
-d
</I>
option takes a
number that specifies the debug level. Be warned that high debug
level values generate large log files.
</P>
<P>
If the
<I>
postmaster
</I>
is not running, you can actually
run the
<I>
postgres
</I>
backend from the command line, and type your
<SMALL>
SQL
</SMALL>
statement directly. This is recommended
<B>
only
</B>
for debugging purposes. If you have compiled with
debugging
symbols, you can use a debugger to see what is happening. Because
the backend was not started from
<I>
postmaster
</I>
, it is not
running in an identical environment and locking/backend interaction
problems might not be duplicated.
</P>
<P>
If the
<I>
postmaster
</I>
is running, start
<I>
psql
</I>
in
one
window, then find the
<SMALL>
PID
</SMALL>
of the
<I>
postgres
</I>
option, many
<I>
assert()
</I>
s monitor the progress of the
backend
and halt the program when something unexpected occurs.
</P>
<P>
The
<I>
postmaster
</I>
has a
<I>
-d
</I>
option that allows
even more detailed information to be reported. The
<I>
-d
</I>
option takes a number that specifies the debug level. Be warned
that high debug
level values generate large log files.
</P>
<P>
If the
<I>
postmaster
</I>
is not running, you can actually
run the
<I>
postgres
</I>
backend from the command line, and type
your
<SMALL>
SQL
</SMALL>
statement directly. This is recommended
<B>
only
</B>
for debugging purposes. If you have compiled with
debugging symbols, you can use a debugger to see what is
happening. Because the backend was not started from
<I>
postmaster
</I>
,
it is not running in an identical environment and locking/backend
interaction
problems might not be duplicated.
</P>
<P>
If the
<I>
postmaster
</I>
is running, start
<I>
psql
</I>
in
one
window, then find the
<SMALL>
PID
</SMALL>
of the
<I>
postgres
</I>
process used by
<I>
psql
</I>
using
<CODE>
SELECT pg_backend_pid()
</CODE>
.
Use a debugger to attach to the
<I>
postgres
</I>
<SMALL>
PID
</SMALL>
.
You can set breakpoints in the debugger and issue queries from the
other. If you are looking to find the location that is generating
an error or log message, set a breakpoint at
<I>
errfinish
</I>
.
<I>
psql
</I>
. If you are debugging
<I>
postgres
</I>
startup, you can
set PGOPTIONS="-W n", then start
<I>
psql
</I>
. This will cause startup
to delay for
<I>
n
</I>
seconds so you can attach to the process with
the debugger, set any breakpoints, and continue through the startup
sequence.
</P>
<P>
You can also compile with profiling to see what functions are
taking execution time. The backend profile files will be deposited
in the
<I>
pgsql/data
</I>
directory. The client profile file will be
put in the client's current directory. Linux requires a compile with
<I>
-DLINUX_PROFILE
</I>
for proper profiling.
</P>
You can set breakpoints in the debugger and issue queries from
the other. If you are looking to find the location that is
generating an error or log message, set a breakpoint at
<I>
errfinish
</I>
.
<I>
psql
</I>
. If you are debugging
<I>
postgres
</I>
startup, you
can set PGOPTIONS="-W n", then start
<I>
psql
</I>
. This will
cause startup to delay for
<I>
n
</I>
seconds so you can attach
to the process with the debugger, set any breakpoints, and
continue through the startup sequence.
</P>
<P>
You can also compile with profiling to see what functions
are taking execution time. The backend profile files will be
deposited in the
<I>
pgsql/data
</I>
directory. The client profile
file will be put in the client's current directory. Linux
requires a compile with
<I>
-DLINUX_PROFILE
</I>
for proper
profiling.
</P>
<H3
id=
"item2.9"
>
2.9) What is the timeline for the next major
PostgreSQL release?
<BR>
<P>
The development schedule for the 8.3 release is:
</P>
<DL>
<DD>
March 1, 2006
</DD>
<DT>
Initial community review of all major feature patches
</DT>
<DD>
April 1, 2006
</DD>
<DT>
Feature freeze, all patches must be submitted for review and application
</DT>
<DD>
mid-May, 2006
</DD>
<DT>
All patches applied, beta testing begins
</DT>
<DD>
July, 2006
</DD>
<DT>
Release of 8.3.0
</DT>
</DL>
<P>
Patches that appear after appropriate dates are typically
not applied but held for the next major release.
</P>
</BODY>
</HTML>
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录