. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4 Features 18 4.1 DB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.1.1 Background . 27 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Data Node 348 7.8.10 [Sharding] If sharding database is partial, should tables without sharding database & table configured in sharding rules? . . . . . . . . . . . . . . . . . . 348 7.8.11 [Sharding] When generic

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4 Features 18 4.1 DB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.1.1 Background . 27 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Data Node 360 7.8.10 [Sharding] If sharding database is partial, should tables without sharding database & table configured in sharding rules? . . . . . . . . . . . . . . . . . . 360 7.8.11 [Sharding] When generic

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4 Features 18 4.1 DB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.1.1 Background . 24 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Data Node Shadow DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Shadow Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Shadow Algorithm .

23 8.1.6 Core Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Data Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 12 Reference 520 12.1 Database Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 12.2 Database Gateway 578 13.3.3 Sharding If sharding database is partial, should tables without sharding database & table configured in sharding rules? . . . . . . . . . . . . . . . . . . . . . . . 578 13.3.4 Sharding When

23 8.1.6 Core Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Data Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 489 12 Reference 491 ix 12.1 Database Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 12.2 Database Gateway 550 13.4.3 Sharding If sharding database is partial, should tables without sharding database & table configured in sharding rules? . . . . . . . . . . . . . . . . . . . . . . . 550 13.4.4 Sharding When

20 3.1.6 Core Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Data Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 7 Reference 354 7.1 Database Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 7.2 Database Gateway expression?457 8.3.3 Sharding If sharding database is partial, should tables without sharding database & table configured in sharding rules? . . . . . . . . . . . . . . . . . . . . . . . 457 8.3.4 Sharding When

19 3.1.6 Core Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Data Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 7 Reference 381 7.1 Database Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 7.2 Database Gateway expression?496 8.3.3 Sharding If sharding database is partial, should tables without sharding database & table configured in sharding rules? . . . . . . . . . . . . . . . . . . . . . . . 496 8.3.4 Sharding When

. . . . . . 294 7.6 If sharding database is partial, should tables without sharding database & table be con‐ figured in sharding rules? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Apache ShardingSphere document, v5.0.0-beta 1.2 Features 1.2.1 Data Sharding • Database sharding & Table sharding • Replica query • Sharding strategy customization • Centre‐less Distributed primary key exceeding affordable threshold. What’s more, database sharding can also effectively disperse TPS. Table sharding, though cannot ease the database pressure, can provide possibilities to transfer distributed

UNINSTALL COMPONENT ‘file://component1’, ‘file://component2’ REPAIR TABLE t_order OPTIMIZE TABLE t_order CHECKSUM TABLE t_order CHECK TABLE t_order SET RESOURCE GROUP group_name DROP RESOURCE GROUP group_name AGGREGATE my_avg(int4) (stype = avg_state, sfunc = avg_transfn, finalfunc = avg_finalfn) CREATE TABLE agg_data_2k AS SELECT g FROM generate_series(0, 1999) g; CREATE SCHEMA alt_nsp1; ALTER AGGREGATE def_view_test DO INSTEAD INSERT INTO def_test SELECT new.* ALTER TABLE alterlock SET (toast.autovacuum_enabled = off) CREATE PUBLICATION pub1 FOR TABLE alter1.t1, ALL TABLES IN SCHEMA alter2 PostgreSQL PostgreSQL

UNINSTALL COMPONENT ‘file://component1’, ‘file://component2’ REPAIR TABLE t_order OPTIMIZE TABLE t_order CHECKSUM TABLE t_order CHECK TABLE t_order SET RESOURCE GROUP group_name DROP RESOURCE GROUP group_name AGGREGATE my_avg(int4) (stype = avg_state, sfunc = avg_transfn, finalfunc = avg_finalfn) CREATE TABLE agg_data_2k AS SELECT g FROM generate_series(0, 1999) g; CREATE SCHEMA alt_nsp1; ALTER AGGREGATE def_view_test DO INSTEAD INSERT INTO def_test SELECT new.* ALTER TABLE alterlock SET (toast.autovacuum_enabled = off) CREATE PUBLICATION pub1 FOR TABLE alter1.t1, ALL TABLES IN SCHEMA alter2 PostgreSQL PostgreSQL