From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: max_slot_wal_keep_size
Date: Mon, 16 Aug 2021 08:27:26 -0600
Message-ID: <B74CCC19-B519-48E7-891A-99EFBA1800DC@elevated-dev.com> (raw)
In-Reply-To: <202108161408.bppauqdp4knj@alvherre.pgsql>
References: <202108161408.bppauqdp4knj@alvherre.pgsql>
> On Aug 16, 2021, at 8:08 AM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> Yes, you should see
> invalidating slot "..." because its restart_lsn ... exceeds max_slot_wal_keep_size
Thank you; that's exactly what I need to cut through the log noise in splunk and see if this happened
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: scott_ribe@elevated-dev.com, alvherre@alvh.no-ip.org, pgsql-admin@lists.postgresql.org
Subject: Re: max_slot_wal_keep_size
In-Reply-To: <B74CCC19-B519-48E7-891A-99EFBA1800DC@elevated-dev.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