public inbox for [email protected]  

help / color / mirror / Atom feed

From: Christophe Pettus <[email protected]>
To: KK CHN <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: PgBackRest and WAL archive expiry
Date: Thu, 19 Sep 2024 22:52:32 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKgGyB_TfVHh+mg-6JpPLscGO0h8_9F=km_EmQHxb69BEmsiiA@mail.gmail.com>
References: <CAKgGyB_TfVHh+mg-6JpPLscGO0h8_9F=km_EmQHxb69BEmsiiA@mail.gmail.com>



> On Sep 19, 2024, at 22:46, KK CHN <[email protected]> wrote:
> 
> 1. In the  EPAS server    I have   postgres.conf with 
> archive_command = 'pgbackrest --stanza=EMI_Repo archive-push %p && cp %p  /data/archive/%f'
> 
> The problem is that the   /data/archive  folder is growing  within a few days to 850GB  of 2 TB  partition.

The /data/archive directory is entirely under your control.  pgbackrest and PostgreSQL don't manage them in any way.  It will just keep growing indefinitely unless you take action to delete the WAL segments out of it.

There's no real benefit in maintaining that separate /data/archive directory; pgbackrest archives and manages the lifecycle of the WAL segments in its repository.  I wouldn't bother with that separate archive, and just use pgbackrest.

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: PgBackRest and WAL archive expiry
  In-Reply-To: <[email protected]>

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

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