pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: confusion between max_standby_archive_delay, max_standby_archive_delay and max_standby_archive_delay
Date: Sat, 11 Mar 2023 14:54:18 -0600
Message-ID: <a49b2087-ffb3-7360-1803-c1a99b59237a@gmail.com> (raw)
In-Reply-To: <CA+ONtZ62CK2mu75N9A3zzqQ_mffoHaRPiQit11xMTF2OC_zYGA@mail.gmail.com>
References: <CA+ONtZ62CK2mu75N9A3zzqQ_mffoHaRPiQit11xMTF2OC_zYGA@mail.gmail.com>

On 3/11/23 14:23, Atul Kumar wrote:
> Hi,
>
> Could someone help me in telling the difference between these 
> three parameters
> 1. max_standby_archive_delay
> 2. max_standby_streaming_delay
> 3. recovery_min_apply_delay
>
> My basic motive is to make the standby database server to be delayed to 
> apply the changes on itself,  if any data has been accidentally 
> deleted/updated/ truncated from the primary server.

What you're looking for is that WAL files be "aggregated and *optimized*" by 
removing statements which don't have any impact on the final state of instance.

That's great for *restoring* instances with update-heavy databases, and can 
only implemented by backup/restore software, or roll-your-own log shipping.  
Just as importantly, that aggregation-optimization software has it's own 
costs (time and disk space), since it takes time to scan through all the 
recovery logs, keeping track of what must stay, what can be tossed, and the 
final state.

-- 
Born in Arizona, moved to Babylonia.

view thread (5+ messages)  latest in thread

Message-ID: <a49b2087-ffb3-7360-1803-c1a99b59237a@gmail.com>
Permalink:  ../a49b2087-ffb3-7360-1803-c1a99b59237a@gmail.com/
Also on:    postgresql.org/message-id/a49b2087-ffb3-7360-1803-c1a99b59237a@gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: confusion between max_standby_archive_delay, max_standby_archive_delay and max_standby_archive_delay
  In-Reply-To: <a49b2087-ffb3-7360-1803-c1a99b59237a@gmail.com>
  References: <CA+ONtZ62CK2mu75N9A3zzqQ_mffoHaRPiQit11xMTF2OC_zYGA@mail.gmail.com> <a49b2087-ffb3-7360-1803-c1a99b59237a@gmail.com>

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

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