Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1ltg1G-0003E1-UF
	for pgsql-performance@arkaria.postgresql.org; Thu, 17 Jun 2021 00:36:30 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1ltg1F-0000MF-58
	for pgsql-performance@arkaria.postgresql.org; Thu, 17 Jun 2021 00:36:29 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <postgresql@mailpen.com>)
	id 1ltg1E-0000M5-Kt
	for pgsql-performance@lists.postgresql.org; Thu, 17 Jun 2021 00:36:28 +0000
Received: from aws.mailpen.com ([52.43.43.172] helo=aws2.mailpen.com)
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <postgresql@mailpen.com>)
	id 1ltg1C-0005NM-0X
	for pgsql-performance@lists.postgresql.org; Thu, 17 Jun 2021 00:36:27 +0000
Received: from [172.20.70.208] (unknown [50.35.114.95])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by aws2.mailpen.com (Postfix) with ESMTPSA id B902FC7E9FE
	for <pgsql-performance@lists.postgresql.org>;
 Wed, 16 Jun 2021 17:36:24 -0700 (PDT)
To: pgsql-performance@lists.postgresql.org
From: "Dean Gibson (DB Administrator)" <postgresql@mailpen.com>
Subject: Estimating wal_keep_size
Organization: UltiMeth Systems
Message-ID: <471a6e7d-928e-c899-bf9f-341ae79b04ea@mailpen.com>
Date: Wed, 16 Jun 2021 17:36:24 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------C2E88A59BB75DEF43135EEDC"
Content-Language: en-US
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Archived-At: 
 <https://www.postgresql.org/message-id/471a6e7d-928e-c899-bf9f-341ae79b04ea%40mailpen.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------C2E88A59BB75DEF43135EEDC
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Is this reasonable thinking?

I'd think that one would want a *wal_keep_size* to cover the pending 
updates while the standby server might be unavailable, however long one 
might anticipate that would be.

In my case, I get a complete replacement (in the form of "|"- delimited 
ASCII files) of one of the SCHEMAs every Sunday.  The size of that ASCII 
data is about 2GB, so I'm thinking of doubling that to 4GB (256 WAL 
files) to protect me in the case of the standby being unavailable during 
the update.  Note that a complete loss of both servers is not 
catastrophic (I have backups);  it would just be annoying.


--------------C2E88A59BB75DEF43135EEDC
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Is this reasonable thinking?<br>
    <br>
    I'd think that one would want a <b>wal_keep_size</b> to cover the
    pending updates while the standby server might be unavailable,
    however long one might anticipate that would be.<br>
    <br>
    In my case, I get a complete replacement (in the form of "|"-
    delimited ASCII files) of one of the SCHEMAs every Sunday.  The size
    of that ASCII data is about 2GB, so I'm thinking of doubling that to
    4GB (256 WAL files) to protect me in the case of the standby being
    unavailable during the update.  Note that a complete loss of both
    servers is not catastrophic (I have backups);  it would just be
    annoying.<br>
    <br>
  </body>
</html>

--------------C2E88A59BB75DEF43135EEDC--