Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
a952d672
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,发现更多精彩内容 >>
提交
a952d672
编写于
12月 20, 1996
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Remove NOTIFY_PATCH.
上级
4371756f
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
0 addition
and
14 deletion
+0
-14
src/include/config.h
src/include/config.h
+0
-14
未找到文件。
src/include/config.h
浏览文件 @
a952d672
...
...
@@ -298,20 +298,6 @@
*/
#define FUNC_UTIL_PATCH
/*
* Async notifies received while a backend is in the middle of a begin/end
* transaction block are lost by libpq when the final end command is issued.
*
* The bug is in the routine PQexec of libpq. The routine throws away any
* message from the backend when a message of type 'C' is received. This
* type of message is sent when the result of a portal query command with
* no tuples is returned. Unfortunately this is the case of the end command.
* As all async notification are sent only when the transaction is finished,
* if they are received in the middle of a transaction they are lost in the
* libpq library. I added some tracing code to PQexec and this is the output:
*/
#define PQ_NOTIFY_PATCH
/*
* Define this if you want to retrieve arrays attributes as Tcl lists instead
* of postgres C-like arrays, for example {{"a1" "a2"} {"b1" "b2"}} instead
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录