external
/
citus
mirror of https://github.com/citusdata/citus.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
6,748 Commits
645 Branches
162 Tags
103 MiB
Commit Graph

13 Commits (f4a79dc2208263451bbd32369139f2e1b9c894d0)

Author SHA1 Message Date
Onur Tirtir f4a79dc220 improve test 2023-10-30 16:20:25 +03:00
Onur Tirtir d00fec9aef make multi_size_queries rerunnable 2023-10-30 16:20:25 +03:00
Cédric Villemain 526cdaa6d6 Fix partitionned index + test 
adding more tests suggested by Onur Tirtir, found and fixed a related bug.
 2023-10-29 19:30:17 +01:00
Cédric Villemain 2c92cc08d7 Update SQL test for citus_*_size 
Add just some test for index on distributed table.
 2023-10-25 16:01:22 +02:00
Onder Kalaci 549edcabb6 Allow disabling node(s) when multiple failures happen 
As of master branch, Citus does all the modifications to replicated tables
(e.g., reference tables and distributed tables with replication factor > 1),
via 2PC and avoids any shardstate=3. As a side-effect of those changes,
handling node failures for replicated tables change.

With this PR, when one (or multiple) node failures happen, the users would
see query errors on modifications. If the problem is intermitant, that's OK,
once the node failure(s) recover by themselves, the modification queries would
succeed. If the node failure(s) are permenant, the users should call
`SELECT citus_disable_node(...)` to disable the node. As soon as the node is
disabled, modification would start to succeed. However, now the old node gets
behind. It means that, when the node is up again, the placements should be
re-created on the node. First, use `SELECT citus_activate_node()`. Then, use
`SELECT replicate_table_shards(...)` to replicate the missing placements on
the re-activated node.
 2021-12-01 10:19:48 +01:00
Marco Slot 4098d33acb Allow citus size functions on replicated tables 2020-12-03 16:33:24 +01:00
Philip Dubé c563e0825c Strip trailing whitespace and add final newline (#3186) 
This brings files in line with our editorconfig file
 2019-11-21 14:25:37 +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
Jason Petersen a2c6f596f9 Address code review comments 2019-03-21 11:59:52 -06:00
Marco Slot 9318aeee6b Allow multiple size function calls per query 2018-04-12 14:16:17 +02:00
Marco Slot 89eb833375 Use citus.next_shard_id where practical in regression tests 2017-11-15 10:12:05 +01:00
Marco Slot 0b579d027a Check whether relation ID exists in citus_relation_size 2017-04-29 01:39:39 +02:00
velioglu e32aff1a26 Size UDFs implemented 
citus_table_size, citus_relation_size and citus_total_relation_size UDFs are implemented.
 2017-03-16 13:50:30 +03:00