Determines weather the service mode is enabled in a BiHA cluster.

You can set the value with the biha.service_mode function.

Possible values:

Specifies the path to the SSL public certificate used to secure service connections between nodes of the initialized BiHA cluster. For more information, refer to Managing SSL for Service Connections.

You can set the value with the biha.set_ssl_certificate function. Node restart is required for the changes to take effect.

Default value: /PGDATA/pg_biha/biha_pub_cert.pem

Specifies the authentication mode for the biha_replication_user role. For more information about SSL authentication configuration, refer to Configuring SSL for biha_replication_user. For more information about modes, refer to sslmode.

You can set the value with the biha.set_ssl_mode function. Node restart is required for the changes to take effect.

Possible values:

Specifies the path to the SSL private key used to secure service connections between nodes of the initialized BiHA cluster. For more information, refer to Managing SSL for Service Connections.

You can set the value with the biha.set_ssl_private_key function. Node restart is required for the changes to take effect.

Default value: /PGDATA/pg_biha/biha_priv_key.pem

Enables quorum-based synchronous replication by setting the synchronous_standby_names parameter and specifying the number of synchronous standbys (quorum) with the ANY method.

You can set the value with the biha.set_sync_standbys function.

The value must be integer and greater than zero, as well as higher than the value of synchronous_standby_names.min parameter if set, and must not exceed the number of followers excluding referee. It is recommended to set the synchronous_standby_names.count value less than the value of minnodes.

Enables relaxed quorum-based synchronous replication by specifying the MIN field value of the synchronous_standby_names parameter, which is the minimum number of synchronous standbys that must be available for the leader node to continue confirming transactions. If the parameter value is not specified, the BiHA cluster operates according to the default synchronous replication restrictions, i.e. the leader node is not available for write transactions until all followers catch up with its current state.

You can set the value with the biha.set_sync_standbys_min function.

The synchronous_standby_names.min value must be integer and equal to or greater than zero, as well as lower than synchronous_standby_names.count. When set to -1, relaxed quorum-based synchronous replication is disabled.

Specifies a list of synchronous standbys in the synchronous_standby_names configuration parameter.

You can set the value with the biha.set_ssn function, as well as modify the list of synchronous standbys with biha.add_to_ssn or biha.get_ssn functions.

Specifies whether to use the protected mode of the service information exchange between cluster nodes with SSL/TLS over the biha control channel. For more information, refer to Managing SSL for Service Connections.

You can set the value with the biha.set_use_ssl function. Node restart is required for the changes to take effect.

Possible values:

Specifies the path to the SSL public certificate used for the biha_replication_user role authentication. For more information about SSL authentication configuration, refer to Configuring SSL for biha_replication_user.

You can set the value with the biha.set_user_cert function.

Specifies the path to the SSL private key used for the biha_replication_user role authentication. For more information about SSL authentication configuration, refer to Configuring SSL for biha_replication_user.

You can set the value with the biha.set_user_key function.

Specifies the maximum number of heartbeats that can be missed on BCP before the node is considered offline.

You can set the value with the biha.set_heartbeat_max_lost function.

Default value: 10

Minimal value: 3

Nodes in all states use the heartbeat timeout value calculated as heartbeat_max_lost * heartbeat_send_period to determine if other nodes are online. For example, if Node A receives no heartbeats from Node B within the heartbeat timeout, the Node B state changes to UNKNOWN in the biha.status_v view of Node A indicating that Node A considers Node B offline. The leader in the LEADER_RW state additionally uses the timeout specified in the no_wal_on_follower parameter.

Specifies the heartbeat sending frequency, in milliseconds.

You can set the value with the biha.set_heartbeat_send_period function.

Default value: 1000

Minimal value: 500

Nodes in all states use the heartbeat timeout value calculated as heartbeat_max_lost * heartbeat_send_period to determine if other nodes are online. For example, if Node A receives no heartbeats from Node B within the heartbeat timeout, the Node B state changes to UNKNOWN in the biha.status_v view of Node A indicating that Node A considers Node B offline. The leader in the LEADER_RW state additionally uses the timeout specified in the no_wal_on_follower parameter.

Specifies the minimum number of operational nodes for the leader node to be open for write transactions.

You can set the value with the biha.set_minnodes function.

Default value: equals nquorum

When setting up this value, consider the split-brain risk. It is recommended to use the following formula: (total_number_of_nodes + 1)/2. For example, if your cluster has 3 nodes, the minnodes value must be 2.

Nodes with the can_vote parameter set to false are ignored by minnodes.

Specifies the timeout of the replication slot position advancement, in milliseconds.

You can set the value with the biha.set_no_wal_on_follower function.

Default value: 20000

Minimum value: 5000

BiHA uses this configuration parameter for the following purposes:

Specifies the minimum number of nodes, which must vote for the new leader node if the current leader is down.

You can set the value with the biha.set_nquorum function.

Default value: 2

When setting up this value, consider the split-brain risk. It is recommended to use the following formula: (total_number_of_nodes + 1)/2. For example, if your cluster has 3 nodes, the nquorum value must be 2.

Nodes with the can_vote parameter set to false are ignored by nquorum.

Specifies the waiting time for execution of asynchronous operations, such as adding segments and removing nodes, in milliseconds. If a segment or node is not added or removed within the specified time, BiHA terminates the SQL command.

The parameter value must be the same on all cluster nodes.

You can set the value with the biha.set_asyncaction_timeout function.

Default value: 30000

Minimum value: 1000

Used by other nodes to connect to the current node by internal control channel (BCP), for example, using a proxy server or a tunnel. If the biha_hosts value is empty, by default, the biha_listen_addresses value of the current node is used.

You can set the value with the biha.set_biha_hosts function.

Possible values: one or several comma-separated addresses in the hostname:port format. port is an optional value, if not specified or set to -1, the biha_port value of the current node is used.

For example: biha-db-1:5433,biha-proxy:8081,biha-node-1

Determines on which addresses listening sockets are open for the internal BCP control channel.

You can set the value only with the bihactl utility.

Possible values: one or several comma-separated addresses in the hostname:port format. port is an optional value, if not specified or set to -1, the biha_port value of the current node is used.

For example: biha-db-1:5433,biha-proxy:8081,biha-node-1

Specifies the port used to exchange service information between nodes.

The parameter value is set with the bihactl utility and can be overridden when modifying biha_hosts, biha_listen_addresses, or replication_hosts configuration parameters.

Sets time for execution of all callbacks for a single event, in milliseconds.

You can set the value with the biha.set_callbacks_timeout.

Default value: 10000

Minimum value: 1000

Determines the timeout to broadcast message with cluster configuration.

You can set the value with the biha.set_config_send_period function.

Default value: 10000

Minimum value: 500

Specifies a list of nodes that cannot be used as replication sources for the current node. If a node identifier is in the list, the current node cannot replicate from such a node.

You can set the value with the biha.set_deny_wal_sources function.

Default value: empty

The deny_wal_sources configuration parameter has higher priority than repl_pref_roles. For example, if the leader node ID is in the deny_wal_sources list of a node, the node does not replicate from the leader even if its repl_pref_roles value is LF.

Determines whether a follower is available for read operations.

You can set the value with the biha.set_flw_ro function.

Possible values:

Determines whether BiHA monitors the xmin value of replication slots.

You can set the value with the biha.set_manage_slots_xmin function.

Possible values:

Specifies the maximum number of biha replication connections to a node, i.e. the maximum number of walsenders where application_name is biha_node_*. For more information, refer to Section 26.1.5.2.

You can set the value with the biha.set_max_replicas function.

The value must be integer, greater than zero, and must not exceed the max_wal_senders value.

Other possible values:

Specifies the node port for incoming connections to Postgres Pro.

The parameter value is set with the bihactl utility and can be overridden when modifying biha_hosts, biha_listen_addresses, or replication_hosts configuration parameters.

Used by other nodes to connect to the current node by replication channel. The biha_listen_addresses value must include replication_hosts. If the replication_hosts value is empty, by default, the biha_listen_addresses value of the current node is used.

You can set the value with the biha.set_replication_hosts function.

Possible values: one or several comma-separated addresses in the hostname:port format. port is an optional value, if not specified or set to -1, the biha_port value of the current node is used.

The maximum string size is 1024 bytes, otherwise it is ignored.

For example: biha-db-1:5433,biha-proxy:8081,biha-node-1

Used by other nodes to execute SQL queries to the current node. If the sql_hosts value is empty, by default, the replication_hosts value of the current node is used.

You can set the value with the biha.set_sql_hosts function.

Possible values: one or several comma-separated addresses in the hostname:port format. port is an optional value, if not specified or set to -1, the biha_port value of the current node is used.

The maximum string size is 1024 bytes, otherwise it is ignored.

For example: biha-db-1:5433,biha-proxy:8081,biha-node-1

Specifies the timeout for a node to stop accepting queries if the biha process does not respond, in seconds. For more information, refer to Section 26.3.9.

You can set the value with the biha.set_watchdog_timeout function. Node restart is required for the changes to take effect.

Default value: 2

Minimum value: 1

Determines the ability of a node or a segment to become the leader.

You can set the value with the biha.set_can_be_leader function.

Possible values:

A node that cannot become the leader may have the largest WAL. In this case, if elections are required, those nodes that can stand as candidates attempt to receive missing data from that node. If they succeed, one of these nodes becomes the leader. If they fail to receive missing data, the automatic rewind process is launched on the node that cannot become the leader. If biha.autorewind is not enabled, the node state changes to NODE_ERROR.

Determines whether a node or a segment is allowed to vote.

You can set the value with the biha.set_can_vote function.

Possible values:

Determines the maximum time for the switchover process to complete when biha.set_leader is called, in milliseconds. If the operation does not complete within the specified time, the node returns to the FOLLOWER state.

You can set the value with the biha.set_leader_timeout function.

Default value: 20000

Minimum value: 0

Specifies the operation mode of a node or segment. The mode value is set with bihactl and cannot be modified after cluster initialization.

Possible values for a node:

Possible values for a segment: regular

Specifies the name of a node or segment. The name value is set with bihactl and cannot be modified after cluster initialization.

Sets the node or segment priority that affects both elections and replication in a cluster, in seconds.

You can set the value with the biha.set_priority function.

The value must be integer and greater than or equal to zero. The 0 value means the highest priority.

Default value: -1, meaning that the parameter is ignored.

BiHA uses this configuration parameter for the following purposes:

Specifies the preferred role of a node acting as a replication source for the current node in a BiHA cluster with cascading replication.

You can set the value with the biha.set_pref_roles function.

Possible values: L (leader), F (follower), or R (referee), or their combinations. The value must be one to three symbols long and must not contain repeatable symbols. For example: L, F, LFR, or LF.

Default value: L, meaning that data is replicated from the leader or front follower depending on the segment where the node is located.

Controls the automatic rewind policy for that node, against which the pg_rewind must be executed. For example, for the old leader when synchronizing it with the new leader. For more information, refer to Automatic Cluster Synchronization after Failover.

Possible values:

Manages the automatic WAL trimming policy within a single node. For more information, refer to Automatic Cluster Synchronization after Failover.

Possible values:

Manages the WAL validation mechanism. The WAL validation procedure runs on history update and during the PRESTARTUP state to avoid the recovery process abortion caused by WAL inconsistency.

Possible values:

The WAL validation mechanism performs the following:

Adds a segment to the GDBiHA cluster. If parent_id is not specified, by default the root node with ID 1111 is assigned as the parent. For more information about changing cluster composition, refer to Section 26.3.1.

For example, add a segment with ID 222 to a cluster with ID 1111:

biha_db=# SELECT biha.add_node(222, 1111);
 add_node
-------------
 t
(1 row)
 

Sets the leader, front follower, or the leader segment manually. For more information about the manual switchover procedure, refer to Manual Switchover.

The following switchover modes are supported:

For example, nominate the node with ID 2 as the new leader in the immediate mode:

biha_db=# SELECT biha.set_leader(2, 'immediate');
 set_leader
-------------
 t
(1 row)

Sets the value of the leader_timeout configuration parameter.

The biha.set_leader_timeout function can be called for an individual physical node or a segment depending on the identifier specified. When called for a segment, the timeout value applies to all nodes within that segment.

For example, set the timeout of 10000 ms for all nodes in segment 222:

biha_db=# SELECT * FROM biha.set_leader_timeout(222, 10000);
 set_leader_timeout
-------------
 t
(1 row)

Removes a node or a segment from the cluster. Before removing, the node must be stopped. You cannot remove a node if it is a parent of another node. For more information about changing cluster composition, refer to Section 26.3.1.

For example, remove a node with ID 3:

biha_db=# SELECT biha.remove_node(3);
 remove_node
-------------
 t
(1 row)

Returns the configuration parameter values for every node and segment. You can also view the most critical configuration parameters using the Section 26.4.3.1 view.

The following parameters are displayed:

For example, call the biha.config function for a node with ID 1:

biha_db=# select * from biha.config() where id = 1 \gx
  -[ RECORD 1 ]---------+--------------------------
  id                    | 1
  nquorum               | 3
  minnodes              | 1
  heartbeat_send_period | 1000
  heartbeat_max_lost    | 10
  no_wal_on_follower    | 20000
  sync_standbys_min     | -2
  priority              | -1
  can_be_leader         | t
  can_vote              | t
  mode                  | regular
  proxima_enabled       | f
  name                  | biha_node_1
  repl_pref_roles       | L
  max_replicas          | 2147483647
  config_version        | 12
  parent_id             | 111
  service_mode          | f
  unit_type             | NODE
  deny_wal_sources      |
  biha_hosts            | biha-db-1:5433,biha-proxy:8081
  replication_hosts     | biha-db-1:5432,postgres-proxy:8081
  sql_hosts             |
  leader_timeout        | 20000
  use_ssl               | f
  ssl_certificate       | pg_biha/biha_pub_cert.pem
  ssl_private_key       | pg_biha/biha_priv_key.pem
  user_cert             |
  user_key              |
  ssl_mode              |
  flw_ro                | t
  callbacks_timeout     | 10000
  watchdog_timeout      | 2
  asyncaction_timeout   | 30000
  manage_slots_xmin     | t
  config_send_period    | 10000

Returns the configuration file content in the JSON format. To view the content of a JSON configuration tree branch at the specified JSON path, use the biha.get_option function.

For example:

biha_db=# select biha.config_json();
                      config_json
-------------------------------------------------------
 {                                                    +
     "unit": {                                        +
         "id": 1111,                                  +
         "mode": "regular",                           +
         "name": "biha_node_1111",                    +
         "nquorum": 1,                                +
         "can_vote": true,                            +
         "children": [                                +
             {                                        +
                 "id": 111,                           +
...
     "proxima_enabled": false,                        +
     "ssl_certificate": "pg_biha/biha_pub_cert.pem",  +
     "ssl_private_key": "pg_biha/biha_priv_key.pem",  +
     "synchronous_standby_names": {                   +
         "min": -2,                                   +
         "count": -1,                                 +
         "names": [                                   +
         ]                                            +
     }                                                +
}
(1 row)

Returns the content of a JSON configuration tree branch at the specified JSON path. To view the full JSON configuration file, use the biha.config_json function.

For example:

biha_db=# select biha.get_option('$.unit.children.[0].children.[1].biha_listen_addresses.[0].address');
 get_option
------------
 "node-3"
(1 row)

Sets the value of the config_send_period configuration parameter.

Returns the description of why the node transferred to the NODE_ERROR state. The returned record contains the type of the error, its details, the place it occurred specifying begin_lsn, end_lsn, and identifier of the current and the next timeline, as well as replay_lsn.

For example:

biha_db=# \x
biha_db=# SELECT * FROM biha.error_details();
-[ RECORD 1 ]--+-------------------------------------------------------------------------------------                 │
type           | TIMELINE_ERROR                                                                                       │
details        | Timeline divergence detected: current timeline ended before replayLSN, rewind needed                 │
next_tli       | 3                                                                                                    │
next_begin_lsn |                                                                                                      │
next_end_lsn   |                                                                                                      │
cur_tli        | 2                                                                                                    │
cur_begin_lsn  | 0/17F53A0                                                                                            │
cur_end_lsn    | 0/3455FC8                                                                                            │
replay_lsn     | 0/34593B8

Displays a table that contains the monitoring data about the current status of cluster nodes. The table consists of the following columns:

For example:

biha_db=# select * from biha.monitoring();
 id |          time          |   biha_state   | pg_state | online | startup_progress
----+------------------------+----------------+----------+--------+-----------------
  3 | 2025-09-02 13:49:57+03 | LEADER_RW      | Promoted | t      |
  1 | 2025-09-02 13:49:57+03 | CSTATE_FORMING | Startup  | t      |               81
  2 | 2025-09-02 13:49:57+03 | FOLLOWER       | Recovery | t      |
(3 rows)

Displays the BiHA transport channel state of the current node to other nodes and defines the biha.nodes_v view, which is described in detail in the biha.nodes_v section.

The function displays a table with the following columns:

For example:

biha_db=# SELECT * FROM biha.nodes();
 id |   host    | port  | state  |       conn_start       | conn_count
----+-----------+-------+--------+------------------------+------------
  1 | localhost | 10001 | ACTIVE | 2023-07-05 17:17:17+07 |          1
  2 | localhost | 10002 |        |                        |
  5 | localhost | 10005 | ACTIVE | 2023-07-05 17:17:17+07 |          1
  3 | localhost | 10003 | ACTIVE | 2023-07-05 17:17:17+07 |          1
  4 | localhost | 10004 | ACTIVE | 2023-07-05 17:17:17+07 |          1
(4 rows)

Defines the biha.status_v view, which is described in detail in the biha.status_v section. It is not recommended to use this function as it provides raw data for the view.

Adds the specified node to the list of synchronous standbys listed by synchronous_standby_names.names. You must specify the node whose name is not yet in the list.

For example:

biha_db=# SELECT biha.add_to_ssn(3);
 add_to_ssn
-------------
 t
(1 row)

Displays the current value of the synchronous_standby_names parameter.

For example:

biha_db=# SELECT biha.get_ssn();
                   get_ssn
---------------------------------------------
 ANY 1 (biha_node_1,biha_node_2,biha_node_3)
(1 row)

Sets the value of the deny_wal_sources configuration parameter for a specified node or resets the existing value.

The prohibited_ids array must meet the following requirements:

For example, you can prevent the node with ID 3 to replicate from the node with ID 1 as follows:

biha_db=# SELECT biha.set_deny_wal_sources(3, ARRAY[1]);
 set_deny_wal_sources
--------------
 t
(1 row)

To reset the parameter to an empty value, call the function with an empty array.

Sets the value of the max_replicas configuration parameter.

For example, configure the node with ID 1 to have the maximum of 3 replicas:

biha_db=# SELECT biha.set_max_replicas(1, 3);
 set_max_replicas
------------------
 t
(1 row)

Sets the value of the repl_pref_roles configuration parameter.

For example:

biha_db=# SELECT biha.set_pref_roles(1, 'LFR');
 set_pref_roles
----------------
 t
(1 row)

Sets the value of the priority configuration parameter.

For example:

biha_db=# SELECT biha.set_priority(1, 10);
 set_priority
--------------
 t
(1 row)

Removes the specified node from the list of synchronous standbys listed by synchronous_standby_names.names. You must specify the node which name is already in the list.

For example:

biha_db=# SELECT biha.remove_from_ssn(3);
  remove_from_ssn
-------------
 t
(1 row)

Sets the value of the synchronous_standby_names.names configuration parameter.

For example:

biha_db=# SELECT biha.set_ssn(1, 2, 3);
 set_ssn
---------
 t
(1 row)

Sets the value of the synchronous_standby_names.count configuration parameter.

For example:

biha_db=# SELECT biha.set_sync_standbys(1);
 set_sync_standbys
-------------------
 t
(1 row)

Sets the value of the synchronous_standby_names.min configuration parameter.

Using this function, you can also manage relaxed quorum-based synchronous replication. To disable relaxed quorum-based synchronous replication, set the -1 value.

For example:

biha_db=# SELECT biha.set_sync_standbys_min(1);
 set_sync_standbys_min
-----------------------
 f
(1 row)

Sets the value of the minnodes configuration parameter. If id belongs to a physical node, the minnodes value is set for the segment where the node is located. If id belongs to a segment, the value is set for this segment and the nodes located in it. You can set different values for each segment.

For example:

  biha_db=# SELECT biha.set_minnodes(3, 1);
   set_minnodes
  --------------------------
   t
  (1 row)
  

Sets the value of the nquorum configuration parameter. If id belongs to a physical node, the nquorum value is set for the segment where the node is located. If id belongs to a segment, the value is set for this segment and the nodes located in it. You can set different values for each segment.

For example:

  biha_db=# SELECT biha.set_nquorum(3, 3);
   set_nquorum
  --------------------------
   t
  (1 row)
  

Sets nquorum and minnodes values. If id belongs to a physical node, the nquorum and minnodes values are set for the segment where the node is located. If id belongs to a segment, the values are set for this segment and the nodes located in it. You can set different values for each segment.

For example:

  biha_db=# SELECT biha.set_nquorum_and_minnodes(3, 3, 1);
   set_nquorum_and_minnodes
  --------------------------
   t
  (1 row)
  

Sets the value of the can_be_leader configuration parameter.

For example, you can allow the node with ID 4 to become a leader candidate as follows:

biha_db=# SELECT biha.set_can_be_leader(4,true);
 set_can_be_leader
--------------
 t
(1 row)

Sets the value of the can_vote configuration parameter.

For example, you can allow the node with ID 4 to vote as follows:

biha_db=# SELECT biha.set_can_vote(4,true);
 set_can_vote
--------------
 t
(1 row)

Displays the current values of network configuration parameters for physical nodes only. In the output, the biha_listen_addresses value is displayed for other network configuration parameter if their values were not specified.

For example:

  biha_db=# select * from biha.config_network();
    id | biha_listen_addresses | biha_hosts | biha_port | replication_hosts | sql_hosts | port
   ----+-----------------------+------------+-----------+-------------------+-----------+------
     1 | biha-db-1             | biha-db-1  |      5433 | biha-db-1         | biha-db-1 | 5432
     2 | biha-db-2             | biha-db-2  |      5433 | biha-db-2         | biha-db-2 | 5432
     3 | biha-db-3             | biha-db-3  |      5433 | biha-db-3         | biha-db-3 | 5432
     4 | biha-db-4             | biha-db-4  |      5433 | biha-db-4         | biha-db-4 | 5432
     5 | biha-db-5             | biha-db-5  |      5433 | biha-db-5         | biha-db-5 | 5432
  (5 rows)
  

Sets the value of the biha_hosts configuration parameter.

For example:

biha_db=# select biha.set_biha_hosts(1, 'biha-1:8080', 'biha-p', 'biha-2222:3333');
 set_biha_hosts
----------------
 t
(1 row)

Sets the value of the sql_hosts configuration parameter.

For example:

biha_db=# select biha.set_sql_hosts(1, 'bha-1:8080', 'bha-p', 'bha-2222:3333');
 set_sql_hosts
----------------
 t
(1 row)

Sets the value of the replication_hosts configuration parameter.

For example:

biha_db=# select biha.set_replication_hosts(1, 'bha-1:8080', 'bha-p', 'bha-2222:3333');
 set_replication_hosts
-----------------------
 t
(1 row)

Sets the value of the ssl_certificate configuration parameter.

For example:

biha_db=# SELECT biha.set_ssl_certificate('/tmp/install/share/extension/biha_pub_cert.pem');
WARNING:  [BiHA] this parameter takes effect after node restart
 set_ssl_certificate
---------------------
 t
(1 row)

Sets the value of the ssl_mode configuration parameter.

For example:

biha_db=# SELECT biha.set_ssl_mode('verify-full');
WARNING:  [BiHA] this parameter takes effect after node restart
 set_ssl_mode
--------------
 t
(1 row)

Sets the value of the ssl_private_key configuration parameter.

For example:

biha_db=# SELECT biha.set_ssl_private_key('/tmp/install/share/extension/biha_priv_key.pem');
WARNING:  [BiHA] this parameter takes effect after node restart
 set_ssl_private_key
---------------------
 t
(1 row)

Sets the value of the user_biha_cert configuration parameter.

For example:

biha_db=# SELECT biha.set_user_cert('/tmp/install/share/extension/biha_pub_cert.pem');
WARNING:  [BiHA] this parameter takes effect after node restart
 set_user_cert
---------------
 t
(1 row)

Sets the value of the user_biha_key configuration parameter.

For example:

biha_db=# SELECT biha.set_user_key('/tmp/install/share/extension/biha_priv_key.pem');
WARNING:  [BiHA] this parameter takes effect after node restart
 set_user_key
--------------
 t
(1 row)

Sets the value of the use_ssl configuration parameter.

For example:

biha_db=# SELECT biha.set_use_ssl(true)
WARNING:  [BiHA] this parameter takes effect after node restart
 set_use_ssl
-------------
 t
(1 row)

Sets the value of the callbacks_timeout configuration parameter.

Adds a new callback and returns its unique ID. This function can only be called from the leader node in the LEADER_RW state. The new callback is replicated to the followers.

See Registering Callbacks for the example of using the biha.register_callback function.

Deletes a callback. This function can only be called on the leader node in the LEADER_RW state. Refer to Unregistering Callbacks for the example of using the biha.unregister_callback function.

Generates a magic string for the cluster node. For example:

biha_db=# SELECT biha.get_magic_string();
                          get_magic_string
----------------------------------------------------------------------
 dmVyc2lvbj0xIGhvc3Q9bG9jYWxob3N0IHBvcnQ9NjU0MzIgYmloYS1wb3J0PTEwMDAx
(1 row)

Sets the value of the asyncaction_timeout configuration parameter.

For example:

biha_db=# SELECT biha.set_asyncaction_timeout(1, 50000);
 set_asyncaction_timeout
-------------------------
 t
(1 row)

Sets the value of the flw_ro configuration parameter.

For example:

biha_db=# SELECT biha.set_flw_ro(1, true);
 set_flw_ro
------------
 t
(1 row)

Sets the value of the manage_slots_xmin configuration parameter.

Enables the service mode in a BiHA cluster. This function can only be called on the leader node. The function takes the following parameters:

Sets the value of the heartbeat_max_lost configuration parameter.

For example:

biha_db=# SELECT biha.set_heartbeat_max_lost(7);
 set_heartbeat_max_lost
-------------
 t
(1 row)

Sets the value of the heartbeat_send_period configuration parameter, in milliseconds.

For example:

biha_db=# SELECT biha.set_heartbeat_send_period(2000);
 set_heartbeat_send_period
-------------
 t
(1 row)

Sets the value of the no_wal_on_follower configuration parameter, in milliseconds.

For example:

biha_db=# SELECT biha.set_no_wal_on_follower(10000);
 set_no_wal_on_follower
------------------------
 t
(1 row)

Sets the value of the watchdog_timeout configuration parameter.

For example:

biha_db=# SELECT biha.set_watchdog_timeout(1, 10);
WARNING:  [BiHA] this parameter takes effect after node restart
 set_watchdog_timeout
----------------------
 t
(1 row)

Resets the NODE_ERROR state on a node. Use this function after you fix the issue that caused the NODE_ERROR state. For more information, see Restoring the Node from the NODE_ERROR State.