Re: pgsql: Ensure that a standby is able to follow a primary on a newer tim

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <fujii(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Ensure that a standby is able to follow a primary on a newer tim
Date: 2021-01-15 02:50:46
Message-ID: YAEDBgdU0Wfftymv@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Jan 14, 2021 at 03:19:02PM +0900, Fujii Masao wrote:
> BTW, I included the URL to Michael's report [1] in the commit log. But this
> URL doesn't seem to work fine maybe because <message-id> part includes
> a slash character.

Sorry about that. This is related to mutt that has changed its logic
to generate message-ids in a recent release to be more random, and
maybe Debian is in play here with some custom patch, but I am not
sure. That's not configurable, but I'll try to investigate more if
there is something I can do about it :/
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2021-01-15 03:00:41 pgsql: Remove PG_SHA*_DIGEST_STRING_LENGTH from sha2.h
Previous Message Michael Paquier 2021-01-15 01:33:46 pgsql: Fix O(N^2) stat() calls when recycling WAL segments