Re: postgrsql 9.5: Old WAL files remain in secondary `pg_xlog`

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: mohan(dot)nbs(dot)ont(at)gmail(dot)com
Cc: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: postgrsql 9.5: Old WAL files remain in secondary `pg_xlog`
Date: 2024-06-05 03:42:48
Message-ID: 0475684C-37A1-403D-8147-26D7FE860845@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


> On Jun 4, 2024, at 9:36 PM, Kashif Zeeshan <kashi(dot)zeeshan(at)gmail(dot)com> wrote:
>
> we are not using slots due to storage related issues that could occur if the network is broken

If you can ever upgrade to a current version, then there's a parameter that can be set to put a limit on retained WAL, so that in case of network failure, it sacrifices the ability to bring the replica back online quickly in favor of not bringing the primary down with disk full condition.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Siraj G 2024-06-05 03:51:56 Unable to create publication
Previous Message Kashif Zeeshan 2024-06-05 03:36:15 Re: postgrsql 9.5: Old WAL files remain in secondary `pg_xlog`