Various experiments with PostgreSQL clustering perfomed at PostgresPro.

This is mirror of postgres repo with several changes to the core and few extra extensions.

• Transaction manager interface (eXtensible Transaction Manager, xtm). Generic interface to plug distributed transaction engines. More info at [[https://wiki.postgresql.org/wiki/DTM]] and [[http://www.postgresql.org/message-id/flat/F2766B97-555D-424F-B29F-E0CA0F6D1D74@postgrespro.ru]].
• Distributed deadlock detection API.
• Logical decoding of two-phase transactions.

• pg_tsdtm. Coordinator-less transaction management by tracking commit timestamps.
• multimaster. Synchronous multi-master replication based on logical_decoding and pg_dtm.

• postgres_fdw. Added support of pg_tsdtm.

1. Build and install postgres from this repo on all machines in cluster.
2. Install contrib/raftable and contrib/mmts extensions.
3. Right now we need clean postgres installation to spin up multimaster cluster.
4. Create required database inside postgres before enabling multimaster extension.
5. We are requiring following postgres configuration:

• 'max_prepared_transactions' > 0 -- in multimaster all writing transaction along with ddl are wrapped as two-phase transaction, so this number will limit maximum number of writing transactions in this cluster node.
• 'synchronous_commit - off' -- right now we do not support async commit. (one can enable it, but that will not bring desired effect)
• 'wal_level = logical' -- multimaster built on top of logical replication so this is mandatory.
• 'max_wal_senders' -- this should be at least number of nodes - 1
• 'max_replication_slots' -- this should be at least number of nodes - 1
• 'max_worker_processes' -- at least 2*N + 1 + P, where N is number of nodes in cluster, P size of pool of workers(see below) (1 raftable, n-1 receiver, n-1 sender, mtm-sender, mtm-receiver, + number of pool worker).
• 'default_transaction_isolation = 'repeatable read'' -- multimaster isn't supporting default read commited level.

1. Multimaster have following configuration parameters:

• 'multimaster.conn_strings' -- connstrings for all nodes in cluster, separated by comma.
• 'multimaster.node_id' -- id of current node, number starting from one.
• 'multimaster.workers' -- number of workers that can apply transactions from neighbouring nodes.
• 'multimaster.use_raftable = true' -- just set this to true. Deprecated.
• 'multimaster.queue_size = 52857600' -- queue size for applying transactions from neighbouring nodes.
• 'multimaster.ignore_tables_without_pk = 1' -- do not replicate tables without primary key
• 'multimaster.heartbeat_send_timeout = 250' -- heartbeat period (ms).
• 'multimaster.heartbeat_recv_timeout = 1000' -- disconnect node if we miss heartbeats all that time (ms).
• 'multimaster.twopc_min_timeout = 40000' -- rollback stalled transaction after this period (ms).
• 'raftable.id' -- id of current node, number starting from one.
• 'raftable.peers' -- id of current node, number starting from one.

1. Allow replication in pg_hba.conf.

• mtm.get_nodes_state() -- show status of nodes on cluster
• mtm.get_cluster_state() -- show whole cluster status
• mtm.get_cluster_info() -- print some debug info
• mtm.make_table_local(relation regclass) -- stop replication for a given table