6 Commits (1f5379457a0dec9d2c8e90d8e6c10c8d903a332c)

Author	SHA1	Message	Date
Brian Cloutier	1f5379457a	Clear metadata_cache upon DROP EXTENSION ... When we notice that pg_dist_partition is being invalidated we assume that the citus extension is being dropped and drop state such as extensionLoaded and the cached oids of all the metadata tables. This frees the user from needing to reconnect after running DROP EXTENSION, so we also no longer send a warning message.	2016-04-22 07:25:49 -07:00
Marco Slot	4a3b6a8ab7	Rename citusdb to citus in regression test output	2016-02-17 23:33:30 +01:00
Marco Slot	58351fb128	Merge remote-tracking branch 'origin/master' into feature/drop_shards_on_drop_table	2016-02-17 22:52:58 +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
Murat Tuncer	c1d377b7d2	Changed product name to citus ... All citusdb references in - extension, binary names - file headers - all configuration name prefixes - error/warning messages - some functions names - regression tests are changed to be citus.	2016-02-15 16:04:31 +02:00
Onder Kalaci	136306a1fe	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00