public inbox for [email protected]  
help / color / mirror / Atom feed
From: Klaus Darilion <[email protected]>
To: pgsql-general <[email protected]>
Subject: WAL compatibility between Primary and Standby Server, chained clients
Date: Mon, 8 Jun 2026 07:57:39 +0000
Message-ID: <DBAPR03MB6358A12B207F441E8B1BF984F11C2@DBAPR03MB6358.eurprd03.prod.outlook.com> (raw)

Hello!

I have questions about the streaming replication and about the WALs on the primary vs. standby servers.

How does the standby server decides when to write/rotate WAL files? Is this in sync how the primary server does this (ie. in the streaming replication protocol there are also signal when to rotate the WAL files)? Or does the standby server act totally on its own and decides itself when to rotate WAL files?

In the first case, are the WAL files between primary and standby server identical (so for example I could use a WAL file from a standby server with the base backup from a primary server)?

These questions came into my mind as we are doing a backup of the standby server using barman. Our standby server fell out of sync and had to resynced from the primary. Should a chained-downstream replication client (ie barman) automatically resync with the standby or is it necessary to re-initialize the replication from the standby to downstream clients?

Thanks
Klaus




--

Klaus Darilion, Head of Operations

nic.at GmbH, Jakob-Haringer-Straße 8/V

5020 Salzburg, Austria




reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: WAL compatibility between Primary and Standby Server, chained clients
  In-Reply-To: <DBAPR03MB6358A12B207F441E8B1BF984F11C2@DBAPR03MB6358.eurprd03.prod.outlook.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox