Hi,
On 2020-03-28 17:47:19 +0900, Michael Paquier wrote:
> On Fri, Mar 27, 2020 at 05:10:03PM -0500, Justin King wrote:
> > This is encouraging. As I mentioned, we have a workaround in place for
> > the moment, but don't hesitate if you need anything else from me.
> > Thanks for jumping in on the thread, it was nice validation to know
> > that I wasn't the only one seeing the issue!
>
> Yes. We have been able to confirm that 2aa6e33 is a direct cause of
> your problem.
I assume you're still trying to track the actual cause of the problem
further?
Greetings,
Andres Freund
