1. Prepare the Backup Server and Database Server To begin, you’ll need to install the following packages on Debian-based installations: For the Barman Backup Server: python3-barman-latest_version barman_3-latest_version barman-cli_3-latest_version For the PostgreSQL Server: python3-barman-latest_version barman-cli_3-latest_version` Once the installation is complete on both nodes, configure SSH access between the servers using the barman (on the backup server) and postgres (on the PostgreSQL server) user accounts. Additionally, you’ll need to create the necessary users on PostgreSQL and configure it to archive data to the Barman backup server.

Issue Overview: As per the official PostgreSQL documentation and also here Pgpedia, the pg_stat_bgwriter table has undergone changes in PostgreSQL version 17, compared to versions 16 and below. As a result, Zabbix’s PostgreSQL plugin may throw errors in the PostgreSQL log files, such as the following: zbx_monitor@postgres LOCATION: errorMissingColumn, parse_relation.c:3716 zbx_monitor@postgres STATEMENT: SELECT row_to_json (T) FROM ( SELECT checkpoints_timed , checkpoints_req , checkpoint_write_time , checkpoint_sync_time , buffers_checkpoint , buffers_clean , maxwritten_clean , buffers_backend , buffers_backend_fsync , buffers_alloc FROM pg_catalog.

Loading Test Data into PostgreSQL To efficiently load test data into PostgreSQL, you can use a simple query like the following: INSERT INTO new.students (fname, fuid, lname, dob, joined) VALUES ( (array['Oswald', 'Henry', 'Bob', 'Vennie', 'Ivan', 'Stefan'])[floor(random() * 6 + 1)], uuid_generate_v4(), (array['Leo', 'Jack', 'Den', 'Daisy', 'Woody', 'Ivanov'])[floor(random() * 6 + 1)], '1980-01-01'::date + trunc(random() * 366 * 12)::int, generate_series('1/1/1990'::date, '12/01/2024'::date, '1 day') ); This query will insert random data into the students table.

Setting up logical replication between PostgreSQL 17 (master) and PostgreSQL 16 (replica), and vice versa, involves several key steps. The main goal is to ensure both systems are properly configured for logical replication, and then to establish the replication connection from PostgreSQL 17 (master) to PostgreSQL 16 (replica). Prerequisites PostgreSQL 17 (master) and PostgreSQL 16 (replica) should both be installed. Both systems should be accessible from each other (network connectivity).

In PostgreSQL, max_wal_senders is a configuration parameter that determines the maximum number of concurrent processes allowed to send Write-Ahead Logging (WAL) data to other systems, such as for replication or backup purposes. Properly configuring max_wal_senders is crucial for ensuring that your replication setup, backup processes, or logical replication needs are met without negatively impacting your primary database’s performance. Here are some best practices for tuning max_wal_senders: 1. Understand the Role of WAL Senders WAL senders are processes that transmit WAL data to replica servers or external systems.