[prev in list] [next in list] [prev in thread] [next in thread]
List: postgresql-general
Subject: How to Straming replication chatch up from archive
From: marco.ptz () tiscali ! it
Date: 2023-12-13 12:25:18
Message-ID: cae1f08b2c966b9a3e9a641c944c21c0 () tiscali ! it
[Download RAW message or body]
Hi,
we have a doubt interpreting documentation. We have a 9.6
installation master+stand-by in streaming replication.
Master database
is in archive mode and WAL archive destination (NFS) is mounted in both
master and stand-by servers.
The question is regarding this part of
documentation:
(https://www.postgresql.org/docs/9.6/warm-standby.html)
If you use
streaming replication without file-based continuous archiving, the
server might recycle old WAL segments before the standby has received
them.
If this occurs, the standby will need to be reinitialized from a
new base backup. You can avoid this by setting wal_keep_segments to a
value large enough to
ensure that WAL segments are not recycled too
early, or by configuring a replication slot for the standby. IF YOU SET
UP A WAL ARCHIVE THAT'S ACCESSIBLE FROM THE STANDBY,
THESE SOLUTIONS
ARE NOT REQUIRED, SINCE THE STANDBY CAN ALWAYS USE THE ARCHIVE TO CATCH
UP PROVIDED IT RETAINS ENOUGH SEGMENTS.
if the master overwrite the wal
BEFORE they are sent to the standby via replication, does the standby
AUTOMATICALLY start looking in WAL archive destination?
Or this step
have to be made by hand?
regards and thanks in advance
MP
[Attachment #3 (unknown)]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<br />Hi,<br />we have a doubt interpreting documentation. We have a 9.6 installation \
master+stand-by in streaming replication.<br />Master database is in archive mode and \
WAL archive destination (NFS) is mounted in both master and stand-by servers.<br \
/><br />The question is regarding this part of documentation: \
(https://www.postgresql.org/docs/9.6/warm-standby.html)<br /><br /><br /><em>If you \
use streaming replication without file-based continuous archiving, the server might \
recycle old WAL segments before the standby has received them. <br />If this occurs, \
the standby will need to be reinitialized from a new base backup. You can avoid this \
by setting <tt class="VARNAME">wal_keep_segments</tt> to a value large \
enough to<br /> ensure that WAL segments are not recycled too early, or by \
configuring a replication slot for the standby.<strong> If you set up a WAL archive \
that's accessible from the standby,</strong><br /><strong> these solutions are not \
required, since the standby can always use the archive to catch up provided it \
retains enough segments.</strong></em><br /><br /><br />if the master overwrite the \
wal BEFORE they are sent to the standby via replication, does the standby \
<strong>automatically</strong> start looking in WAL archive destination?<br />Or this \
step have to be made by hand?<br /><br /><br />regards and thanks in advance<br />MP \
</body></html> <br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic