1PG_AUTOCTL ACTIVATE(1) pg_auto_failover PG_AUTOCTL ACTIVATE(1)
2
3
4
6 pg_autoctl activate - pg_autoctl activate
7
8 pg_autoctl activate - Activate a Citus worker from the Citus coordina‐
9 tor
10
12 This command calls the Citus “activation” API so that a node can be
13 used to host shards for your reference and distributed tables.
14
15 usage: pg_autoctl activate [ --pgdata ]
16
17 --pgdata path to data directory
18
20 When creating a Citus worker, pg_autoctl create worker automatically
21 activates the worker node to the coordinator. You only need this com‐
22 mand when something unexpected have happened and you want to manually
23 make sure the worker node has been activated at the Citus coordinator
24 level.
25
26 Starting with Citus 10 it is also possible to activate the coordinator
27 itself as a node with shard placement. Use pg_autoctl activate on your
28 Citus coordinator node manually to use that feature.
29
30 When the Citus coordinator is activated, an extra step is then needed
31 for it to host shards of distributed tables. If you want your coordina‐
32 tor to have shards, then have a look at the Citus API
33 citus_set_node_property to set the shouldhaveshards property to true.
34
36 --pgdata
37 Location of the Postgres node being managed locally. Defaults to
38 the environment variable PGDATA. Use --monitor to connect to a
39 monitor from anywhere, rather than the monitor URI used by a lo‐
40 cal Postgres node managed with pg_autoctl.
41
43 Microsoft
44
46 Copyright (c) Microsoft Corporation. All rights reserved.
47
48
49
50
512.0 Sep 13, 2023 PG_AUTOCTL ACTIVATE(1)