Re: max_slot_wal_keep_size

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: max_slot_wal_keep_size
Date: 2021-08-16 14:27:26
Message-ID: B74CCC19-B519-48E7-891A-99EFBA1800DC@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On Aug 16, 2021, at 8:08 AM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message srijith s 2021-08-16 16:20:49 After vacuum db size is increasing
Previous Message Alvaro Herrera 2021-08-16 14:08:56 Re: max_slot_wal_keep_size