Python、C、Perl、TCL、 PLSQL 等等语言来扩展功能，在后续章节中，我将展现这种扩展 是如何的方便，另外，开发新的功能模块、新的数据类型、新的索 引类型等等非常方便，只要按照 API 接口开发，无需对 PG 重新编译。 PG 中 contrib 目录下的各个第三方模块，在 GP 中的 postgis 空间 数据库、R、Madlib、pgcrypto 各类加密算法、gptext 全文检索都 是通过这种方式实现功能扩展的。 postgresql 的 contrib 中的一些常用模块 Greenplum 提 供了编译后的模块开箱即用，如：oraface、postgis、pgcrypt 等， 对于其它模块，用户可以自行将 contrib 下的代码与 Greenplum 的 include 头文件编译后，将动态 so 库文件部署到所有节点就可进行测 试使用了。有些模块还是非常好用的，例如：oraface，基本上集成了 Oracle Hadoop 集群配合运作的案例越 来越多。在中国移动的大数据架 构规范中，云化 ETL 是一个重 要的组成部分。云化 ETL 就是构架在 Hadoop 集群之上。Greenplum 提供了专用产品模块 gphdfs，Greenplum 通过 gphdfs 可以直接与 HDFS 上的数据进行交互，并且可以同时发挥 Greenplum 和 Hadoop 两者并行处理的优势。 Big Date2.indd

."\n\n"; } echo "Operation done successfully\n"; pg_close($db); ?> 1.7 node客户端访问 客户端访问 1）安装pg模块 npm install -g node_gyp npm install -g pg 2）连接数据库并访问 ⽰例代码如下： var pg = require('pg'); var constring 优刻得 174/206 接⼊第三⽅ BI ⼯具 Greenplum数据仓库 UDW Copyright © 2012-2021 UCloud 优刻得 175/206 其中，每个Slice对应的模块，可以⾃由拖拽位置和⼤⼩，并保存整个Dashboard的布局。 关于superset的更多信息请参考： http://airbnb.io/superset/ https://github.com/airbnb/superset

数据仓库体系架构 一 Greenplum开发规范 五 Greenplum运维体系 四 Greenplum扩展规划 六 39 Greenplum扩展规划 整体扩展思路 • OLAP三大模块不断完善 Ø 通过dbsync程序，实现数据传输和加载优化 Ø 对于Greenplum上的架构和设计不断优化 Ø 继续建设多样化的postgresql数据集市，满足不同需求 • 优化现有业务的调度实现

bool delayEagerFree 某个Segment的排序节点输出最后一条元组 后是否可以提前 释放内存 36 ● ExecSort： 从下层Outer节点读取所有元组，并传递给tuplesort模块进行排序 排序节点 37 TupleSort是排序节点的核心，算法主要阶段： ● 第一阶段初始化TupleSort，通过调用函数tuplesort_begin_common，生成 Tuple

的支持。这些新数据类型及相关函数有助于打造 一个没有孤岛的环境，结构化、半结构化和非结构化数据均可在一个位置进行存储和分析。其他功能还有 dblink，这是一 个用于与其他数据库（无论在同一数据库主机还是远程主机上）建立连接的新模块。Pivotal Greenplum 支持数据库用户 使用 dblink 在其他数据库中执行简短的临时查询。最后，Greenplum 5 将已安装的 Python 版本升级为 2.7。PL/Python

corrupt the shared memory, reporting errors such as latch already owned, failed to re- find shared lock object, failed to re-find shared proclock object, or sorry, too many clients already. 376446 Resolves if it does not exist, the utility generates the file and exits with a prompt to verify the file and re-run gpexpand. 16478 Resolves a problem where running utilities such as gpstop or gpstate would fail of those mirrors would be marked as up and the user would have to re-run these operations for all mirrors. Now, the user only need re-run these operations for those mirrors that failed during pg_basebackup

of those mirrors would be marked as up and the user would have to re-run these operations for all mirrors. Now, the user only need re-run these operations for those mirrors that failed during pg_basebackup unblocked it would attempt to re-initialize all sub-plans even if they were not needed for the plan being re-evaluated. Greenplum now considers subplan motions when re-initializing, and correctly throws segment instance hostname is bound to a different IP address at runtime, you must execute gpstop -U to re-load the gp_interconnect_proxy_addresses value. See Configuring Proxies for the Greenplum Interconnect

of those mirrors would be marked as up and the user would have to re-run these operations for all mirrors. Now, the user only need re-run these operations for those mirrors that failed during pg_basebackup unblocked it would attempt to re-initialize all sub-plans even if they were not needed for the plan being re-evaluated. Greenplum now considers subplan motions when re-initializing, and correctly throws segment instance hostname is bound to a different IP address at runtime, you must execute gpstop -U to re-load the gp_interconnect_proxy_addresses value. See Configuring Proxies for the Greenplum Interconnect

of those mirrors would be marked as up and the user would have to re-run these operations for all mirrors. Now, the user only need re-run these operations for those mirrors that failed during pg_basebackup unblocked it would attempt to re-initialize all sub-plans even if they were not needed for the plan being re-evaluated. Greenplum now considers subplan motions when re-initializing, and correctly throws segment instance hostname is bound to a different IP address at runtime, you must execute gpstop -U to re-load the gp_interconnect_proxy_addresses value. See Configuring Proxies for the Greenplum Interconnect

if it does not exist, the utility generates the file and exits with a prompt to verify the file and re-run gpexpand. 16478 Resolves a problem where running utilities such as gpstop or gpstate would fail of those mirrors would be marked as up and the user would have to re-run these operations for all mirrors. Now, the user only need re-run these operations for those mirrors that failed during pg_basebackup unblocked it would attempt to re-initialize all sub-plans even if they were not needed for the plan being re-evaluated. Greenplum now considers subplan motions when re-initializing, and correctly throws