Distributed PostgreSQL as an extension

cituscitus-extensiondatabasedatabase-clusterdistributed-databasemulti-tenantpostgrespostgresqlrelational-databasescaleshardingsql

Marco Slot 52f11223e5 Drop shards when a distributed table is dropped ... After this change, shards and associated metadata are automatically dropped when running DROP TABLE on a distributed table, which fixes #230. It also adds schema support for master_apply_delete_command, which fixes #73. Dropping the shards happens in the master_drop_all_shards UDF, which is called from the SQL_DROP trigger. Inside the trigger, the table is no longer visible and calling master_apply_delete_command directly wouldn't work and oid <-> name mappings are not available. The master_drop_all_shards function therefore takes the relation id, schema name, and table name as parameters, which can be obtained from pg_event_trigger_dropped_objects() in the SQL_DROP trigger. If the user calls master_drop_all_shards while the table still exists, the schema name and table name are ignored. Author: Marco Slot Reviewed-By: Andres Freund		2016-02-16 10:54:29 +01:00
src	Drop shards when a distributed table is dropped	2016-02-16 10:54:29 +01:00
.gitattributes	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00
.gitignore	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00
.travis.yml	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00
Makefile	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00
Makefile.global.in	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00
autogen.sh	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00
configure	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00
configure.in	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00
prep_buildtree	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00