Feedback-ID: ia2694551:Fastmail
Date: Thu, 23 May 2024 14:31:44 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Jethish Jethish <jethish777@gmail.com>
Cc: Torsten =?utf-8?Q?F=C3=B6rtsch?= <tfoertsch123@gmail.com>, 
	pgsql-general@lists.postgresql.org
Subject: Re: Backup failure Postgres
Message-ID: <202405231231.53fwifecg76g@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAKeSjMh3YKDkcDORDL8cE4DbwaAuWrRz_aoS1GoS-XX=Ki5KvQ@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/202405231231.53fwifecg76g%40alvherre.pgsql>
Precedence: bulk

On 2024-May-23, Jethish Jethish wrote:

> I have tried by increasing the max_standby_streaming_delay but I'm facing
> lag issues on the replica server.
> 
> When i increase the max_standby_streaming_delay even if a query runs for 2
> minutes I'm facing lag issues for 2 minutes.

You could use a separate replica for backups, with a larger max delay.

> Data size is 3TB

I think pg_dump is not an appropriate tool for backups on an instance
this size.  Have you considered using pgbarman or such, instead?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/