<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Database on BIFIT Mitigator</title>
    <link>https://docs.mitigator.ru/v26.04/en/tags/database/</link>
    <description>Recent content in Database on BIFIT Mitigator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://docs.mitigator.ru/v26.04/en/tags/database/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pgfailover Documentation</title>
      <link>https://docs.mitigator.ru/v26.04/en/kb/pgfailover/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.mitigator.ru/v26.04/en/kb/pgfailover/</guid>
      <description>pgfailover monitors the state of a PostgreSQL cluster and acts as a TCP proxy for clients, directing them to the current Primary. When the Primary changes, pgfailover terminates client connections, and they must reconnect.
Connection parameters are specified via environment variables with the PGFAILOVER_ prefix:
export PGFAILOVER_BIND_ADDRESS=&amp;#34;:5432&amp;#34; export PGFAILOVER_SERVERS=&amp;#34;postgres://repuser@pg0.example.com/database?sslmode=disable&amp;amp;connect_timeout=5 postgres://repuser@pg1.example.com/database?sslmode=disable&amp;amp;connect_timeout=5&amp;#34; ./pgfailover The server role (Primary/Standby) is checked using pg_is_in_recovery(), by default every 5 seconds (PGFAILOVER_INTERVAL), with the number of connection attempts controlled by the PGFAILOVER_ATTEMPTS environment variable (default: 1).</description>
    </item>
  </channel>
</rss>