58 Commits (e9a7295ead49d7a75771082f92ec7668e57de090)

Author	SHA1	Message	Date
Murat Tuncer	938546b938	Add router plannable check and router planning logic ... for single shard select queries	2016-04-21 09:15:33 +03:00
Brian Cloutier	35bbc1dbfd	Treat nodePort as the 64bit integer it is	2016-04-15 11:29:36 -07:00
Jason Petersen	423e6c8ea0	Update copyright dates ... Fixed configure variable and updated all end dates to 2016.	2016-03-23 17:14:37 -06:00
Marco Slot	75a141a7c6	Merge remote-tracking branch 'origin/master' into feature/drop_shards_on_drop_table	2016-02-17 22:52:58 +01:00
Marco Slot	2af6797c04	Perform relcache invalidation in CitusInvalidateRelcacheByRelid	2016-02-16 12:59:38 +01:00
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
Jason Petersen	fdb37682b2	First formatting attempt ... Skipped csql, ruleutils, readfuncs, and functions obviously copied from PostgreSQL. Seeing how this looks, then continuing.	2016-02-15 23:29:32 -07:00
Onder Kalaci	136306a1fe	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00