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负担； • 这种方式虽然可以暂时解决问题，我们自己用也没有任何 问题，可以结合各自数据库优点，发挥性能。但是我们有 很多客户是需要私有化部署数据库，让每家客户都接受这 种方式，会为甲方增加很多服务器以及运维成本，可能客 户数据量很少，也需要使用双数据库，更新运维都比较麻

Settings .................................................................................450 18.3.2. Security and Authentication.....................................................................452 18.4 .............................................................................520 20.5. Function Security................................................................................................ ...........................................................................................1530 SECURITY LABEL..........................................................................................

....................................................................................478 18.3.2. Security and Authentication............................................................................480 .............................................................................552 20.5. Function Security................................................................................................ ...........................................................................................1633 SECURITY LABEL..........................................................................................

....................................................................................285 17.3.2. Security and Authentication............................................................................286 report has security implications and you’d prefer that it not become immediately visible in public archives, don’t send it to pgsql-bugs. Security issues can be reported privately to <security@postgresql this chapter is concerned with adding features to the table definition to ensure data integrity, security, or convenience. If you are eager to fill your tables with data now you can skip ahead to Chapter

Settings............................................................................252 16.4.2.2. Security and Authentication...............................................................253 16.4.3. Resource this chapter is concerned with adding features to the table definition to ensure data integrity, security, or convenience. If you are eager to fill your tables with data now you can skip ahead to Chapter is equal to the session user, but it changes during the execution of functions with the attribute SECURITY DEFINER. In Unix parlance, the session user is the “real user” and the current user is the “effective

Connection Settings.....................................................................239 16.4.2.2. Security and Authentication........................................................240 16.4.3. Resource this chapter is concerned with adding features to the table definition to ensure data integrity, security, or convenience. If you are eager to fill your tables with data now you can skip ahead to Chapter is equal to the session user, but it changes during the execution of functions with the attribute SECURITY DEFINER. In Unix parlance, the session user is the “real user” and the current user is the “effective

....................................................................................284 17.3.2. Security and Authentication............................................................................285 report has security implications and you’d prefer that it not become immediately visible in public archives, don’t send it to pgsql-bugs. Security issues can be reported privately to <security@postgresql this chapter is concerned with adding features to the table definition to ensure data integrity, security, or convenience. If you are eager to fill your tables with data now you can skip ahead to Chapter

....................................................................................298 17.3.2. Security and Authentication............................................................................300 report has security implications and you’d prefer that it not become immediately visible in public archives, don’t send it to pgsql-bugs. Security issues can be reported privately to <security@postgresql this chapter is concerned with adding features to the table definition to ensure data integrity, security, or convenience. If you are eager to fill your tables with data now you can skip ahead to Chapter

....................................................................................298 17.3.2. Security and Authentication............................................................................300 report has security implications and you’d prefer that it not become immediately visible in public archives, don’t send it to pgsql-bugs. Security issues can be reported privately to <security@postgresql this chapter is concerned with adding features to the table definition to ensure data integrity, security, or convenience. If you are eager to fill your tables with data now you can skip ahead to Chapter

Settings .................................................................................384 18.3.2. Security and Authentication.....................................................................386 x 18 ............................................................1653 E.23.3.2.2. Authentication and security..........................................1653 E.23.3.2.3. pg_hba.conf.......................... handling .........................................................................2081 F.23.6.3. Security limitations....................................................................2081 F.23.6.4. Useful