your requirements? Postgres Conference China 2016 中国用户大会 What are your requirements? • Is the workload for OLTP, OLAP or is it mixed? • What percentage of transactions are read-only vs. write? • If server • Use streaming replication Postgres Conference China 2016 中国用户大会 Read-Only / Read-Mainly Workload • Use streaming replication • Use application-level defined read-only connections or something Applications need data location awareness Postgres Conference China 2016 中国用户大会 OLTP – Write-Heavy Workload • Use custom sharding such as schema-level • PL/Proxy • Postgres-XL Strong Consistency Required

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly TABLE accounts (manager text, company text, contact_email text); ALTER TABLE accounts ENABLE ROW LEVEL SECURITY; CREATE POLICY account_managers ON accounts TO managers USING (manager = current_user);

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly TABLE accounts (manager text, company text, contact_email text); ALTER TABLE accounts ENABLE ROW LEVEL SECURITY; CREATE POLICY account_managers ON accounts TO managers USING (manager = current_user);

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly TABLE accounts (manager text, company text, contact_email text); ALTER TABLE accounts ENABLE ROW LEVEL SECURITY; CREATE POLICY account_managers ON accounts TO managers USING (manager = current_user);

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly TABLE accounts (manager text, company text, contact_email text); ALTER TABLE accounts ENABLE ROW LEVEL SECURITY; CREATE POLICY account_managers ON accounts TO managers USING (manager = current_user);

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly the products table contained a reference to a product manager, and the product manager entry gets deleted, then setting the product's product manager to null or a default might be useful. The actions SET

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly the products table contained a reference to a product manager, and the product manager entry gets deleted, then setting the product's product manager to null or a default might be useful. The actions SET

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly the products table contained a reference to a product manager, and the product manager entry gets deleted, then setting the product's product manager to null or a default might be useful. 71 Data Definition

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly the products table contained a reference to a product manager, and the product manager entry gets deleted, then setting the product's product manager to null or a default might be useful. The actions SET

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly the products table contained a reference to a product manager, and the product manager entry gets deleted, then setting the product's product manager to null or a default might be useful. The actions SET