for PostgreSQL - 打造更简单易用的Cloud SQL Data Warehouse 个人介绍 缪长风 ⚫ 2010年初加入支付宝，负责Oracle RAC和Greenplum数据仓库 ⚫ 有幸参与了Oracle RAC到 Greenplum再到Hadoop以及最终到 ODPS的架构演进工作。 ⚫ 2012年起，转至阿里巴巴大数据团队，负责Hbase/OTS业务支 PostgreSQL 典型场景 4. AnalyticDB for PostgreSQL 未来演进 Greenplum发展史@Alibaba rac1 rac2 rac3 rac n Oracle RAC 11G ODPS ETL建模 交互式分析 AnalyticDB for MySQL 实时数仓 ⚫ All In One数仓去O ⚫ 交互式分析 ⚫ 中小规模实时数仓 小烟枪在阿里的场景裂变 PostgreSQL 在线MPP数据仓库服务 简单易用、海量扩展、兼容部分Oracle 语法生态、既支持在线交互分析，也支持离线数据处理。 AnalyticDB for PostgreSQL （云Greenplum）低成本，快速 构筑在线企业数据仓库。 • 应用易开发、适配 支持SQL 2003，部分兼容Oracle语法， 支持PL/SQL 存储过程，OLAP窗口函数，事务及数据库标准隔离级别

户数据量很少，也需要使用双数据库，更新运维都比较麻 烦。 2018年PostgreSQL中国技术大会 PgSQL≈MySQL+MongoDB • 个人认为，PgSQL结合了MySQL关系型数据库事务处理能力 以及MongoDB的大数据处理能力。稳定性强，高并发，支 持JSON,扩展字段特别方便。 • 我们团队没有大量专业的DBA运维人员，业务迭代也非常 快，需求变更频繁，对数据库非常依赖，用了PgSQL之后， 感觉可以充分满足我们的需求。

.........................................................................589 35.11. Porting from Oracle PL/SQL.....................................................................................594 35 semantics behind your commands. Especially refrain from merely saying that “This is not what SQL says/Oracle does.” Digging out the correct behavior from SQL is not a fun undertaking, nor do we all know how for example, to_char(-12, ’S9999’) produces ’ -12’, but to_char(-12, ’MI9999’) produces ’- 12’. The Oracle im- plementation does not allow the use of MI ahead of 9, but rather requires that 9 precede MI.

.........................................................................556 35.11. Porting from Oracle PL/SQL..............................................................................561 35.11.1 semantics behind your commands. Especially refrain from merely saying that “This is not what SQL says/Oracle does.” Digging out the correct behavior from SQL is not a fun undertaking, nor do we all know how for example, to_char(-12, ’S9999’) produces ’ -12’, but to_char(-12, ’MI9999’) produces ’- 12’. The Oracle implementation does not allow the use of MI ahead of 9, but rather requires that 9 precede MI. •

.........................................................................630 36.11. Porting from Oracle PL/SQL.....................................................................................635 36 semantics behind your commands. Especially refrain from merely saying that “This is not what SQL says/Oracle does.” Digging out the correct behavior from SQL is not a fun undertaking, nor do we all know how for example, to_char(-12, ’S9999’) produces ’ -12’, but to_char(-12, ’MI9999’) produces ’- 12’. The Oracle im- plementation does not allow the use of MI ahead of 9, but rather requires that 9 precede MI.

.........................................................................633 36.11. Porting from Oracle PL/SQL.....................................................................................639 36 semantics behind your commands. Especially refrain from merely saying that “This is not what SQL says/Oracle does.” Digging out the correct behavior from SQL is not a fun undertaking, nor do we all know how for example, to_char(-12, ’S9999’) produces ’ -12’, but to_char(-12, ’MI9999’) produces ’- 12’. The Oracle im- plementation does not allow the use of MI ahead of 9, but rather requires that 9 precede MI.

.........................................................................705 37.11. Porting from Oracle PL/SQL.....................................................................................711 37 semantics behind your commands. Especially refrain from merely saying that “This is not what SQL says/Oracle does.” Digging out the correct behavior from SQL is not a fun undertaking, nor do we all know how for example, to_char(-12, ’S9999’) produces ’ -12’, but to_char(-12, ’MI9999’) produces ’- 12’. The Oracle im- plementation does not allow the use of MI ahead of 9, but rather requires that 9 precede MI.

.........................................................................705 37.11. Porting from Oracle PL/SQL.....................................................................................711 37 semantics behind your commands. Especially refrain from merely saying that “This is not what SQL says/Oracle does.” Digging out the correct behavior from SQL is not a fun undertaking, nor do we all know how for example, to_char(-12, ’S9999’) produces ’ -12’, but to_char(-12, ’MI9999’) produces ’- 12’. The Oracle im- plementation does not allow the use of MI ahead of 9, but rather requires that 9 precede MI.

Marks.......................................................................805 38.12. Porting from Oracle PL/SQL.....................................................................................807 38 your commands. Especially refrain from merely saying that “This is not what SQL liii Preface says/Oracle does.” Digging out the correct behavior from SQL is not a fun undertaking, nor do we all know how for example, to_char(-12, ’S9999’) produces ’ -12’, but to_char(-12, ’MI9999’) produces ’- 12’. The Oracle im- plementation does not allow the use of MI ahead of 9, but rather requires that 9 precede MI.

Quotation Marks................................................................761 38.12. Porting from Oracle PL/SQL..............................................................................762 38.12.1 semantics behind your commands. Especially refrain from merely saying that “This is not what SQL says/Oracle does.” Digging out the correct behavior from SQL is not a fun undertaking, nor do we all know how for example, to_char(-12, ’S9999’) produces ’ -12’, but to_char(-12, ’MI9999’) produces ’- 12’. The Oracle implementation does not allow the use of MI ahead of 9, but rather requires that 9 precede MI. •