2018年PostgreSQL中国技术大会 为什么我们抛弃MongoDB和 MySQL，选择PgSQL 张启程 qc@aochuang.cn 奥创软件研究院（上海）研发中心 2018年PostgreSQL中国技术大会 任何数据库都很好用 • 我不是一个专业的DBA ，对数据库的理解不够深入，也不 一定准确，在此抛砖引玉，只是结合我们团队业务场景来 分享下我们选择数据库的过程。 • 2018年PostgreSQL中国技术大会 MySQL应用史 • 最开始做的站群系统WEB端使用MySQL： • copy简单快速，批量复制，替换修改简单； • 每个网站一个库，单体数据量小，数据类型固定； • 后来做SCRM系统，也首选MySQL： • 需求经常改动，每次改需求先改数据库； • 数据量越来越大，越来越不了解这只海豚； 2018年PostgreSQL中国技术大会 MySQL+MongoDB • • 迫于无奈，分拆数据，将需要用到事务、调用频繁的数据 继续用MySQL,将IM中聊天记录等数据量大的数据，用 MongoDB存储，减轻MySQL负担； • 这种方式虽然可以暂时解决问题，我们自己用也没有任何 问题，可以结合各自数据库优点，发挥性能。但是我们有 很多客户是需要私有化部署数据库，让每家客户都接受这 种方式，会为甲方增加很多服务器以及运维成本，可能客 户数据量很少，也需要使用双数据库，更新运维都比较麻

.....................................................................1160 43. Frontend/Backend Protocol................................................................................................ ............................................................1190 43.6. Summary of Changes since Protocol 2.0...................................................................1191 44. PostgreSQL Coding ); 5.7.3. The Schema Search Path Qualified names are tedious to write, and it’s often best not to wire a particular schema name into applica- tions anyway. Therefore tables are often referred to by unqualified

.....................................................................1153 43. Frontend/Backend Protocol................................................................................................ ............................................................1183 43.6. Summary of Changes since Protocol 2.0...................................................................1184 44. PostgreSQL Coding ); 5.7.3. The Schema Search Path Qualified names are tedious to write, and it’s often best not to wire a particular schema name into applica- tions anyway. Therefore tables are often referred to by unqualified

.....................................................................1270 44. Frontend/Backend Protocol................................................................................................ ............................................................1300 44.6. Summary of Changes since Protocol 2.0...................................................................1301 45. PostgreSQL Coding ); 5.7.3. The Schema Search Path Qualified names are tedious to write, and it’s often best not to wire a particular schema name into applica- tions anyway. Therefore tables are often referred to by unqualified

.....................................................................1270 44. Frontend/Backend Protocol................................................................................................ ............................................................1300 44.6. Summary of Changes since Protocol 2.0...................................................................1301 45. PostgreSQL Coding ); 5.7.3. The Schema Search Path Qualified names are tedious to write, and it’s often best not to wire a particular schema name into applica- tions anyway. Therefore tables are often referred to by unqualified

.....................................................................1071 42. Frontend/Backend Protocol................................................................................................ ............................................................1101 42.6. Summary of Changes since Protocol 2.0...................................................................1103 43. PostgreSQL Coding ); 5.8.3. The Schema Search Path Qualified names are tedious to write, and it’s often best not to wire a particular schema name into applica- tions anyway. Therefore tables are often referred to by unqualified

.....................................................................1000 42. Frontend/Backend Protocol.............................................................................................1002 ............................................................1030 42.6. Summary of Changes since Protocol 2.0............................................................1031 43. PostgreSQL Coding Conventions ); 5.8.3. The Schema Search Path Qualified names are tedious to write, and it’s often best not to wire a particular schema name into applications anyway. Therefore tables are often referred to by unqualified

.....................................................................1793 46. Frontend/Backend Protocol................................................................................................ ..............................................................1806 46.3. Streaming Replication Protocol.................................................................................1806 46.4. Message ............................................................1827 46.7. Summary of Changes since Protocol 2.0...................................................................1828 47. PostgreSQL Coding

.....................................................................1681 46. Frontend/Backend Protocol.............................................................................................1683 ..............................................................1695 46.3. Streaming Replication Protocol..........................................................................1695 46.4. Message Data ............................................................1715 46.7. Summary of Changes since Protocol 2.0............................................................1716 47. PostgreSQL Coding Conventions

.....................................................................1415 45. Frontend/Backend Protocol................................................................................................ ............................................................1446 45.6. Summary of Changes since Protocol 2.0...................................................................1447 46. PostgreSQL Coding ); 5.7.3. The Schema Search Path Qualified names are tedious to write, and it’s often best not to wire a particular schema name into applica- tions anyway. Therefore tables are often referred to by unqualified