Re: Postgresql Wal archive and Barman setup

From: masheed ullah <masheedullah(at)gmail(dot)com>
To: sa sa <ssmaugust(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgresql Wal archive and Barman setup
Date: 2026-07-01 07:15:14
Message-ID: CAHr8x_s-EBi4Fk-1aM1xB0iFn9p35+inu6SNN=LVpAZyuo+W2w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

You need to actively monitor archive location to avoid space issue.

Schedule a job to send alert email when archive location full to 80% or 90%

Best Regards,
*Masheed Ullah*

On Tue, Jun 30, 2026, 11:36 PM sa sa <ssmaugust(at)gmail(dot)com> wrote:

> Hello All,
>
> I have a scenario, where I need some suggestions and improvements if
> applicable.
>
> Our setup in brief
> 1) Primary --> standby
> using archive_command = rsync to primary local location and standby
> local location
> 2) Primary --> Barman
> Using streaming. Barman backup location is /nfs/DD9
> 3) Archive cleanup on primary is setup via crontab to every 14 days.
>
> Here is my scenario, If my barman nfs is down for 5 days and my local
> archive location is filled up during this time. what will happen.
>
> if my /srv/archive (location archive wal location) on primary and standby
> is 100% full during this time.
> my /srv/data is going to be 100% full , causing my cluster to go down.
>
> So what are the suggestions to avoid this situation.
>
> Thanks,
> Sa
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Venkat Akhil Pavuluri 2026-07-01 07:28:24 Re: Postgresql Wal archive and Barman setup
Previous Message Ron Johnson 2026-06-30 16:47:11 Re: Guidance on Calculating max_locks_per_transaction for a Highly Partitioned Environment