消费，即在未来的调用中还会返回这些改变。 2016Postgres中国用户大会 Postgres Conference China 2016 中国用户大会 使用限制 目前不支持DDL的解析, 只有DML的解析 如：create，drop TEMPORARY表和UNLOGGED表不会被复制 表必须有主键或者唯一约束，否则像update或 者delete这样的操作无法被复制 2016Postgres中国用户大会

log. Therefore, the following actions will produce error messages: • Data Manipulation Language (DML): INSERT, UPDATE, DELETE, MERGE, COPY FROM, TRUN- CATE. Note that there are no allowed actions that cannot be taken without updating the underlying data files. • Rules on SELECT statements that generate DML commands. • LOCK that explicitly requests a mode higher than ROW EXCLUSIVE MODE. • LOCK in short By default, all op- eration types are replicated. These publication specifications apply only for DML operations; they do not affect the initial data synchronization copy. (Row filters have no effect for

log. Therefore, the following actions will produce error messages: • Data Manipulation Language (DML): INSERT, UPDATE, DELETE, MERGE, COPY FROM, TRUN- CATE. Note that there are no allowed actions that 786 High Availability, Load Balancing, and Replication • Rules on SELECT statements that generate DML commands. • LOCK that explicitly requests a mode higher than ROW EXCLUSIVE MODE. • LOCK in short types. By default, all operation types are replicated. These publication specifications apply only for DML operations; they do not affect the initial data synchronization copy. (Row filters have no effect for

messages: 809 High Availability, Load Balancing, and Replication • Data Manipulation Language (DML): INSERT, UPDATE, DELETE, MERGE, COPY FROM, TRUN- CATE. Note that there are no allowed actions that cannot be taken without updating the underlying data files. • Rules on SELECT statements that generate DML commands. • LOCK that explicitly requests a mode higher than ROW EXCLUSIVE MODE. • LOCK in short types. By default, all operation types are replicated. These publication specifications apply only for DML operations; they do not affect the initial data synchronization copy. (Row filters have no effect for

log. Therefore, the following actions will produce error messages: • Data Manipulation Language (DML): INSERT, UPDATE, DELETE, MERGE, COPY FROM, TRUN- CATE. Note that there are no allowed actions that High Availability, Load Bal- ancing, and Replication • Rules on SELECT statements that generate DML commands. • LOCK that explicitly requests a mode higher than ROW EXCLUSIVE MODE. • LOCK in short By default, all op- eration types are replicated. These publication specifications apply only for DML operations; they do not affect the initial data synchronization copy. (Row filters have no effect for

log. Therefore, the following actions will produce error messages: • Data Manipulation Language (DML): INSERT, UPDATE, DELETE, MERGE, COPY FROM, TRUN- CATE. Note that there are no allowed actions that cannot be taken without updating the underlying data files. • Rules on SELECT statements that generate DML commands. • LOCK that explicitly requests a mode higher than ROW EXCLUSIVE MODE. • LOCK in short types. By default, all operation types are replicated. These publication specifications apply only for DML operations; they do not affect the initial data synchronization copy. (Row filters have no effect for

log. Therefore, the following actions will produce error messages: • Data Manipulation Language (DML): INSERT, UPDATE, DELETE, MERGE, COPY FROM, TRUN- CATE. Note that there are no allowed actions that cannot be taken without updating the underlying data files. • Rules on SELECT statements that generate DML commands. • LOCK that explicitly requests a mode higher than ROW EXCLUSIVE MODE. • LOCK in short By default, all op- eration types are replicated. These publication specifications apply only for DML operations; they do not affect the initial data synchronization copy. (Row filters have no effect for

log. Therefore, the following actions will produce error messages: • Data Manipulation Language (DML) - INSERT, UPDATE, DELETE, COPY FROM, TRUNCATE. Note that there are no allowed actions that result cannot be taken without updating the underlying data files. • Rules on SELECT statements that generate DML commands. • LOCK that explicitly requests a mode higher than ROW EXCLUSIVE MODE. • LOCK in short should be carefully investigated. 31.3. Conflicts Logical replication behaves similarly to normal DML operations in that the data will be updated even if it was changed locally on the subscriber node.

log. Therefore, the following actions will produce error messages: • Data Manipulation Language (DML) - INSERT, UPDATE, DELETE, COPY FROM, TRUNCATE. Note that there are no allowed actions that result cannot be taken without updating the underlying data files. • Rules on SELECT statements that generate DML commands. • LOCK that explicitly requests a mode higher than ROW EXCLUSIVE MODE. • LOCK in short should be carefully investigated. 31.3. Conflicts Logical replication behaves similarly to normal DML operations in that the data will be updated even if it was changed locally on the subscriber node.

log. Therefore, the following actions will produce error messages: • Data Manipulation Language (DML) - INSERT, UPDATE, DELETE, COPY FROM, TRUNCATE. Note that there are no allowed actions that result cannot be taken without updating the underlying data files. • Rules on SELECT statements that generate DML commands. • LOCK that explicitly requests a mode higher than ROW EXCLUSIVE MODE. • LOCK in short should be carefully investigated. 31.3. Conflicts Logical replication behaves similarly to normal DML operations in that the data will be updated even if it was changed locally on the subscriber node.