Re: pgsql: Fix handling of WAL segments ready to be archived during crash r

From: Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix handling of WAL segments ready to be archived during crash r
Date: 2020-04-27 10:29:08
Message-ID: 20200427122908.0275206c@firost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sat, 25 Apr 2020 09:31:14 +0900
Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> On Fri, Apr 24, 2020 at 05:30:21PM +0900, Kyotaro Horiguchi wrote:
> > I think we can reimplement them by waiting
> > pg_stat_archiver.last_failed_wal at least for archive_mode=always
> > case. I'm not sure about the case where archive_mode=on, though.
>
> Yeah, the second case is more tricky, and there is no point to add a
> poll query using pg_stat_file() on a .ready file either.

I suggested a patch in the original thread, waiting for the LSN gathered on
the primary.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2020-04-27 12:32:17 pgsql: pg_dump: Replace can't-happen error with assertion
Previous Message David G. Johnston 2020-04-27 07:37:33 Re: Detecting renamed columns via pgouput in logical replication ?