citus

Commit Graph

Author	SHA1	Message	Date
Marco Slot	78866df13c	Remove master_append_table_to_shard UDF	2021-11-08 10:43:24 +01:00
Onder Kalaci	82a4830c7d	Adjust the existing regression tests	2020-12-15 18:17:10 +03:00
Hanefi Önaldı	b0a2c1ee5c	Disallow volatile functions on single shard update queries We currently do not support volatile functions in update/delete statements because the function evaluation logic does not know how to distinguish volatile functions (that need to be evaluated per row) from stable functions (that need to be evaluated per query), and it is also not safe to push the volatile functions down on replicated tables.	2020-09-29 15:40:21 +03:00
Onur Tirtir	3a73fba810	Apply planner changes for citus local tables	2020-09-09 11:51:18 +03:00
SaitTalhaNisanci	164c00cf08	Fix typo: longer visible -> no longer visible (#3803 )	2020-04-27 16:32:46 +03:00
Hanefi Önaldı	0c5d0cfee9	Notice message to help truncate local data after distribution	2020-04-17 13:21:34 +03:00
Jelte Fennema	7730bd449c	Normalize tests: Remove trailing whitespace	2020-01-06 09:32:03 +01:00
Jelte Fennema	6353c9907f	Normalize tests: Line info varies between versions	2020-01-06 09:32:03 +01:00
Jelte Fennema	7f3de68b0d	Normalize tests: header separator length	2020-01-06 09:32:03 +01:00
Jelte Fennema	8c5c0dd74c	Normalize tests: s/localhost:[0-9]+/localhost:xxxxx/g	2020-01-03 11:40:50 +01:00
Marco Slot	ba39d72fe1	Fix incorrect union all pushdown issue	2020-01-01 09:03:50 +01:00
Marco Slot	486c620a3c	Fix inserts into local tables with distributed subqueries	2019-12-10 10:17:18 +01:00
Jelte Fennema	01da11f264	Change citus truncate trigger to AFTER and add more upgrade tests (#3070 ) * Add more upgrade tests * Fix citus trigger generation after upgrade citus_truncate_trigger runs before truncate when created by create_distributed_table: `492d1b2cba/src/backend/distributed/commands/create_distributed_table.c (L1163)` * Remove pg_dist_jobid_seq	2019-10-07 16:43:04 +02:00
Onder Kalaci	5d68a13139	Add order by to multi_shard_update_delete	2019-05-02 20:09:33 +03:00
Onder Kalaci	004f28e18c	Sort output of RETURNING The feature is only intended for getting consistent outputs for the regression tests. RETURNING does not have any ordering gurantees and with unified executor, the ordering of query executions on the shards are also becoming unpredictable. Thus, we're enforcing ordering when a GUC is set. We implicitly add an `ORDER BY` something equivalent of ` RETURNING expr1, expr2, .. ,exprN ORDER BY expr1, expr2, .. ,exprN ` As described in the code comments as well, this is probably not the most performant approach we could implement. However, since we're only targeting regression tests, I don't see any issues with that. If we decide to expand this to a feature to users, we should revisit the implementation and improve the performance.	2019-04-24 11:51:19 +03:00
Onder Kalaci	298e95c441	Add order by multi_shard_update_delete	2019-04-09 12:41:46 +03:00
Marco Slot	61d2c0f618	Stabilise output of multi_shard_update_delete test	2018-05-11 08:33:23 +02:00
velioglu	caa27161ca	Check volatile functions in modify queries	2018-05-08 11:16:40 +03:00
Marco Slot	90cdfff602	Implement recursive planning for DML statements	2018-05-03 14:42:28 +02:00
velioglu	32bcd610c1	Support modify queries with multiple tables With this commit we begin to support modify queries with multiple tables if these queries are pushdownable.	2018-05-02 16:22:26 +03:00
velioglu	72dfe4a289	Adds colocation check to local join	2018-04-04 22:49:27 +03:00
Metin Doslu	bcf660475a	Add support for modifying CTEs	2018-02-27 15:08:32 +02:00
mehmet furkan şahin	314fc09d90	regression test shard_count is changed from 32 to 4	2017-11-20 12:47:49 +03:00
Marco Slot	89eb833375	Use citus.next_shard_id where practical in regression tests	2017-11-15 10:12:05 +01:00
velioglu	0b5db5d826	Support multi shard update/delete queries	2017-10-25 15:52:38 +03:00

25 Commits (bbe1b161252e1cd7d77540c87fe42e333b6cdefd)