From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Archive cleanup
Date: Sat, 5 Aug 2023 19:44:28 -0500
Message-ID: <11b4adf7-9b46-a3b5-e18f-2cc38adc6116@gmail.com> (raw)
In-Reply-To: <CAJk5AtZTXYEWfs-Pp29rCjWawZfurm9=1QSsj24SktuNiu9r-g@mail.gmail.com>
References: <CAJk5AtZktvzjfdcKqtTt2S6Q9jN2Y3d4VgL246wWVQ1Tjp3XBQ@mail.gmail.com>
<CAMkU=1wj6bujF3JEh4tYjZ7aavwah_4mkckJyn8FcmV04w=wVA@mail.gmail.com>
<CAJk5AtZTXYEWfs-Pp29rCjWawZfurm9=1QSsj24SktuNiu9r-g@mail.gmail.com>
Use PgBackRest, and make your life a *lot* easier.
On 8/5/23 19:36, Rajesh Kumar wrote:
> Archive is must for point in time recovery right?
>
> On Fri, 4 Aug 2023 at 06:48, Jeff Janes <jeff.janes@gmail.com> wrote:
>
> On Fri, Aug 4, 2023 at 5:04 AM Rajesh Kumar
> <rajeshkumar.dba09@gmail.com> wrote:
>
> Hi friends,
>
> Anybody let me know how to automate the archive clean up in postgres.
>
>
> If the only reason you have an archive is so a standby can get the
> WAL, then you can just use a slot instead. If you don't have an
> archive, you don't need to clean it up.
>
> If you are using the archive for something else, you would need to
> tell us what that is. Otherwise, you are just asking "how long is a
> piece of string"?
>
> Cheers,
>
> Jeff
>
--
Born in Arizona, moved to Babylonia.
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: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Archive cleanup
In-Reply-To: <11b4adf7-9b46-a3b5-e18f-2cc38adc6116@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