索引（B树，位图，GiST） 安全性 语言支持 标准SQL支持，SQL 2003 OLAP扩展 支持 MapReduce 扩展编程语言 (Python,R, Java, Perl, C/C++） 第三方工具 BI 工具, ETL 工具 文本分析，数据挖掘等 管理工具 GP Command Center GP Workload Manager 7 Pivotal Confidential–Inter Segment 1C Segment 1D Segment 2A Segment 2B Segment 2C Segment 2D Segment 3A Segment 3B Segment 3C Segment 3D Segment 1A Segment 1B Segment 1C Segment 1D Segment 2A Segment 2B Segment 2C Segment 2D Segment 3A Segment 3B Segment 3C Segment 3D Segment 1A Segment 1B Segment 1C Segment 1D Segment 2A Segment 2B Segment 2C Segment 2D Segment 3A Segment 3B Segment 3C Segment 3D 分布和分区 SELECT COUNT(*)

XML Teradata SQL Other DB SQL Apache MADlib ML/Statistics/Graph Python. R, Java, Perl, C Programmatic Apache SOLR Text PostGIS GeoSpatial Custom Apps BI / Reporting Machine Learning ⼯工作原理理 2017.thegiac.com C API (Greenplum, PostgreSQL, HAWQ) 底层抽象层 (数组操作、类型转换、数值计算库等) 数据库内建函 数 ⽤用户接⼝口 ⾼高层抽象层 (迭代控制器器) 内循环函数 (实现机器器学习逻辑) Python SQL C++ MADlib 架构 2017.thegiac

mysql 在这方面限制。 3) 扩展性方面，Postgresql 比 mysql 也要出色许多，Postgres 天生就 是 为 扩 展 而 生 的， 你 可 以 在 PG 中 用 Python、C、Perl、TCL、 PLSQL 等等语言来扩展功能，在后续章节中，我将展现这种扩展 是如何的方便，另外，开发新的功能模块、新的数据类型、新的索 引类型等等非常方便，只要按照 API 接口开发，无需对 Postgresql 的良好扩展性（这里是 extension，不 是 scalability），Greenplum 可以采用各种开发语言来扩展用户自定 义函数（UDF）（我个人是 Python 和 C 的 fans，后续章节与大家分享）。 这些自定义函数部署到 Greenplum 后可用充分享受到实例级别的并行 性能优势，我们强烈建议用户将库外的处理逻辑，部署到用 MPP 数 据库的 UDF 这种 等等很多，这些技术有些是在 Mapreduce 上做 了优化。例如 Spark 采用内存中的 Mapreduce 技术，号称性能比 基于文件的的 Mapreduce 提高 10 倍；有的则采用 C/C++ 语言替 代 Java 语言重构 Hadoop 和 Mapreuce（如 MapR 公司及国内某 知名电商的大数据平台）；而有些则直接绕开了 Mapreduce 另起 炉灶，如 Impala、hawq

Custom Data Access Protocol 844 Notes 845 Installing the External Table Protocol 845 gpextprotocal.c 846 Querying Data 852 About Greenplum Query Processing 853 Understanding Query Planning and Dispatch strict function with zero arguments was used as a filter for NULL rejection. 181646913 : Resolves a C++ compiler and nullptr usage mismatch by using NULL instead. VMware Tanzu Greenplum v6.20 Documentation process was searching for a file that had been rightfully deleted. 12670 : Introduces a contentId (%c) parameter to the WAL archive_command and restore_command; this parameter identifies a WAL stream from

the External Table Protocol 845 Installing the External Table Protocol 0 gpextprotocal.c 846 gpextprotocal.c 0 Querying Data 852 Querying Data 0 About Greenplum Query Processing 853 About Greenplum process was searching for a file that had been rightfully deleted. 12670 : Introduces a contentId (%c) parameter to the WAL archive_command and restore_command; this parameter identifies a WAL stream from "22023","recovery command file ""recovery.conf"" request for standby mode not specified",,,,,,,0,,"xlog.c",5465 Greenplum Database now supports server recovery in a non-continuous mode using standby_mode=on

the External Table Protocol 854 Installing the External Table Protocol 0 gpextprotocal.c 855 gpextprotocal.c 0 Querying Data 861 Querying Data 0 About Greenplum Query Processing 862 About Greenplum process was searching for a file that had been rightfully deleted. 12670 : Introduces a contentId (%c) parameter to the WAL archive_command and restore_command; this parameter identifies a WAL stream from "22023","recovery command file ""recovery.conf"" request for standby mode not specified",,,,,,,0,,"xlog.c",5465 Greenplum Database now supports server recovery in a non-continuous mode using standby_mode=on

the External Table Protocol 777 Installing the External Table Protocol 0 gpextprotocal.c 778 gpextprotocal.c 0 Querying Data 784 Querying Data 0 About Greenplum Query Processing 785 About Greenplum For all GUCs with a vartype of string, you may no longer enclose the value you pass to gpconfig -c in single quotes. 178254153 Resolved an issue where gprecoverseg -p was reporting an error despite operator name in the CREATE OPERATOR command (deprecated since 6.0). The Greenplum external table C API (deprecated since 6.0). Any developers using this API are encouraged to use the new Foreign Data

Custom Data Access Protocol 728 Notes 729 Installing the External Table Protocol 729 gpextprotocal.c 730 Querying Data 735 About Greenplum Query Processing 736 Understanding Query Planning and Dispatch define the structure of the record with an AS clause. select * from json_to_record(‘{“a”:1,“b”:[1,2,3],“c”:“bar”}’) as x(a int, b text, d text) a | b | d —+———+— 1 | [1,2,3] | json_to_recordset(json) jsonb structure of the record with an AS clause. select * from json_to_recordset(‘[{“a”:1,“b”:“foo”},{“a”:“2”,“c”:“bar”}]’) as x(a int, b text); a | b —+—– 1 | foo 2 | Note: The examples for the functions json_populate_record()

Custom Data Access Protocol 755 Notes 756 Installing the External Table Protocol 756 gpextprotocal.c 757 Querying Data 762 About Greenplum Query Processing 763 Understanding Query Planning and Dispatch truncation during a segment upgrade. 13706 Resolves an error, FATAL: Unexpected internal error (list.c:395), that could occur when creating a plan for a correlated subquery against a partitioned table. master. 13669 Resolved an assertion failure, "FATAL" error "Unexpected internal error (vmem_tracker.c:436)","Process 399817 will wait for gp_debug_linger=120 seconds before termination, that could occur

Custom Data Access Protocol 764 Notes 764 Installing the External Table Protocol 765 gpextprotocal.c 765 Querying Data 770 About Greenplum Query Processing 771 Understanding Query Planning and Dispatch Documentation VMware by Broadcom 184 13706 Resolves an error, FATAL: Unexpected internal error (list.c:395), that could occur when creating a plan for a correlated subquery against a partitioned table. master. 13669 Resolved an assertion failure, "FATAL" error "Unexpected internal error (vmem_tracker.c:436)","Process 399817 will wait for gp_debug_linger=120 seconds before termination, that could occur